mirror of
https://github.com/pulsar-edit/pulsar.git
synced 2024-09-20 07:28:08 +03:00
477b075db5
To make https://github.com/atom-community/atom/pull/386 reviewable, that pr will be separated into many simpler prs. This is one of them. This first commit does the following: - update package.json - update package-lock.json using `./script/build` which also seems to update `apm/package-lock.json` - update packages/README.md - clone all language packages. Specifically: - `mkdir packages/language-<all of them>` - `cd packages/about` - For all languages: - `cd ../language-<>` - `git clone language-<>` - Move all files except `.git` from `language-<>/language-<>` to `language-<>` - delete `language-<>/language-<>` Since at first I accidentally updated `dependencies` then `packageDependencies`, it appears that since the versions of language-c, language-css, language-go, language-javascript, and language-sass don't match, `dependencies` was reset for those versions. [Those repos just happen to be precisely the ones that have tree-sitter v19](https://github.com/icecream17/atom-update-backlog/blob/main/Languages.md), (sans language-sass), which [currently breaks atom](https://github.com/atom/atom/issues/22129). So even though their repos are now in `packages`, **I've decided to not use them**. This is done by updating `packageDependencies` only for non-breaking languages.
41 lines
1.6 KiB
Markdown
41 lines
1.6 KiB
Markdown
<!--
|
|
|
|
Have you read Atom's Code of Conduct? By filing an Issue, you are expected to comply with it, including treating everyone with respect: https://github.com/atom/atom/blob/master/CODE_OF_CONDUCT.md
|
|
|
|
Do you want to ask a question? Are you looking for support? The Atom message board is the best place for getting support: https://discuss.atom.io
|
|
|
|
-->
|
|
|
|
### Prerequisites
|
|
|
|
* [ ] Put an X between the brackets on this line if you have done all of the following:
|
|
* Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
|
|
* Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
|
|
* Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
|
|
* Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
|
|
* Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
|
|
|
|
### Description
|
|
|
|
[Description of the issue]
|
|
|
|
### Steps to Reproduce
|
|
|
|
1. [First Step]
|
|
2. [Second Step]
|
|
3. [and so on...]
|
|
|
|
**Expected behavior:** [What you expect to happen]
|
|
|
|
**Actual behavior:** [What actually happens]
|
|
|
|
**Reproduces how often:** [What percentage of the time does it reproduce?]
|
|
|
|
### Versions
|
|
|
|
You can get this information from copy and pasting the output of `atom --version` and `apm --version` from the command line. Also, please include the OS and what version of the OS you're running.
|
|
|
|
### Additional Information
|
|
|
|
Any additional information, configuration or data that might be necessary to reproduce the issue.
|