1. 25

We have tags for emacs and vim, but no tag for text editing or text processing in general. There are a lot of editors out there that aren’t Emacs or Vim, and a lot of text processing tools that might benefit from being discussed under their own tag here.

What do y’all think?

  1.  

  2. 7

    Kakoune users would be pleased.

    1. 2

      Naive question: Is there really so much being written about Kakoune? Emacs and Vi/Vim have a history and “philosophy” (for lack of a better term), I’m not sure if this is the case with newer editors.

      1. 2

        I would say that, in terms of philosophy, Kakoune is a solid contender for the most interesting editor: https://kakoune.org/why-kakoune/why-kakoune.html.

        1. 2

          Sorry, but I’m missing what’s new… It seems like a better vim, but just from looking at the features I don’t see a totally new approach.

          1. 2

            I would say that verb noun vs noun verb is a huge difference. Embracing of multi-selection model is also novel. The plugin API is quite different from most other editors as well.

            1. 1

              I can’t seem to find anything notable on the plugin API, could you give an example? Regarding the other point, I fail to see what’s novel. “verb noun” vs “noun verb” seems like a matter of historical coincidence, and multi-selection/cursors has existed before in sublime and has been improved in editors like vis.

              1. 2

                Sorry, I don’t really want this to turn into back and forth dialog :) It’s totally ok if you have different concept of what novelty is. You can find more info about extending neovim in the docs.

    2. 4

      From the about page:

      To propose a tag, post a meta thread with the name and description. Explain the scope, list existing stories that should have been tagged, make a case for why people would want to specifically filter it out, and justify the increased complexity for submitters and mods.

      I don’t have a horse in this race, but I like the idea of validating this request by doing the work of digging out all the past posts that would have used this tag

      1. 3

        There was a meta-thread on the exact same question last year. A few ideas were thrown around, but no real consensus seems to have been reached.

        1. 1

          Let’s see if we can reach a consensus this time. :)

          1. 2

            I’m still into a tools tag, though I’m concerned it’d turn into a marketing channel.

        2. 1

          Assuming that tags are mainly to help people filter stuff out (I seem to have seen this suggested repeatedly?), what would be the intended aspects of editors to filter out through this tag? In a way, I think I’m kinda concerned this would easily conflate “editors use” with “editors writing”, and also potentially “word processors”. Maybe even “graphics editors”? Or the likes of PlantUML? I think I much easier understand that someone might to want to filter out vim, say if they are “emacs kind of person”, or just stick to vscode and couldn’t care less for all things vim. (And similar with emacs.)

          Though, I may well be misguided here.

          1. 3

            In my mind, it was for discussions of all things “text editor”: writing them, using them, configuring them, etc. We see a lot of posts for themes and for implementations of text editors, and for configurations and things like that. It might be that people want to filter that sort of thing out (or specifically search for them).

            There are other generic tags, like “programming” and “compsci”, and other topic-generic tags like “browsers” and “compilers”, so “editors” might fit in like those do. Just my $0.02, of course.

            1. 2

              Assuming that tags are mainly to help people filter stuff out (I seem to have seen this suggested repeatedly?)

              I like tags for another reason. Each tag on lobste.rs has an RSS feed (add .rss to the URL of a tag page).