• 0 Posts
  • 26 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle










  • File-based navigation is often inefficient anyway (symbolic navigation is much better when you can), but if you do need it, that’s what fuzzy finders are for. Blows any mouse-based navigation out of the water.

    The only time a visual structure is useful is when you are actually just interested in learning how things are structured for whatever reason, but for that task, tree works just fine anyway.





  • ! is supported

    Vim’s command line, i.e, commands starting with :. The vanishingly few it does support are, again, only the most basic, surface-level commands (and some commands aren’t even related to their vim counterparts, like :cwindow, which doesn’t open the quick fix list since the extension doesn’t support that feature).

    Your experience is out of date.

    The last commit to the supported features doc was 5 years ago, so no, it isn’t. Seriously, you can’t possibly look at that doc and tell me that encompasses even 20% of vim’s features. Where’s the quick fix list? The location list? The args list? The change list? The jump list? Buffers? Vim-style window management (including vim’s tabs)? Tags? Autocommands (no, what it has does not count)? Ftplugins? ins-completion? The undo tree? Where’s :edit, :find, :read [!], and :write !? :cdo, :argdo, :bufdo, :windo?

    Compared to what vim can do, it is absolutely a joke.




  • I use a different tool, visidata. It’s especially nice when used as a psql pager.

    A text editor isn’t the right tool for editing tabular data, imo.

    As for KaTeX, what I would do is have a preview process running outside of vim that watches for changes in source files and re-renders. That’s the Unix way of doing things.


  • There’s many very basic features of vim that VsVim does not have (like… almost all command line commands), basic features which regular vim users use all the time.

    You seem to think that people using vim emulation is the norm and using vim itself is the exception and unusual… Which is very much not the case. The opposite is true, with VsVim users being a minority. It’s relatively novel among vscode users (most just use a mouse and maybe a small handful of built-in shortcuts), whereas vim itself is quite ubiquitous in the Unix world, with many Linux machines even providing it as the default editor. I know many vim and emacs users (including lots that I work with), and maybe 1 VsVim user (honestly not even sure if they do).