| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Shorter CI times, and it should be good enough.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The panics would occur because set_style
would draw outside of the the surface.
Both occured using `find_prev` or `till_prev`
In my case the first panic! would appear
in a terminal with around 80 columns
in helix/README.md going to the end of the file
with `geglf(`
the second with `geglfX`
The off by one fix ensures that `find_nth_prev`
starts at the first character to the left
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add MacOS install instructions
* Change version name argument
When using the -V command to get the version you are given 'helix-term x.x.x', I changed this to just helix as it makes more sense.
* Fixed version number
* Fixed version number
* Fixed version number
* Fixed version number
* Fixed version number
* Fixed version number
|
| |
|
|
|
|
|
|
|
|
|
|
| |
`is_ascii_punctuation` will only work for ASCII punctuations, and when
we have unicode punctuation (or other) we jump into the `unreachable`.
This patch fallback into categorizing everything in this branch as
`Unknown`.
Fixes https://github.com/helix-editor/helix/issues/123
https://github.com/helix-editor/helix/pull/135: add better support for
unicode categories.
|
| | |
|
| | |
|
| |
|
|
| |
Co-authored-by: Ivan Tham <pickfire@riseup.net>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* theme: Enable style modifiers in theme.toml
* docs: theme documentation
* fixup: parse modifiers with filter_map
* theme: tests for parse_style
* theme: Log invalid cases in theme.toml parse
* docs: theme documentation fixup
* docs: Blaz's theming comments
* docs: Theme doc fixes from pickfire
Co-authored-by: Ivan Tham <pickfire@riseup.net>
* theme: More context in logs, TODO for alerting users
* contrib: Ingrid's theme
* docs: Theme subsection fixes
Co-authored-by: Ivan Tham <pickfire@riseup.net>
|
| | |
|
| | |
|
| |
|
|
|
| |
It seemed to panic when I pressed too many times, but that is from
lsp side.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Runs every day as cron. Add matrix for test, includes windows and macos.
|
| | |
|
| |
|
|
|
| |
This makes the load_runtime_file function behave like the non-embedded
one.
|
| |
|
|
| |
This test makes sure we can read some amount of data from the runtime folder.
|
| |
|
|
| |
Reduce the number of feature switches for the embed_runtime feature.
|
| |
|
| |
Co-authored-by: Ivan Tham <pickfire@riseup.net>
|
| |
|
|
| |
Co-authored-by: Ivan Tham <pickfire@riseup.net>
|
| | |
|
| |
|
|
|
|
| |
These changes provide a new feature flag "embed_runtime" that when
enabled and built in release mode will embed the runtime folder into the
resulting binary.
|
| |
|
|
| |
Fix #93
|
| |
|
|
| |
tree_sitter_haskell not compiling on msvc without it
|
| |
|
|
| |
helix-term/src/ui/editor.rs:275:29
This would happen when the window-size was to small to display the entire width and one would start jumping forwards with f<some_char> and the beginning of the highlighted area would end up outside of the window
|
| |
|
|
|
|
| |
Bevore this PR `commands::find_prev_char` and `commands::till_prev_char` were triggerable through keys
but `seach::find_nth_next()` was hardcoded in `_find_char`.
The passed `fn` was nerver used. With this PR the passed `fn` is used.
The change in search.rs resolves an off by one error in the behivor of `find_nth_prev`
|
| | |
|
| |
|
| |
Better error for #123
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* init
* wip
* wip
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* add home-end keymaps
* implement extend methods for extend_line_start, extend_line_end
* add home-end mappings to keymaps.md
* add ^-$ extend mappings for extend mode
* pass cargo linter
|
| |
|
|
|
|
| |
The haskell grammar requires at last c++14 to build.
Fixes #117
|
| |
|
|
|
|
| |
cc-rs will already do the right thing and figure out the flags.
Fixes #34
|
| |
|
|
| |
It seems to work
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
