aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Support Cairo 0.10 syntaxBlaž Hrastnik2022-10-17
|
* Fix Cairo comment tokenJonathan LEI2022-10-17
|
* Fix readability of highlighted text on the rose_pine themes using official ↵echoriiku2022-10-17
| | | | palettes (#4221)
* Fix selecting pop dark theme (#4323)Brandon Dong2022-10-17
|
* Log failures to load tree-sitter parsers as error (#4315)Michael Davis2022-10-16
| | | | | | | Info logs don't show up in the log file by default, but this line should: failures to load tree-sitter parser objects are useful errors. A parser might fail to load it is misconfigured (https://github.com/helix-editor/helix/pull/4303#discussion_r996448543) or if the file does not exist.
* Fix debug assertion for diagnostic sort order (#4319)Michael Davis2022-10-16
| | | | | | | The debug assertion that document diagnostics are sorted incorrectly panics for cases like `[161..164, 162..162]`. The merging behavior in the following lines that relies on the assertion only needs the input ranges to be sorted by `range.start`, so this change simplifies the assertion to only catch violations of that assumption.
* Show keys required to enter each minor mode (#4302)Ben White-Horne2022-10-16
| | | Co-authored-by: Michael Davis <mcarsondavis@gmail.com>
* feat(csharp,debug): add C# debugger support (#4213)Filip Dutescu2022-10-15
|
* themes: Add `bogster_light` theme (#4265)Wojciech Kępka2022-10-15
| | | Co-authored-by: Wojciech Kępka <wojciech.kepka@softax.pl>
* themes: Update bogster theme (#4264)Wojciech Kępka2022-10-15
| | | Co-authored-by: Wojciech Kępka <wojciech.kepka@softax.pl>
* C# syntax highlight tweaks (#4285)Chickenkeeper2022-10-15
|
* Fixup Zig Indent Queries (#4281)Sora2022-10-15
|
* fix `:insert-output` doc: inserting output **before** each selection (#4286)ZJPzjp2022-10-15
|
* c/c++ highlighting: various tweaksSam McCall2022-10-15
| | | | | | | | | | - treat `restrict`/`_Atomic` like `const`/`volatile` => @keyword.storage.modifier - highlight `unsigned int` as builtin => @type.builtin - recognize `static_cast` and friends => @keyword - `template` is a kind of entity like `typename` => @keyword.storage.type - many declaration modifiers have nothing to do with storage/types (explicit, friend, access specifiers, inline in C++) => @keyword - fix floats highlighted as integer => @constant.numeric
* c/c++ highlights: *& are @type or @operator based on context (#4278)Sam McCall2022-10-15
|
* nit: remove a String allocation that is immediately used as an &str (#4277)Poliorcetics2022-10-14
|
* Changed Selection Yank Message (#4275)Nathaniel Graham2022-10-14
| | | Co-authored-by: Nathaniel Graham <ngraham@protonmail.com>
* Add support for Purescript language (#4242)Dario Oddenino2022-10-14
|
* Created heisenberg theme for helix editor (#4209)IrishMaestro2022-10-14
|
* Fix C++ syntax highlighting, and improve C & WGSL highlighting (#4079)Chickenkeeper2022-10-14
|
* Monokai Pro Octagon statusline modes (#4247)Ben Lee-Cohen2022-10-14
|
* tutor: Normalize key names, capitalization, etc.Tim Siegel2022-10-12
|
* book: Refer to keys by key names, not representationsTim Siegel2022-10-12
| | | | | | | | | | | | | | | | | | This is an attempt to clean up the inconsistent way that keys are written in various places. These rules require the fewest changes to the existing text. Use the "Key name", as defined in remapping.md, which uses "Some-Modifiers-PascalCaseKey". The "Representation", which uses "S-M-lowercasekey", is only used for configuration entries. For key combinations which do not present a popup, just present the keys one after the other, with no intervening space, like `]p`. For key combinations which present a popup, separate them with ` + `, like `Space + f`. The Ctrl modifier is called Ctrl, not Control.
* tutor: Minor grammar fixTim Siegel2022-10-12
| | | | No need to say additionally, as well, also, etc. One is enough.
* tutor: Clarify forward reference to "primary selection"Tim Siegel2022-10-12
|
* tutor: Clarify first multi-cursor exampleTim Siegel2022-10-12
| | | | | If the reader is unfortunate enough to place the cursor at the beginning of the line on step #1, subsequent steps will fail.
* tutor: Clarify forward reference to "select command"Tim Siegel2022-10-12
| | | | | | The phrase "Like the select command" suggests that the reader has been introduced to select already. That doesn't happen until the next chapter.
* Apply transactions to the jumplist for undo/redo (#4227)Michael Davis2022-10-12
| | | | | Undo/redo/earlier/later call `Document::apply_impl` which applies transactions to the document. These transactions also need to be applied to the view as in 0aedef0.
* Fix some commands not showing names in palette (#4223)Armin Ronacher2022-10-12
|
* Update tree-sitter-lua and add textobjects for Lua (#3552)Lennard Hofmann2022-10-12
|
* Fix append cursor location when selection anchor is at end of document (#4147)Graic2022-10-12
|
* Rearrange README.md slightly (#4206)Jacob Kiesel2022-10-11
|
* Fix confusion with using --hsplit --vsplit on startup at same time (#4202)Brian Orwe2022-10-11
|
* Rename extend indent captures.Daniel Ebert2022-10-11
| | | | Clarify comments in indent code.
* Slightly change the behavior of the `@stop-extend` capture.Daniel Ebert2022-10-11
| | | | This improves the behavior in case of multiple nested extensions.
* Improve code style for tree-sitter indentation.Daniel Ebert2022-10-11
| | | | Split extend logic into a separate file.
* Fix a bug that caused the indent for the line below to also be added in rare ↵Triton1712022-10-11
| | | | cases at the beginning of a file.
* Fix clippy warning.Triton1712022-10-11
|
* Add python indentation support to docs.Triton1712022-10-11
| | | | Document @extend-indented and @stop-extend captures for indent queries.
* Add `extend-indented` and `stop-extend` captures for indent queries.Triton1712022-10-11
| | | | Improve and re-enable python indent queries.
* update everforest theme (#3998)Alex2022-10-11
|
* Add colours "color-modes" to ayu_light theme (#4109)Stuart Baker2022-10-11
| | | | | | | * Rename "dark gray" to "light gray" * Add colours for statusline modes * Use UI background for inactive panes
* do not reparse unmodified injections (#4146)Pascal Kuthe2022-10-11
|
* fix: remove unneeded allocations when calling helix_view::Info::newAlexis (Poliorcetics) Bourget2022-10-11
|
* chore: fix clippy lintingAlexis (Poliorcetics) Bourget2022-10-11
|
* Overlay all diagnostics with highest severity on top (#4113)Michael Davis2022-10-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Here we separate the diagnostics by severity and then overlay the Vec of spans for each severity on top of the highlights. The error diagnostics end up overlaid on the warning diagnostics, which are overlaid on the hints, overlaid on info, overlaid on any other severity (default), then overlaid on the syntax highlights. This fixes two things: * Error diagnostics are now always visible when overlapped with other diagnostics. * Ghost text is eliminated. * Ghost text was caused by duplicate diagnostics at the EOF: overlaps within the merged `Vec<(usize, Range<usize>)>` violate assumptions in `helix_core::syntax::Merge`. * When we push a new range, we check it against the last range and merge the two if they overlap. This is safe because they both have the same severity and therefore highlight. The actual merge is skipped for any of these when they are empty, so this is very fast in practice. For some data, I threw together an FPS counter which renders as fast as possible and logs the renders per second. With no diagnostics, I see an FPS gain from this change from 868 FPS to 878 (+1.1%) on a release build on a Rust file. On an Erlang file with 12 error diagnostics and 6 warnings in view (233 errors and 66 warnings total), I see a decrease in average FPS from 795 to 790 (-0.6%) on a release build.
* remove filterting with C-space from pickerPascal Kuthe2022-10-11
|
* Treat space as a seperator instead of a character in fuzzy pickerPascal Kuthe2022-10-11
|
* Add a helper function for applying transactionsMichael Davis2022-10-11
| | | | | | It is easy to forget to call `Document::apply` and/or `View::apply` in the correct order. This commit introduces a helper function which closes over both calls.
* Apply transactions to ViewsMichael Davis2022-10-11
| | | | | | This change adds View::apply calls for all Document::apply call-sites, ensuring that changes to a document do not leave invalid entries in the View's jumplist.