sidju / hired Goto Github PK

Expected: pressing d and u to navigate up and down
Actual: Help overlay is closed

For example allow \n to be converted into newline.

It seems that newlines aren't included when text is pasted into the editor. I'll have to look over the crossterm configurations about this, because I'm quite certain it has worked before...

When moving to a earlier line the moved lines are inserted, when moving to a later line they are appended. make this consistent to the same behavior as 'ed'.

Something that takes a signed integer and adds that to the number of spaces the selection is indented by.
Trying to remove more than there exists should just remove all there is without error.

Currently writing '90a90a' is a valid command interpreting as '90a'. Some warning should be raised instead.

Proposed commands:
'A': As the 'a' command except appending to the same line.
'C': As the 'c' command except presenting you with a line buffer with the current contents of the given line or each line in turn.
'I': As the 'i' command except prepending to the same line.

Since regex search is essential in every editor 'g' with support for at least one command (such as 'n', to print line with number) should be added in next version.

Currently they are included with the repo/code, which I think it is legal as the only distrubution method is as source, but to legally distribute binary packages we should add an attributions flag or similar to print them out.

The current highlighting requires a terminal with 24bit color support. Additionally the current printing doesn't wrap in a good way, so A rewrite is due that solves this.

'J': To re-flow the given selection to a given column width.

The easiest way to achieve this is to print a "viewed" selection after each command.

We currently assume that black is the background color and that white is the foreground color. We should instead either handle those as their own colors or use background/foreground instead of black/white.

Set the UI to something with borders, active filename, a command line and a window that shows the state of the buffer. In essence take the first steps towards VI.

crossterm-rs/crossterm#797

A recent change in Crossterm has causes Kitty and Windows key events to fire twice, once on press and again on release. We need to start explicitly ignoring release events (or upgrade to a crossterm version that allows opting out of this feature, PR ongoing: crossterm-rs/crossterm#778)

Until this is fixed it is unusable on windows.

Currently $ is after the '\n', meaning that replacing it with something is the same as adding to the line after. This is unexpected and should be resolved.

Since we now reset the color on white and black in 16-colour themes we should note that in the relevant code (which looks a bit strange now) and the theme declaration.

(
Possibly it would be good to create a way to more explicitly handle this in the theme itself, to provide a "colour" that is default and more explicitly use this in the theme.
)

(See 362c4a4 for relevant code change to clarify)

Allow users to write macros with arbitrary names to be accessed under ':'.

Initially without argument handling and acting upon a buffer.

(Intended use case is something along the lines of a shortcut for changing indentation, a crazy bash pipe for incrementing something or just appending 'hello world' to the buffer.)

Any plan to package this for nixos?