3 ms·

I don’t see much about this idea that requires a new editor. This seems to be mainly a new terminal app, not a new editor. The only points of integration betwee

I don’t see much about this idea that requires a new editor. This seems to be mainly a new terminal app, not a new editor. The only points of integration between the terminal and the editor are the E/W/L commands to manage open files and the right-click context rules. With so little connection between the editor and the terminal, I think this project would be better off changing focus to be only a new terminal app. There is no need to reinvent the wheel by bundling an editor with it. You haven’t listed any planned features for the editor that other editors don’t already do, so by cancelling the editor portion of the project, you wouldn’t lose any features. Your terminal could still support customizable E/W/L commands and right-click context rules – but there is no need to tie those features to any one particular editor. Instead, provide a custom configuration of the terminal that sends commands to your favorite existing editor through built-in means. Or if that integration wouldn’t be powerful enough, provide a plugin for the editor that integrates it with your new terminal. That way, users of many different editors could use your terminal.

satyajitranjeev 12y ago
Many a time I see myself having two windows open. My editor and shell. I keep jumping from these windows either copying content or executing commands. The whole idea of the project is to bring them together. It is to act as a bridge between the commands that the OS provides and the editor.
- ayrx 12y ago
  > The whole idea of the project is to bring them together. What does this do that a normal shell and vim doesn't? If I use that together with something like tmux I can jump between the two seamlessly entirely with keyboard commands.
  - satyajitranjeev 12y ago
    Right now it does not do anything a vim and a normal shell can't do. But the idea of plumbing is something that would be quite difficult(not impossible) to achieve in vim and a terminal.
- z0r 12y ago
  This is an interesting project for sure (writing text editors are fun, and the mix of technologies chosen is interesting) - but I think it would be fairly straightforward to implement the features you've shown in your demonstration as an emacs package :)
  - bdamm 12y ago
    Emacs has a ton of baggage. I like the fresh approach and especially the idea of hacking on my editor in go. As a hardened vim user I like that influence and I think it shows in edi.

satyajitranjeev 12y ago

Many a time I see myself having two windows open. My editor and shell. I keep jumping from these windows either copying content or executing commands. The whole idea of the project is to bring them together. It is to act as a bridge between the commands that the OS provides and the editor.

ayrx 12y ago
> The whole idea of the project is to bring them together. What does this do that a normal shell and vim doesn't? If I use that together with something like tmux I can jump between the two seamlessly entirely with keyboard commands.
- satyajitranjeev 12y ago
  Right now it does not do anything a vim and a normal shell can't do. But the idea of plumbing is something that would be quite difficult(not impossible) to achieve in vim and a terminal.
z0r 12y ago
This is an interesting project for sure (writing text editors are fun, and the mix of technologies chosen is interesting) - but I think it would be fairly straightforward to implement the features you've shown in your demonstration as an emacs package :)
- bdamm 12y ago
  Emacs has a ton of baggage. I like the fresh approach and especially the idea of hacking on my editor in go. As a hardened vim user I like that influence and I think it shows in edi.