Rewrite keyfork-crossterm into keyfork-multiterm #17

New Issue

Open

opened 2024-01-16 02:37:15 +00:00 by ryan · 0 comments

ryan commented

2024-01-16 02:37:15 +00:00

Owner

Crossterm is built around controlling the existing terminal. This will not be compatible if keyforkd needs to control the terminal of a calling process, or if any program needs to control any terminal other than the terminal provided by the process. Crossterm has a lot of global lock functionality that needs to be replaced with types containing the locked value.

Additionally, Crossterm has a mix of types that implement Command, and functions not associated with Command, in the same modules. Some examples are {Enable,Disable}BracketedPaste in the event module and {Enter,Leave}AlternateScreen in the terminal module. These should be moved to their own module.

Crossterm is built around controlling the existing terminal. This will not be compatible if `keyforkd` needs to control the terminal of a calling process, or if any program needs to control any terminal other than the terminal provided by the process. Crossterm has a lot of global lock functionality that needs to be replaced with types containing the locked value. Additionally, Crossterm has a mix of types that implement `Command`, and functions not associated with `Command`, in the same modules. Some examples are `{Enable,Disable}BracketedPaste` in the `event` module and `{Enter,Leave}AlternateScreen` in the `terminal` module. These should be moved to their own module.

ryan changed title from ~~Investigate how keyfork-crossterm's event::read() works~~ to Rewrite keyfork-crossterm into keyfork-multiterm

2024-01-18 21:21:12 +00:00

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/keyfork#17

No description provided.