Explore the possibility to have the speed-type-mode as minor mode to use cursor-motion from the actual major mode

[lordnik22]

This is mainly subject to speed-type-buffer and speed-type-region

I would like to explore the possibility to have the speed-type-mode as minor mode.

Defining the speed-type-mode only as minor mode while typing would make it possible to use cursor-motion from the major mode the speed-type-typing-session was started from.

Maybe multiple speed-type-modes are needed:

• One for the typing session (minor mode)
• One for the end-menu (major mode)
  • Side-comment: The end-menu could also be realized using transient as an alternative.

Maybe it's possible to take over all the key-bindings from the major-mode when starting a speed-type-typing-session. This way the speed-type-major-mode would be curated with the functionality of the major-mode it was started from. This seems like the most lightweight solution. It would need to be removed after closing/completing the session. This would make it possible to also support major modes which require a file ref.

Maybe https://github.com/polymode has useful code for this problem

[lordnik22]

prepare-buffer ignore-errors and only call prog-mode as fallback

[lordnik22]

preview- and content-buffer should have it's own mode. similar magit has different modes for all it's buffers (magit-status-mode, magit-process-mode, magit-log-mode).

This way the mode does what it purpose is and users can make configurations more accuratly.

Still the major mode from which the speed-type session was started can't just be replaced by a speed-type-mode. so it's not exactly the same story as in the magit example.

It would be cool to turn any buffer into a speed-type session by changing the mode to speed-type-mode. Maybe if region is active it would narrow the buffer to the region and change the mode to speed-type-mode. If the major mode is changed there would be no need for the content buffer. The main problem is that in the speed-type session the text is touched. Add-words-on-error and fill-region would be deactivated.

On complete it would widen the buffer again and not insert the menu into the buffer (it would just save). It would not deactivate the mode (maybe add a config).

Make display-statistic interactive and display the statistic in a new buffer or just as message in *Messages* or something. Make actions interactive which would act on the completed-buffer.

[lordnik22]

Thoughts

The questions persists:

• Should speed-type be a mode compatible with other modes, undo and so forth or should it stay what it currently is?
• Should it be designed more like uniline which makes it more versatile and integrated into emacs?
• Speed-type can't be reused or combined by other packages. It's a closed package (sealed product). Does this need to change?

It would be good to extract everything related to the core functionality (typing, stats, timing, coloring) into the mode and everything which isn't (predefined setups, display stats, menu, actions, text-preparation) should stay and still work the same way.

Using just the mode would of course lead to inconsistent behavior. It would be more of a best effort solution instead of a seamless (but isolated) experience.

Much which is currently done in speed-type--setup needs to be migrated to speed-type-mode. The idea that speed-type-mode should be derived from overwrite-mode is a tingling idea but not practical due to #101 . overwrite-mode is also a minor-mode, which may be an argument that speed-type-modeshould also be a minor-mode.

Development Goal

• Isolation => Interconnectability
• one sealed product => can be opened up, an broken up in reusable parts by others
• closed => open

Various

MAYBE: This idea should be continued in a fork because it would redefine many things and break respectively. It would no longer have the same role or type of application.

Clarification

core functionality = is more or less everything which is needed while a speed-type session is running.

what is the relation between overwrite-mode and speed-type-mode? => both modes do not insert new characters but rather replace existing characters.

[lordnik22]

Which major modes should be supported by that new minor mode?

[lordnik22]

paredit-mode insterts () when typing (. Maybe we can trim input if the command was an self-insert-command to one char.