40 years of stagnation? Are you still using xterm on Xf86?
I’m not knowing people working on keyboard handling, but I’ve seen improvements in terminals every few months for the ~30 years I’ve been using one, including much improved keyboard handling. Yes there is a lot of legacy stuff going on in terminals, but there has also been a lot of good progress and modern terminals are nowhere close to what they were 15 years ago.
Of course. But maintaining hard wraps requires either an editor understanding the semantics (where a break can be inserted or removed without changing meaning) or manual labour, especially when editing existing paragraphs. Soft-wrapping is easier to do for the editor as it can’t change meaning and requires no manual work.
In what circumstances is a line break semantically significant within a Markdown paragraph (or a HMTL <p> tag, for that matter)?
I’m asking because I’m dimly aware of vast amounts of “non-standard” Markdown dialects floating around and I’m wondering if this is something like that.
(Of course, 2+ spaces followed by a line break does insert a <br /> tag in most MD dialects, but that’s not the issue here as far as I can see).
I never understood nor liked them: When in process of typing these arguments, there is signature help, and when I need info later, I can look at the hover help of the function, while inlay hints (in my eyes) just take space and create visual clutter.
That said, I’m glad it got added to Helix for all those who want/need them! I can just not enable inlay hints, but it increases use and thus potential developer manpower for Helix. I think it’s really great to have a modal editor with batteries included, even if nobody uses all of those batteries.
Always makes me happy to see another release from Helix. Great job guys! I absolutely love this editor.
An addition that isn’t in the linked to article is the file_picker_in_current_buffer_directory command. It does what the name suggests. Very useful imo.
I don’t think there is a key mapping for it though (how do I find out?), but adding your own is easy enough. These are my key binding additions after today’s update:
[keys.normal.","]
h = ":toggle lsp.display-inlay-hints"
w = ":toggle soft-wrap.enable"
f = "file_picker_in_current_buffer_directory"
I don’t think there is a key mapping for it though (how do I find out?)
Let me introduce to you the great <Space>? command picker! Regarding your mappings, I’ll try the inlay hints toggling, thanks for that idea. What do you use for keep_primary_selection, as comma is used as custom leader?
Comprehensive keyboard handling in terminals is a new idea to me. It’s cool to see someone trying to improve TTYs after 40 years of stagnation.
40 years of stagnation? Are you still using
xtermon Xf86?I’m not knowing people working on keyboard handling, but I’ve seen improvements in terminals every few months for the ~30 years I’ve been using one, including much improved keyboard handling. Yes there is a lot of legacy stuff going on in terminals, but there has also been a lot of good progress and modern terminals are nowhere close to what they were 15 years ago.
Another nice release for my favorite editor!
Soft-wrap!?!?! Finally.
This was the feature that I was waiting for too. Huge quality of life improvement if you’re editing markdown.
Maybe I am misunderstanding something, but isn’t the whole idea of how paragraphs work in markdown that hard wraps are fine?
Of course. But maintaining hard wraps requires either an editor understanding the semantics (where a break can be inserted or removed without changing meaning) or manual labour, especially when editing existing paragraphs. Soft-wrapping is easier to do for the editor as it can’t change meaning and requires no manual work.
In what circumstances is a line break semantically significant within a Markdown paragraph (or a HMTL
<p>tag, for that matter)?I’m asking because I’m dimly aware of vast amounts of “non-standard” Markdown dialects floating around and I’m wondering if this is something like that.
(Of course, 2+ spaces followed by a line break does insert a
<br />tag in most MD dialects, but that’s not the issue here as far as I can see).Sure, but one can hard or soft-wrap more than Markdown or HTML…
Yes, I can agree that being able to choose between softwrap och hardwrap is a good feature for a text editor!
That makes sense. Thanks! :)
Those LSP inlays are neat.
Before:
and after
The “named parameters” are virtual text and come from the parameter names in the source code.
I never understood nor liked them: When in process of typing these arguments, there is signature help, and when I need info later, I can look at the hover help of the function, while inlay hints (in my eyes) just take space and create visual clutter.
That said, I’m glad it got added to Helix for all those who want/need them! I can just not enable inlay hints, but it increases use and thus potential developer manpower for Helix. I think it’s really great to have a modal editor with batteries included, even if nobody uses all of those batteries.
I also hate the added noise, but I added this to my
config.tomlMaybe this way makes more sense to you as well. As a thing you can toggle on for a sec when needed.
Always makes me happy to see another release from Helix. Great job guys! I absolutely love this editor.
An addition that isn’t in the linked to article is the
file_picker_in_current_buffer_directorycommand. It does what the name suggests. Very useful imo.I don’t think there is a key mapping for it though (how do I find out?), but adding your own is easy enough. These are my key binding additions after today’s update:
Let me introduce to you the great
<Space>?command picker! Regarding your mappings, I’ll try the inlay hints toggling, thanks for that idea. What do you use forkeep_primary_selection, as comma is used as custom leader?Hah, you’re right. It was the first time setting them up, and forgot that
,was already taken. I’ll have to find a better leader.