1. Forum
  2. Usenet
  3. COMP.EDITORS

  • (10 essential Vim plugins) -- Top 11 Text Editors (Jan. 2024)

    From HenHanna@21:1/5 to All on Sat Mar 2 18:44:15 2024
    i didn't even know that Vim allowed plugins!


    Does Vim support this? --- making up a command "on the fly" by
    mapping some keystrokes onto a single KEY... i guess that's what [map] does.


    10 essential Vim plugins https://medium.com/@huntie/10-essential-vim-plugins-for-2018-39957190b7a9



    https://old.reddit.com/r/vim/comments/ulphgp/what_are_your_musthave_vimnvim_extensions/





    Which is one of the most used text editors?

    The Top 11 Text Editors (January 18, 2024)

    1. UltraEdit. UltraEdit is a versatile and powerful text editor known for handling complex and large files with ease. ...

    2. BBEdit. ...

    3. Visual Studio Code. ...

    4. Sublime Text. ...

    5. WebStorm. ...

    6. Notepad++ ...

    7. CoffeeCup HTML Editor. ...

    8. TextMate.

    9. Espresso

    10. Bluefish

    11. Vim ------------ Wow!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Janis Papanagnou@21:1/5 to Stan Brown on Sat Mar 2 23:40:54 2024
    On 02.03.2024 23:23, Stan Brown wrote:
    On Sat, 2 Mar 2024 18:44:15 +0000, HenHanna wrote:
    Does Vim support this? --- making up a command "on the fly" by
    mapping some keystrokes onto a single KEY... i guess that's what [map] does.


    Always nice to see someone find an answer to their own question, [...]

    Not too surprising given that he's got the hint in his previous thread.
    ;-)

    Janis

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stan Brown@21:1/5 to HenHanna on Sat Mar 2 14:23:22 2024
    On Sat, 2 Mar 2024 18:44:15 +0000, HenHanna wrote:
    Does Vim support this? --- making up a command "on the fly" by
    mapping some keystrokes onto a single KEY... i guess that's what [map] does.


    Always nice to see someone find an answer to their own question,
    though it _is_ rather faster than usual to do it before finishing the
    paragraph that contains the question!

    --
    Stan Brown, Tehachapi, California, USA https://BrownMath.com/
    Shikata ga nai...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to HenHanna on Sun Mar 3 00:06:57 2024
    On Sat, 2 Mar 2024 18:44:15 +0000, HenHanna wrote:

    i didn't even know that Vim allowed plugins!

    That depends on the vim though, doesn’t it? There are multiple
    incompatible versions; there’s even one that supports Lua as an extension language.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Kempe@21:1/5 to All on Sun Mar 3 20:23:51 2024
    Den 2024-03-03 skrev Lawrence D'Oliveiro <ldo@nz.invalid>:
    On Sat, 2 Mar 2024 18:44:15 +0000, HenHanna wrote:

    i didn't even know that Vim allowed plugins!

    That depends on the vim though, doesn’t it? There are multiple
    incompatible versions; there’s even one that supports Lua as an extension language.

    Vim is vim, isn't it? Vim has support for plugins in at least lua,
    perl and python as far as I know. Are you thinking of different clones
    of vi?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to Andreas Kempe on Sun Mar 3 23:32:49 2024
    On Sun, 3 Mar 2024 20:23:51 -0000 (UTC), Andreas Kempe wrote:

    Are you thinking of different clones of vi?

    Aren’t they all called “vim” nowadays?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Janis Papanagnou@21:1/5 to Lawrence D'Oliveiro on Mon Mar 4 08:12:33 2024
    On 04.03.2024 00:32, Lawrence D'Oliveiro wrote:
    On Sun, 3 Mar 2024 20:23:51 -0000 (UTC), Andreas Kempe wrote:

    Are you thinking of different clones of vi?

    Aren’t they all called “vim” nowadays?

    No. Why should vi clones be called "vim"?

    Vim is one (outstanding) vi clone.

    Janis

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to Janis Papanagnou on Mon Mar 4 22:00:00 2024
    On Mon, 4 Mar 2024 08:12:33 +0100, Janis Papanagnou wrote:

    Why should vi clones be called "vim"?

    All with “vim” somewhere in their names:

    https://vi.stackexchange.com/questions/24459/can-you-use-neovim-in-a-gui-like-mvim-or-gvim-mac-os-x
    https://www.reddit.com/r/vim/comments/dct9ry/what_is_the_difference_between_vim_gvim_and_neovim/?rdt=38898
    https://news.ycombinator.com/item?id=27291799

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Janis Papanagnou@21:1/5 to Lawrence D'Oliveiro on Tue Mar 5 02:25:15 2024
    On 04.03.2024 23:00, Lawrence D'Oliveiro wrote:
    On Mon, 4 Mar 2024 08:12:33 +0100, Janis Papanagnou wrote:

    Why should vi clones be called "vim"?

    All with “vim” somewhere in their names:

    Why this red herring now? - In response to Andreas' hint about *Vi*
    you had said: "Aren’t they all called “vim” nowadays?"

    In case you are interested in the typical taxonomy[*]...
    It started with ex/vi, then there were Vi-clones (own implementations
    or approximations or extensions of Vi), Vim as being a prominent one.
    There's were/are lot of Vi clones (stevie, elvis, vile, nvi, and more).
    There's a Vim branch neovim (that might or might not get relevance in
    future now that Bram had died), I don't know of mvim, and gvim is just graphical Vim.

    It should be obvious to name any clone according to the functional base
    or code base the clone is comparing with or is based on.

    Janis


    https://vi.stackexchange.com/questions/24459/can-you-use-neovim-in-a-gui-like-mvim-or-gvim-mac-os-x
    https://www.reddit.com/r/vim/comments/dct9ry/what_is_the_difference_between_vim_gvim_and_neovim/?rdt=38898
    https://news.ycombinator.com/item?id=27291799


    [*] "typical", because no one can prevent anyone to name a tool myvi
    or myvim with or without any reference to vi and vim respectively.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to Janis Papanagnou on Tue Mar 5 03:22:47 2024
    On Tue, 5 Mar 2024 02:25:15 +0100, Janis Papanagnou wrote:

    Why this red herring now? - In response to Andreas' hint about *Vi* you
    had said: "Aren’t they all called “vim” nowadays?"

    Nobody seems to use any editor called “vi” any more.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Janis Papanagnou@21:1/5 to Lawrence D'Oliveiro on Tue Mar 5 06:42:01 2024
    On 05.03.2024 04:22, Lawrence D'Oliveiro wrote:

    Nobody seems to use any editor called “vi” any more.

    You again seem to know everyones habits? (I don't.)
    But I'm sure this is true for the most (all?) free
    Unixes at least.

    Personally I edit my files with "vi" on my system.
    Since I am using Linux this "vi" is of course Vim.

    But I wouldn't expect that commercial Unixes come
    with Vim. (Please CMIIW; I have meanwhile decades
    to work on commercial Unixes and maybe things have
    changed. Anyone who knows?)

    Anyway, the taxonomy should be made clear; it's a
    *big* difference if you have a yet still powerful
    but (in comparison to Vim) restricted Vi as the
    functional base of a clone, or whether you have a
    Vim.

    BTW, to my knowledge there had been Vi clones on
    Windows, too. In a document I wrote some decades
    ago I find (besides the ones I mentioned upthread)
    also calvin, elwin, lemmy, viper - some (or all?)
    may be or have been available on Windows or DOS?

    Janis

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to Janis Papanagnou on Tue Mar 5 07:10:22 2024
    On Tue, 5 Mar 2024 06:42:01 +0100, Janis Papanagnou wrote:

    Personally I edit my files with "vi" on my system. Since I am using
    Linux this "vi" is of course Vim.

    Like this?

    ldo@theon:~> ls -l /usr/bin/vi
    lrwxrwxrwx 1 root root 20 May 5 2023 /usr/bin/vi -> /etc/alternatives/vi
    ldo@theon:~> ls -l /etc/alternatives/vi
    lrwxrwxrwx 1 root root 17 May 5 2023 /etc/alternatives/vi -> /usr/bin/vim.tiny

    So even when you think you’re using “vi”, you’re still actually using “vim”...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Janis Papanagnou@21:1/5 to Lawrence D'Oliveiro on Tue Mar 5 17:08:51 2024
    On 05.03.2024 08:10, Lawrence D'Oliveiro wrote:
    On Tue, 5 Mar 2024 06:42:01 +0100, Janis Papanagnou wrote:

    Personally I edit my files with "vi" on my system. Since I am using
    Linux this "vi" is of course Vim.

    Like this?

    ldo@theon:~> ls -l /usr/bin/vi
    lrwxrwxrwx 1 root root 20 May 5 2023 /usr/bin/vi -> /etc/alternatives/vi
    ldo@theon:~> ls -l /etc/alternatives/vi
    lrwxrwxrwx 1 root root 17 May 5 2023 /etc/alternatives/vi -> /usr/bin/vim.tiny

    So even when you think you’re using “vi”, you’re still actually using “vim”...

    Yes, exactly. This is possible because Vim is in practice a superset
    of Vi, and having a program that implements Vi functionality called
    "vi" is defined as part of the POSIX utilities.

    Only that I don't think that I'm using Vi, as I said, only that it's
    called "vi". But others may think so. Mind that it's a reply to what
    you said: >>> Nobody seems to use any editor called “vi” any more.

    But again, this is Linux and the commercial world had been different.
    On Linux you have full Vim functionality available when using "vi".

    Janis

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Janis Papanagnou@21:1/5 to Lawrence D'Oliveiro on Tue Mar 5 17:19:30 2024
    Just noticed...

    On 05.03.2024 08:10, Lawrence D'Oliveiro wrote:
    lrwxrwxrwx 1 root root 17 May 5 2023 /etc/alternatives/vi -> /usr/bin/vim.tiny

    On my system it is: /etc/alternatives/vi -> /usr/bin/vim.gnome
    This may be important if I inspect the file sizes...

    2392032 /usr/bin/vim.gnome
    777056 /usr/bin/vim.tiny

    Not sure what the difference is; some restricted functionality in
    the .tiny version or maybe some graphical support in .gnome?

    Janis

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony Howe@21:1/5 to Lawrence D'Oliveiro on Wed Mar 6 10:20:13 2024
    On 2024-03-04 22:22, Lawrence D'Oliveiro wrote:
    On Tue, 5 Mar 2024 02:25:15 +0100, Janis Papanagnou wrote:

    Why this red herring now? - In response to Andreas' hint about *Vi* you
    had said: "Aren’t they all called “vim” nowadays?"

    Nobody seems to use any editor called “vi” any more.

    I personally use a POSIX and historically compatible vi(1). Nvi by Keith Bostic
    is proof of concept and faithful reproduction of Billy Joy's original vi(1). Nvi comes stock (along with ed(1)) on every BSD I use (FreeBSD, NetBSD, OpenBSD,
    GhostBSD). One of the first things I do with a new Linux box is uninstall Vim and install Nvi (and ed) from package or source. So yes, I use a proper vi.

    --
    Anthony C Howe
    achowe@snert.com BarricadeMX & Milters http://nanozen.snert.com/ http://software.snert.com/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Geoff Clare@21:1/5 to Janis Papanagnou on Thu Mar 7 13:40:47 2024
    Janis Papanagnou wrote:

    On 05.03.2024 04:22, Lawrence D'Oliveiro wrote:

    Nobody seems to use any editor called “vi” any more.

    Personally I edit my files with "vi" on my system.
    Since I am using Linux this "vi" is of course Vim.

    I am using Linux and the "vi" on my system(s) is not vim, it is nvi.

    $ readlink /usr/bin/vi
    /etc/alternatives/vi
    $ readlink /etc/alternatives/vi
    /usr/bin/nvi

    But I wouldn't expect that commercial Unixes come
    with Vim. (Please CMIIW; I have meanwhile decades
    to work on commercial Unixes and maybe things have
    changed. Anyone who knows?)

    MacOS has vim as its POSIX conforming vi (certified conforming to
    UNIX 03).

    Solaris 11.4 has vim in addition to a "real" (SVR4-derived) vi.
    Which one you get if you type "vi" depends on your PATH:

    $ readlink /usr/bin/vi
    vim
    $ type vi
    vi is a tracked alias for /usr/xpg7/bin/vi
    $ getconf PATH # standards-conforming PATH /usr/xpg7/bin:/usr/xpg6/bin:/usr/xpg4/bin:/usr/bin:....

    --
    Geoff Clare <netnews@gclare.org.uk>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)