• 0 Posts
  • 126 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle


  • Let’s give it a shot. I live in the suburbs of Lincoln, Nebraska, which is an average-sized college town in the US (about 300k residents):

    • Nearest convenience store: 1.1 miles/1.7km (we often do walk there, takes about 20 minutes)
    • Nearest chain supermarket/big supermarket (they are often one in the same here): Target @ 1.5 miles/2.4km
    • Bus stop: 1.3 miles/2.1km
    • Nearest park: 0.6 miles/965m
    • Nearest public library: 3.5 miles/5.6km
    • Nearest train station: 9.1 miles/14.6km (we don’t really use trains much at all in the US, though)


  • Interactive rebase? There’s no GUI that actually does that well, if at all. And it’s a massive part of my daily workflow.

    The CLI is far, far more powerful and has many features that GUIs do not.

    It’s also scriptable. For example, I often like to see just the commits I’ve made that diverge from master, along with the files changed in each. This can be accomplished with git log --oneline --stat --name-status origin/master..HEAD. What’s more, since this is just a CLI command, I can very easily make a keybind in vim to execute the command and stick it’s output into a split window. This lets me use git as a navigation tool as I can then very quickly jump to files that I’ve changed in some recent commit.

    This is all using a standard, uniform interface without mucking around with IDE plugin settings (if they even can do such a thing). I have many, many other examples of scripting with it, such as loading side-by-side diffs for all files in the worktree against some particular commit (defaulting to master) in vim in a tabpage-per-file, which I often use to review all of my changes before making a commit.










  • I dunno, I ended up blocking the instance way before I knew about their reputation (like, when I first joined Lemmy) because all of the users their kept posting the most unhinged shit.

    I have definitely seen blatant apologism for China/Russia from them.

    FWIW, I’m much further left than your average Democrat (I consider myself a leftist/anarchist). I personally don’t consider what I’ve seen from them to be very “left”, just authoritarian.


  • ! 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.





  • 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).