As a long time Vimmer, I have recently started using Emacs out of sheer curiosity. I chose Doom Emacs as it has evil-mode enabled by default, and do not want to dive down the rabbit hole of configuring the editor from scratch (at least, not yet!).

After installing and enabling libvterm in Emacs, I am having a frustrating experience. I configured ZSH shell to use vi-mode keybindings which interferes with evil-mode whenever I press Esc or C-[.

After having searched a little, I came across a workaround to disable evil-mode when in vterm. But it is still not a smooth experience. For instance, when switching between buffers (C-w C-w).

I would like to know how others in the community tackled this problem. Is there a better solution to this problem? Or have you made peace with the aforementioned workaround? Or have you stopped using vterm entirely?

  • aport@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    Vterm was so integral to my workflow that I finally abandoned vim and learned the default key bindings.

    Totally worth it too. I got rid of so many extra packages adapting things to evil mode

    • AusatKeyboardPremi@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      9 months ago

      That’s an extreme workaround. How do you feel about abandoning the vim motions? Does emacs way of moving and editing stand up to vim motions?

      One of the reasons I liked vim motions is that I find it very logical to move around and edit text.

      I find it weird that one has to keep holding one or two modifiers to unleash true power of Emacs. Perhaps, that’s just my bias.

        • AusatKeyboardPremi@lemmy.worldOP
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          9 months ago

          I never really tried using incremental search (avy or vim-easymotion) for minute navigation. I will certainly try this approach without evil-collection, along with the package you suggested.

          But I can already see it being slightly more time consuming as in my experience with vim-easymotion (and similar plugins like vim-sneak), the “jump” labels aren’t really generated in a logical manner such that I can effortlessly predict the label for the word I intend to bring the cursor/caret to. :-S

          How’s your experience with using this for minute navigations?

          • nmtake@lemm.ee
            link
            fedilink
            arrow-up
            2
            ·
            9 months ago

            I stick with C-s (similar to vim’s /) because of the exact reason you said, and I’m happy with C-s.

            Please note that C-s <some characters> RET moves the cursor at the end of the target (/ moves it at the beginning). If you don’t like the behavior, see this post (I use C-s ... C-r RET in that case).

      • hajovonta@mastodon.online
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        @AusatKeyboardPremi
        It’s a mental burden to keep track of modes. That’s why people invented modifier keys in the first place. But I admit after a while there can be too much shortcuts and then something needs to be done about it. I recently transferred my less-often used shortcuts into hydras so I don’t need to remember them (and hydras resemble modal operations)

        In Emacs, there are no modes the user needs to be aware of when typing where the cursor is.

        @aport

        • AusatKeyboardPremi@lemmy.worldOP
          link
          fedilink
          arrow-up
          1
          ·
          9 months ago

          I read the paper in its entirety. Thank you so much for sharing it.

          I really like the insight shared therein. Specifically on how much thought goes into keybindings, or rather must go into keybindings.

          Unfortunately, I don’t think EXPRES is widely supported as the authors hoped.

          As intuitive and similar to vim motions EXPRES may be, I don’t want to configure keybindings every time I install a plug-in/module.