aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* fix terminfo detectionPascal Kuthe2022-10-12
|
* adress review commentsPascal Kuthe2022-10-11
|
* fix typoPascal Kuthe2022-10-08
| | | Co-authored-by: Omnikar <omkar.subramaniam@icloud.com>
* add deprectation not for underlined modifier to docspascalkuthe2022-10-08
|
* avoid visual artificats on terminal emulators that do not support underline ↵Pascal Kuthe2022-10-06
| | | | colors
* make casing consistent with other configurationPascal Kuthe2022-10-06
|
* switch to termini for terminfoPascal Kuthe2022-10-06
|
* make underline_style a seperate optionPascal Kuthe2022-10-01
| | | | | | | | | | Underline styles are mutally exclusive and overwrite each other. Therefore implementing as an modifier lead to incorrect behaviour when the underline style is overwritten. For backwards compatability the "underline" modified is retained (but deprecated). Instead the "underline_style" and "underline_color" optios should be used to style underlines.
* Detect extended underline support using terminfoGokul Soumya2022-10-01
| | | | | | | The cxterminfo crate has been used over popular alternatives like `term` since it supports querying for extended capabilities and also for it's small codebase size (which will make it easy to inline it into helix in the future if required).
* Update theme documentationA-Walrus2022-10-01
|
* Fix failing testsA-Walrus2022-10-01
| | | | Add underline field to doctests, and fix bugs
* Add separate color for underlinesA-Walrus2022-10-01
|
* Support different kinds of underline renderingGokul Soumya2022-10-01
| | | | | | | | | Adds four new modifiers that can be used in themes: - undercurled - underdashed - underdotted - double-underline
* Ensure cursor in view after format (#4047)zensayyy2022-10-01
| | | Co-authored-by: Michael Davis <mcarsondavis@gmail.com>
* Add support for webassembly text format (#4040)Roberto Vidal2022-10-01
|
* themes: Add onedarker (#3980)nuid322022-10-01
|
* WGSL syntax highlighting fix (#3996)Chickenkeeper2022-09-30
|
* Add comment injection for R (#4031)Maximilian Muecke2022-09-29
|
* tutor: missing <ESC> before removing the second cursor (#4027)joleaf2022-09-29
| | | This step was missing in section 5.2 of tutor.
* Fix tutor typo `favourite` to `favorite` (#4007)Sora2022-09-28
|
* Add gruvbox dark (#3948)Sven-Hendrik Haase2022-09-28
| | | | | * Add gruvbox dark * fixup! Add gruvbox dark
* nix: replace `runCommandNoCC` with `runCommand` (#3992)Erin Kim2022-09-27
|
* build(deps): bump serde from 1.0.144 to 1.0.145 (#3989)dependabot[bot]2022-09-26
| | | Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* build(deps): bump thiserror from 1.0.35 to 1.0.36 (#3991)dependabot[bot]2022-09-26
| | | Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* build(deps): bump unicode-general-category from 0.5.1 to 0.6.0 (#3990)dependabot[bot]2022-09-26
| | | Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix: Improve JSX and TSX tag highlighting (#3973)Jacob Chandler2022-09-26
|
* build(deps): bump tokio-stream from 0.1.9 to 0.1.10 (#3988)dependabot[bot]2022-09-26
| | | Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* build(deps): bump once_cell from 1.14.0 to 1.15.0 (#3987)dependabot[bot]2022-09-26
| | | Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Remove `do_block` from Ruby indents (#3976)Oskar Köök2022-09-26
| | | `do_block` and `block` seem to conflict, causing double-indentation in some cases. Removing `do_block` does not seem to have any negative effect, while fixing the double-indentation issue.
* Add documentation for `max-line-length` (#3974)Oskar Köök2022-09-26
|
* chore: remove unneeded attribute after MSRV bump to 1.61 (#3961)Poliorcetics2022-09-25
|
* heex: upgrade grammar, add roots matching elixir (#3959)Clay2022-09-25
|
* Add bufferline colors to 15 themes (#3881)Invader Zim2022-09-23
| | | | | | | | | | | | | | | | | | | Themes: * acme * ayu_dark * ayu_light * ayu_mirage * base16_default_dark * base16_default_light * bogster * catppuccin_frappe * catppuccin_latte * catppuccin_macchiato * catppuccin_mocha * darcula * dark_plus * doom_acario_dark * emacs
* docs: Punctuation on tutor (#3888)adrian52022-09-23
|
* Add mix.exs and mix.lock as Elixir root markers (#3917)Riccardo Binetti2022-09-23
|
* Split helix_core::find_root and helix_loader::find_local_config_dirs (#3929)Riccardo Binetti2022-09-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Split helix_core::find_root and helix_loader::find_local_config_dirs The documentation of find_root described the following priority for detecting a project root: - Top-most folder containing a root marker in current git repository - Git repository root if no marker detected - Top-most folder containing a root marker if not git repository detected - Current working directory as fallback The commit contained in https://github.com/helix-editor/helix/pull/1249 extracted and changed the implementation of find_root in find_root_impl, actually reversing its result order (since that is the order that made sense for the local configuration merge, from innermost to outermost ancestors). Since the two uses of find_root_impl have different requirements (and it's not a matter of reversing the order of results since, e.g., the top repository dir should be used by find_root only if there's not marker in other dirs), this PR splits the two implementations in two different specialized functions. In doing so, find_root_impl is removed and the implementation is moved back in find_root, moving it closer to the documented behaviour thus making it easier to verify it's actually correct * helix-core: remove Option from find_root return type It always returns some result, so Option is not needed
* Document MSRV policy (#3913)Pascal Kuthe2022-09-23
|
* Deduplicate regexes in search_selection command (#3941)A-Walrus2022-09-22
|
* Theme: Papercolor: Tune inactive statusline (#3938)Henrik Tjäder2022-09-22
|
* Improve keymap errors from command typos (#3931)Michael Davis2022-09-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Improve keymap errors from command typos Currently, opening helix with a config containing a bad command mapping fails with a cryptic error. For example, say we have a config (bad.toml) with a command name that doesn't exist: [keys.normal] b = "buffer_close" # should be ":buffer-close" When we `hx -c bad.toml`, we get... > Bad config: data did not match any variant of untagged enum KeyTrie for key `keys.normal` at line 1 column 1 > Press <ENTER> to continue with default config This is because of the way that Serde tries to deserialize untagged enums such as `helix_term::keymap::KeyTrie`. From the Serde docs[^1]: > Serde will try to match the data against each variant in order and the > first one that deserializes successfully is the one returned. `MappableCommand::deserialize` fails (returns an Err variant) when a command does not exist. Serde interprets this as the `KeyTrie::Leaf` variant failing to match and declares that the input data doesn't "match any variant of untagged enum KeyTrie." Luckily the variants of KeyTrie are orthogonal in structure: we can tell them apart by the type hints from a `serde::de::Visitor`. This change uses a custom Deserialize implementation along with a Visitor that discerns which variant of the KeyTrie applies. With this change, the above failure becomes: > Bad config: No command named 'buffer_close' for key `keys.normal.b` at line 2 column 5 > Press <ENTER> to continue with default config We also provide more explicit information about the expectations on the field. A config with an unexpected type produces a message with that information and the expectation: [keys.normal] b = 1 > Bad config: invalid type: integer `1`, expected a command, list of commands, or sub-keymap for key `keys.normal.b` at line 2 column 5 > Press <ENTER> to continue with default config [^1]: https://serde.rs/enum-representations.html#untagged * Update helix-term/src/keymap.rs Co-authored-by: Ivan Tham <pickfire@riseup.net> Co-authored-by: Ivan Tham <pickfire@riseup.net>
* Fix highlighting on single-character Rust consts (#3927)gavincrawford2022-09-21
| | | | Co-authored-by: Kirawi <67773714+kirawi@users.noreply.github.com> Co-authored-by: Gavin Crawford <gavincrawford@users.noreply.github.com>
* Fix the picker’s keymap documentation (#3925)taupiqueur2022-09-21
|
* fix fish completions for --config & --log (#3912)Benedikt Müller2022-09-20
|
* add :lsp-restart command (#3435)Filipe Azevedo2022-09-20
|
* Fix preview bug (#3644)Joe2022-09-20
| | | | | * Fix preview bug * Add comment to empty case
* diagnostics: Use Vec<Tag> instead of Option<Vec<Tag>>Blaž Hrastnik2022-09-20
|
* Track source and tags in diagnostics (#3898)Luke Cycon2022-09-20
|
* Add command line parameter to specify log file (#3807)Tobias Hunger2022-09-20
| | | | | | | | | | | * Add command line parameter to specify log file I had the logs of my debug helix mixed in with the logs from the production helix. Add a `--log` command line argument to redirect any logs to other files, making my debugging easier :-) * Update completion files with `--log` argument
* Re-sort diagnostics after transaction transform (#3895)Michael Davis2022-09-20
| | | | | | | | Applying document-change transactions to diagnostic ranges is not stable with respect to the ordering of diagnostics. This can cause diagnostics to become temporarily unordered with some edits to a document, which can eventually break some invariants/assumptions in syntax::merge. With this change, Document::diagnostics are always sorted.
* build(deps): bump textwrap from 0.15.0 to 0.15.1 (#3906)dependabot[bot]2022-09-19
| | | Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
generated by cgit v1.2.3-70-g09d2 (git 2.47.1) at 2024-12-23 19:19:12 +0000