I’ve been using konsole (and iterm2 on my work mac) for most of my working career, but on the linux side, I’ve recently switched to Kitty, but now I’m wondering if I can finally get used to just using emacs on both.

Does anyone use emacs as their main terminal? Is there one better than ansi-term that supports modern features like libsixel?

I still can’t quite get used to the keybindings (like C-c twice for ^C) and some other weirdness.

  • aport
    link
    fedilink
    arrow-up
    8
    ·
    6 months ago

    I more or less live in emacs on my development machine, so vterm is my main terminal

      • Byter@lemmy.one
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        I’m not sure I understand your question.

        Eat has its own major mode which is used when you open a standalone buffer via the eat function.

        When it’s embedded in Eshell it mostly just does the right thing whenever you invoke a command that uses terminal control codes (e.g. htop) – and many of those can be closed with q, yes.

        I assume Eat is activated for any program listed in the eshell-visual-commands variable (but I’ll admit I don’t really understand how that works). The notable new minor modes present when I run htop in eshell are Eat--Eshell-Local and Eat--Eshell-Process-Running.

        • Makussu@feddit.de
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          Yeah i was just asking if you close your eat buffer with q. I really like having one button to open and close my terminal so thats why i asked. Thanks for the extensive awnser tho

      • kelvie@lemmy.caOP
        link
        fedilink
        arrow-up
        3
        ·
        6 months ago

        Thanks for the rec, my first impression is that it doesn’t really work well with evil-mode, but that may be my configuration error (as it is with emacs).

        • aport
          link
          fedilink
          arrow-up
          8
          ·
          6 months ago

          Vterm not working well with evil was actually my motivation to drop evil completely and embrace emacs key bindings.

          It was the best decision I made. I don’t perceive a any measurable impact on my ability to efficiently write code or edit text, but I’ve seen a significant improvement on my ability to use emacs in general

          • kelvie@lemmy.caOP
            link
            fedilink
            arrow-up
            3
            ·
            6 months ago

            I went the other way, I’ve used emacs key bindings for over a decade and switched to evil because it appears most things in doom emacs worked better.

            Magit is still a bit of a mess with evil, though, but is manageable.

            Maybe one day I’ll switch back again, but my fingers know both.

        • Shareni
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          It’s probably a configuration error.

          As far as I remember it was working fine like a year ago when I was trying to make my own config (just vterm and evil packages were required). At the time the Doom people were saying it was impossible due to how terminal emulation works. Now it’s mostly working in Doom unless you go over 1 line. If you do, you’re not in a good place since you can’t use ESC to jump between words.

  • AusatKeyboardPremi@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    This is a problem that I face too. I have not yet figured out how to smoothly move over my terminal workflows to vterm (running ZSH in vi mode).

    I even made a post here asking for suggestions but I have not found a graceful solution to it yet.

  • plugd@lemmy.sdf.org
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    Yes, I have been using eshell exclusively for the last 7 years. It does have a few drawbacks, but for me it’s definitely a win overall due to a) everything being in a buffer, b) being able to run both elisp functions and executables from the command line, and c) tramp.

    P.s. I chuckled a bit when you mentioned sixel graphics support as modern. :) Jokes aside, I have my own toy implementation of sixel graphics in elisp, so decent emacs support is probably out there already.