| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* init
* wip
* wip
* fix unicode break
* fix unicode break
* Update helix-core/src/transaction.rs
Co-authored-by: Benoît Cortier <benoit.cortier@fried-world.eu>
* clippy
* fix
* add changes
* added test
* wip
* wip
* wip
* wip
* fix
* fix view
* fix #88
Co-authored-by: Benoît Cortier <benoit.cortier@fried-world.eu>
|
|
|
|
|
|
| |
User can select register to yank into with the " command.
A new state is added to `Editor` and `commands::Context` structs.
This state is managed by leveraging a new struct `RegisterSelection`.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
It seemed to panic when I pressed too many times, but that is from
lsp side.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Fixes #91
|
| |
|
| |
|
|\
| |
| | |
Fix match_brackets::find
|
| | |
|
|/ |
|
|
|
|
|
| |
As history is used separately from the rest of the edits, separating it
can avoid needless borrowing and cloning. But one need to be aware later.
|
| |
|
| |
|
|
|
|
| |
Closes #32
|
|
|
|
| |
Off by 1 error
|
| |
|
| |
|
|
|
|
|
| |
We barely have any flags so it's not worth the compilation time or
binary size to use clap.
|
| |
|
| |
|
|
|
|
| |
account.
|
|
|
|
|
|
|
|
|
| |
Can't do it via a scm query nicely because it returns an iterator over
all the matches, whereas we want to traverse the tree ourselves.
Can't extract the pattern data from a parsed query either.
Oh well, toml files for now.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|