7 ms·

I've wanted to write a small text editor for a while - cause I feel like most editors don't fit my workflow - but I've been a bit too busy with work. I don't r

by Daunk 4y ago

I've wanted to write a small text editor for a while - cause I feel like most editors don't fit my workflow - but I've been a bit too busy with work. I don't really care about fancy features or extensions. Let me just create "tasks" (for compiling and such) and let me execute these tasks with a single button, then let me see the output from these tasks that eventually execute some application/compiler etc. That'll let me use it for any language and task. I'd also preferably like to use I J K L as the cursor keys and toggle "Mode" (VIM style) with TAB. And the whole thing should just run in your terminal, which can already render text nicely.

proxysna 4y ago
Sounds like all you need is à plugin to call makefile targets from vim.
- Daunk 4y ago
  That is a method I've been toying with. But it's still such as hassle to quickly prototype something this way. It's also near impossible to get I J K L working as the cursor keys in VIM without having some major interference.
  - nequo 4y ago
    Maybe you’d have more success with Emacs? You could write elisp functions for your tasks and bind them to your prefered keys, with or without Evil.
    - engfan 4y ago
      Actually, using Org mode and the Hyperbole package in Emacs solves all the problems listed in easy to use ways except you get much more editing dunctionality rather than just the features requested. Don’t reinvent the wheel; just learn something that runs everywhere and solves your problems. You start Emacs once and then rapidly edit files from the command-line by calling emacsclient, not restarting Emacs.
      - nine_k 4y ago
        Emacs is a great software ecosystem, with a very.flexible editor built in. With evil-mode, there's no excuse not to try it even if you find Vim's way of controlling input superior (which it as well may be).
  - hiccuphippo 4y ago
    I haven't used it but there is :make which works with a Makefile.
properparity 4y ago
Also been thinking this. What I want from a text editor is: - Like you said, running tasks with a button/keybind, easily customizable (Like I wanna open a config file, add a function/script, bind to key/create UI button, done, not make a "plugin" not compile an "extension" or anything like that) - Fuzzy finding/search - ripgrep and fzf can do that, so just bundle those I guess, or write my implementation of those. - Must start instantly, load files instantly, every action needs to takes at most 100 ms. - Be a "portable application", i.e it sits in a folder with everything it needs and I can copy that folder to any computer and be up and running with exactly the same configuration. and NOTHING else.
- aethy 4y ago
  This is also my general hope for lite. - Configs in lite are all done in lua files, and there are two files that you can edit without ever having to create a plugin that are automatically loaded by the editor: your system wide user config (a lua file), and a project file (.lite_project). Both of these can bind keys, create buttons, add functions, and whatever you like, really. - Fuzzy finding we can do, but it's not great. We're doing some work on this, but at the moment, we'll probably disappoint you. - We should start pretty instantaneously on a vanilla config, though for large directory trees, there's an architectural issue that does make us take a bit longer, that hopefully will be resolved in a release or two. So if you have a smaller directory tree, then lite should be pretty quick; if it's large, perhaps hold off looking at it. - lite offers fully portable releases, and infact, I have an all-in-one build that bundles everything into a single, mostly statically linked executable; it's generally very flexible about how things are deployed. We tend to add almost all extra functionality via plugins; so if you don't want a particular feature, you can simply remove the plugin, and be done with it.
aethy 4y ago
I actually authored something for this to work with my workflow on lite-xl (I compile a mid-sized C++ codebase on the regular). It's still not really ready for release, but it's here, in case you're at all interested: https://github.com/adamharrison/lite-xl-ide https://github.com/adamharrison/lite-xl-ide ; it's a build system and debugger integration. The build tasks don't run in a terminal however; they move over to a build window at the bottom of the editor. The execution, however, by default, runs in whatever terminal you want to configure, so the actual program output does dump to an external terminal. Unfortunately, there is no truly integrated terminal as of yet.
marssaxman 4y ago
I built something which scratches that basic itch, though my taste differs from yours: https://www.github.com/marssaxman/ozette.git https://www.github.com/marssaxman/ozette.git I've used this for both hobby projects and professional work, over the years (though I often find myself using VSCode these days).
alwillis 4y ago
Certainly Vim has all of the Makefile machinery built-in and it wouldn't take much to customize it [1]. [1]: https://vimways.org/2018/runtime-hackery/ https://vimways.org/2018/runtime-hackery/

by Daunk 4y ago

proxysna 4y ago

Sounds like all you need is à plugin to call makefile targets from vim.

Daunk 4y ago
That is a method I've been toying with. But it's still such as hassle to quickly prototype something this way. It's also near impossible to get I J K L working as the cursor keys in VIM without having some major interference.
- nequo 4y ago
  Maybe you’d have more success with Emacs? You could write elisp functions for your tasks and bind them to your prefered keys, with or without Evil.
  - engfan 4y ago
    Actually, using Org mode and the Hyperbole package in Emacs solves all the problems listed in easy to use ways except you get much more editing dunctionality rather than just the features requested. Don’t reinvent the wheel; just learn something that runs everywhere and solves your problems. You start Emacs once and then rapidly edit files from the command-line by calling emacsclient, not restarting Emacs.
    - nine_k 4y ago
      Emacs is a great software ecosystem, with a very.flexible editor built in. With evil-mode, there's no excuse not to try it even if you find Vim's way of controlling input superior (which it as well may be).
- hiccuphippo 4y ago
  I haven't used it but there is :make which works with a Makefile.

properparity 4y ago

Also been thinking this. What I want from a text editor is: - Like you said, running tasks with a button/keybind, easily customizable (Like I wanna open a config file, add a function/script, bind to key/create UI button, done, not make a "plugin" not compile an "extension" or anything like that) - Fuzzy finding/search - ripgrep and fzf can do that, so just bundle those I guess, or write my implementation of those. - Must start instantly, load files instantly, every action needs to takes at most 100 ms. - Be a "portable application", i.e it sits in a folder with everything it needs and I can copy that folder to any computer and be up and running with exactly the same configuration. and NOTHING else.

aethy 4y ago
This is also my general hope for lite. - Configs in lite are all done in lua files, and there are two files that you can edit without ever having to create a plugin that are automatically loaded by the editor: your system wide user config (a lua file), and a project file (.lite_project). Both of these can bind keys, create buttons, add functions, and whatever you like, really. - Fuzzy finding we can do, but it's not great. We're doing some work on this, but at the moment, we'll probably disappoint you. - We should start pretty instantaneously on a vanilla config, though for large directory trees, there's an architectural issue that does make us take a bit longer, that hopefully will be resolved in a release or two. So if you have a smaller directory tree, then lite should be pretty quick; if it's large, perhaps hold off looking at it. - lite offers fully portable releases, and infact, I have an all-in-one build that bundles everything into a single, mostly statically linked executable; it's generally very flexible about how things are deployed. We tend to add almost all extra functionality via plugins; so if you don't want a particular feature, you can simply remove the plugin, and be done with it.

aethy 4y ago

I actually authored something for this to work with my workflow on lite-xl (I compile a mid-sized C++ codebase on the regular). It's still not really ready for release, but it's here, in case you're at all interested: https://github.com/adamharrison/lite-xl-ide https://github.com/adamharrison/lite-xl-ide ; it's a build system and debugger integration. The build tasks don't run in a terminal however; they move over to a build window at the bottom of the editor. The execution, however, by default, runs in whatever terminal you want to configure, so the actual program output does dump to an external terminal. Unfortunately, there is no truly integrated terminal as of yet.

marssaxman 4y ago

I built something which scratches that basic itch, though my taste differs from yours: https://www.github.com/marssaxman/ozette.git https://www.github.com/marssaxman/ozette.git I've used this for both hobby projects and professional work, over the years (though I often find myself using VSCode these days).

alwillis 4y ago

Certainly Vim has all of the Makefile machinery built-in and it wouldn't take much to customize it [1]. [1]: https://vimways.org/2018/runtime-hackery/ https://vimways.org/2018/runtime-hackery/