Closed MasonProtter closed 3 years ago
The minimum Next should do is add to ability to edit fields with an external editor. This is extremely useful for GitHub issues, wiki editing, etc.
Beyond that, @MasonProtter do you have specific examples in mind?
I was imagining just providing the ability to access and edit text files that are stored locally on my computer. Doesn't need to be anything fancy, and then one could conceivably build up an emacs style workflow using common lisp as the extension language.
If that was implemented then there could be a command to select a text field and open a text buffer, then you write in the buffer and when you're done the text gets automatically put into the relevant field.
Perhaps another way to go about doing this is making some way to open an emacs buffer inside next, ie. using next as its window server. Don't know how feasible any of this is though. 🤷♂️
If that was implemented then there could be a command to select a text field and open a text buffer, then you write in the buffer and when you're done the text gets automatically put into the relevant field.
Yes, that's exactly what I meant. Qutebrowser can do that.
I was imagining just providing the ability to access and edit text files that are stored locally on my computer. Doesn't need to be anything fancy, and then one could conceivably build up an emacs style workflow using common lisp as the extension language.
Well, that's way out of the scope of Next, I guess... Is there a link with Web browsing here?
If you are looking for an Emacs alternative using a better Lisp, what about https://github.com/tonyg/rmacs or https://github.com/soegaard/remacs?
Perhaps another way to go about doing this is making some way to open an emacs buffer inside next, ie. using next as its window server. Don't know how feasible any of this is though.
Don't know, maybe GTK can do this.
Note that you can go the other way around with EXWM or Emacs Application Framework.
If you are looking for an Emacs alternative using a better Lisp
and Lem, written in CL, so this may open up possibilities ?
The minimum Next should do is add to ability to edit fields with an external editor. This is extremely useful for GitHub issues, wiki editing, etc.
I would argue that unless next is going to completely re-implement emacs and vi it is probably also the most it should do.
The way things are looking, I would say we are on track to making a CL Emacs :-D
See also #461.
What's that you say? Integrate an editor into Nyxt? My wish is your command!
https://github.com/atlas-engineer/nyxt/pull/1242
now any editor can be implemented as an extension. As a proof of concept I've implemented the Ace
editor. It is nothing spectacular right now, but we can open and edit/save files. In the future we can configure it to do all sorts of highlighting, etc.
Ace: implementation: https://github.com/atlas-engineer/nx-ace
please enjoy :-)
I'm only half joking here, but I think it'd be neat to copy some of emacs' functionality into an integrated text editor. Then I'd never have to leave my browser. 😄