My main concern was about taking up such a prime key for this task. But I suppose that marking is a central operation and it's not unreasonable.
If you want to create a PR with this I'm happy to accept it :)

I already made 2 attempts but my Rust is very rusty ;-) I'll have to work on that sometime in the future when I'll have free time to actually learn rust.

No rush though, redu is an excellent helper as it is today. Much better than what I was doing before, manually scanning repos and manually creating lists!

Feel free to close the issue.

I would suggest understanding how the flow works for example for deleting a mark, then implementing a toggle should be very similar.

At a high level the event loop goes like this:

Terminal event is read and converted from a raw key event to something a bit more high level with semantic meaning. See

redu/src/main.rs

Line 229 in 2e5bff7

let mut o_event = convert_event(crossterm::event::read()?);
We call the update function on the UI code with this event and get back some action that we should perform. See

redu/src/main.rs

Line 231 in 2e5bff7

o_event = match app.update(event) {

and

redu/src/ui.rs

Line 151 in 2e5bff7

Unmark => self.unmark_selection(),
We perform the action which might result in additional events which we feed back to the UI via update again. See

redu/src/main.rs

Line 258 in 2e5bff7

Action::DeleteMark(loc) => {
When there's no more events resulting from this action go back to 1

Feature request: Allow toggle marks using <space> instead of Mark/Unmark keys #18

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions