@Raemon and I have shipped some improvements to the editor experience.
The two major changes displayed above are:
@Raemon cleaned up the options at the bottom of the editor. They used to look like this:
I implemented a basic command palette, available both in the post and comment editor. To open it, press ctrl/cmd + shift + p (same as the VSCode keybinding), or ctrl/cmd + /, because the first keybinding is “open an incognito window” on Firefox. The goal is to improve the discoverability and accessibility of various editor features, some of which previously required you to open the toolbar to use.
It behaves the same way as most other command palettes - esc to exit, up/down arrow to cycle, enter to execute the selected command, and also shows you the native keybindings for executing any given command.
Another minor QoL improvement is the right-click behavior in the editor. Previously, the only reliable way to open the inline toolbar was to manually highlight some text. If you tried to right-click to open the toolbar, this would happen to you:
Now it’s this:
(Note that most of the functionality inside of the toolbar is either trivial or available more easily via the command palette—I guess it’s now easier to convert something to a heading, block quote, or list?)
As always, let us know if you run into problems, or have other thoughts on the changes.
Er, bug report, the right-click menu is where my spell-check’s suggestions were. So now I get a red underline telling me a word is not in the dictionary, but to correct it I have to just, try to type the correct spelling. Or google it I guess.
Another minor QoL improvement is the right-click behavior in the editor
That’s really useful, thanks!
Any chance you can make a way to easily insert a horizontal-line element into comments? Perhaps add the button to the “show more items” submenu? People (me) sometimes write long-form comments with several different sections, and as-is, you have to go into your post-drafts folder and copy-paste it from there.
(Note that most of the functionality inside of the toolbar is either trivial or available more easily via the command palette—I guess it’s now easier to convert something to a heading, block quote, or list?)
It’s not clear offhand if/how I can convert things into heading with the command palette, is that currently supposed to be possible?
@Raemon and I have shipped some improvements to the editor experience.
The two major changes displayed above are:
@Raemon cleaned up the options at the bottom of the editor. They used to look like this:
I implemented a basic command palette, available both in the post and comment editor. To open it, press
ctrl/cmd + shift + p(same as the VSCode keybinding), orctrl/cmd + /, because the first keybinding is “open an incognito window” on Firefox. The goal is to improve the discoverability and accessibility of various editor features, some of which previously required you to open the toolbar to use.It behaves the same way as most other command palettes -
escto exit, up/down arrow to cycle,enterto execute the selected command, and also shows you the native keybindings for executing any given command.Another minor QoL improvement is the right-click behavior in the editor. Previously, the only reliable way to open the inline toolbar was to manually highlight some text. If you tried to right-click to open the toolbar, this would happen to you:
Now it’s this:
(Note that most of the functionality inside of the toolbar is either trivial or available more easily via the command palette—I guess it’s now easier to convert something to a heading, block quote, or list?)
As always, let us know if you run into problems, or have other thoughts on the changes.
Er, bug report, the right-click menu is where my spell-check’s suggestions were. So now I get a red underline telling me a word is not in the dictionary, but to correct it I have to just, try to type the correct spelling. Or google it I guess.
Oh, unfortunate. Will think about how to reconcile those, then.
That’s really useful, thanks!
Any chance you can make a way to easily insert a horizontal-line element into comments? Perhaps add the button to the “show more items” submenu? People (me) sometimes write long-form comments with several different sections, and as-is, you have to go into your post-drafts folder and copy-paste it from there.
Just make a new paragraph with three dashes into it, and it will automatically convert into a horizontal line.
Looks like that!
Oh, thanks!
It’s not clear offhand if/how I can convert things into heading with the command palette, is that currently supposed to be possible?
Yeah, you click the “paragraph” dropdown and change it to one of the heading options while having your cursor on the relevant line of text.
I don’t see a paragraph dropdown in the command-palette.