1. 12

Vim, being a command-line tool, comes with all the modular conveniences this entails - such as the ability to respond to signals, to be opened with special flags, or to receive input from a unix pipe. See how these features can be integrated into your everyday editing workflows.

  1.  

  2. 15

    Ctrl-Z and fg are shell features and have nothing to do with vim. Also the “-” as a sign to read from stdin is a very common pattern in unix and many tools understand this. The “**” thing looks like fzf and has also nothing to do with vim itself. I know that I am splitting hairs a bit here, but I feel we should attribute things to the right tools and not conflate shell features with vim.

    1. 10

      Also “nvim” is neovim - not Vim!

      1. 2

        I didn’t mean to mislead so much as impress VS-Code users / command-line-shy types with the might of what you can do with vim’s nimble CLI :)

        1. 1

          And here I thought I was a fool for installing fzf, but no - it looks like ** simply expands for the current directory

        2. 3

          also related: just use / to search or :tag to jump to ctags on vim’s own prompt without needing to exit vim first :P

          Opening a file with colon and line number doesn’t work for me; i think some plugin is mentioned but i don’t get the name. I would love that feature, but much rather have this on the :e command within vim, to copy paste error locations. For that I use :make and the :clist command family instead.

          I’m always thrilled to find out hidden vim gems i was ignorant about, but this one wasn’t it.

          1. 1

            Vim-fetch is what you’re looking for :)

            BTW I’ve got show-notes for all the plugins etc. used over here: https://www.semicolonandsons.com/episode/Vim's-Versatile-CLI

            1. 1

              found the file:line plugin that works from cmdline and :e, so i did get something from it after all <3

              https://www.vim.org/scripts/script.php?script_id=2184