I’m reconsidering my terminal emulator and was curious what everyone was using.

  •  chenxiaolong   ( @chenxiaolong@lemm.ee ) 
    22•2 years ago

    I primarily use Alacritty. I spend quite a lot of time running things that produce ludicrous amounts of output (eg. compiling Android from source). Out of 10 or so terminal emulators I’ve tested earlier this year, it was the only one that didn’t use 100% CPU displaying all that output, staying in the low single digits.

    I’d prefer to use Wezterm because I like its lua configuration system and the builtin pane splitting, but with my workload, I still run into issues where its CPU usage shoots to 100% and becomes non-responsive for a while. (That said, it’s already a lot better than before. I try to report any issues I can reliably reproduce and Wez has been wonderful about fixing them.)

  •  pimeys   ( @pimeys@lemmy.nauk.io ) 
    20•2 years ago

    I use foot together with foot-server. The client opens in less than a millisecond, and I usually have tens of terminal windows open at the same time. Tabbing comes from the window manager.

  •  silva   ( @silva@beehaw.org ) 
    17•2 years ago

    When I’m using a tiling window manager, I use kitty, because I like its speed and support for font ligatures. When I’m using a Desktop Environment like Gnome or KDE I usually don’t use the terminal at all, but if I need it, I use the default emulator.

    •  Crul   ( @Crul@lemm.ee ) 
      4•2 years ago

      Sorry for the off-topic question, but I’m still trying to wrap my head around basic linux concepts: you use “tiling window manager” and “desktop environment” as if they were mutually exclusive options. What’s the relationship between them?

      Thanks!

      •  silva   ( @silva@beehaw.org ) 
        9•2 years ago

        I don’t know if I’m correct, but in my head, a window manager JUST manages windows. Gnome and KDE also manage windows, but they also contain applications for settings, printing, etc. Desktop Environments also have window managers, but they have more applications on top.

        •  Crul   ( @Crul@lemm.ee ) 
          2•2 years ago

          So, just to check I understood:

          • “[Tiling] Window Managers” are a very specific tool.
          • “Desktop Environments” are broader tools that (may?) contain Window Managers.

          Now… the next questions (if you have the patience :P) are:

          • is is possible to use a Window Manager without a Desktop Environment?
          • how does this influence your choose for the terminal emulator? Ó_ò

          Thanks for the answers!

          •  silva   ( @silva@beehaw.org ) 
            3•2 years ago
            • Yes, you can absolutely use a WM without a DE. A DE is usually just a set of preconfigured and pre-installed applications. If you use a WM like i3 etc. you just get something that draws windows, and no settings and bluetooth applications
            • It influences my choosing because window managers usually don’t come with a terminal, and you have to manually install a terminal emulator. But on desktop environments I use the default terminal, although I could also install kitty.
            •  Crul   ( @Crul@lemm.ee ) 
              2•2 years ago

              Oooh… I see. I didn’t understand how broad the Desktop Env really are. Is not that they manage “a lot of things regarding the desktop and windows”… is just like a bundle of apps.

              Now it’s starting to sound like a sub-distro inside the distros, but I think this is a good point to stop bothering you. Thanks again!

      •  LeFantome   ( @LeFantome@programming.dev ) 
        5•2 years ago

        Window Managers manage windows as the name suggests and control how they are displayed and interacted with. A window manager is one component of a desktop environment which provides other facilities like compositors, task bars, status trays, task switchers, configuration applets, virtual desktops, and perhaps some default applications for basic things like terminal, file management, text editing, connection management, and image viewing. Some desktop environments feature extensive plug-in systems ( extensions ) and vast application ecosystems.

        In the early days of Linux, there were no “desktop environments” and you would run a window manager directly over the window server ( eg. X11 ) with applications running directly over the WM. Proprietary UNIX introduced desktop environments like CDE, OpenWindows, and NeXTstep but, as they were proprietary, Linux lacked them. This changed with the advent of KDE and GNOME soon after. These days, the vast majority of Linux users are working with a desktop environment ( probably still one of these two though there are now others ).

        A timing window manager in particular is a window manager that allows auto arranging and resizing applications to share the screen ( typically using keyboard commands ). The goal of a tiling window manager is that application views do not overlap and that the full desktop space is used efficiently. A floating window manager in contrast allows windows to overlap and leaves positioning, resizing, visibility, and focus up to the user. The desktop itself may be plainly visible and may even have clickable icons or applets displayed on it. Interaction with windows in a floating window manager is usually done with the mouse. Windows and Mac are examples of the floating metaphor so that is the one most of us are more familiar with. Any given window manager can incorporate both floating and tiling ideas and features but most WMs lean pretty heavily one way or the other.

        Technically, a window manager is just a special kind of application. In X11, it is not even required. You can run applications directly without one but, if you run more than one application, you will quickly understand the value of a window manager. The value of a full desktop environment is more a matter of preference. Most people welcome them or consider them essential. Others see DEs as bloat. The middle ground is assembling a desktop experience yourself from a group of applications you select for that purpose from the window manager up.

  •  theshatterstone54   ( @theshatterstone54@feddit.uk ) 
    12•2 years ago

    I use Kitty, because it works well on both X and Wayland, and is GPU accelerated. For some reason, Alacritty doesn’t display the fonts properly (Displays them much smaller on Wayland. Only program I have such issues with)

    Also Kitty is more widely packaged (for example on Debian based distros)

  •  kevincox   ( @kevincox@lemmy.ml ) OP
    10•2 years ago

    Personally I’ve been using gnome-terminal for quite a while and was fairly happy except that I needed to maintain gnome-terminal and libvte patches to get notification support. Having some sort of notification when a long-running command completes is very important to my productivity.

    I’ve been using Konsole but not fully happy.

    • No hyperlink support.
    • Selection is lost when my prompt updates (I have the time so that I know when I have started commands).

    I’ve been looking at other options but none-of them feel quite right.

    Alacritty:

    • No unlimited scrollback.

    Kitty:

    • Selection bug with updating prompt.
    • No unlimited scrollback.

    Wezterm:

    • No unlimited scrollback.

    Terminator:

    • Has this terminal group bar that I can’t get rid of.
    • No notification support.

    I realize that I am probably going to have to make a compromise (probably just go back to gnome-terminal with patches) but I figured it would be interesting to see what everyone else was using and make sure I didn’t miss something.

    To me the important features are:

    1. Unlimited scrollback.
    2. Notification support (ideally with the 777 Notify command, but if the terminal bell can make a notification that is fine).
    3. Clean UI. (I don’t use tabs so need to be able to hide the tab bar)
    4. Hyperlink support.
    •  Alex   ( @ultra@discuss.online ) 
      1•2 years ago

      You can use zellij for infinite scrollback. If ot takes too muxh space, use compact mode.

      Also, I use konsole and it does have hyperlink support, just control-click the links.

  •  hackris   ( @hackris@lemmy.ml ) 
    10•2 years ago

    Anything, but with tmux running inside. You can copy text even in a tty, split the terminal window, detach from and attach to tmux sessions, etc. I will never use a terminal for any moderately complex task without tmux again :)

      •  hackris   ( @hackris@lemmy.ml ) 
        2•2 years ago

        Copying in tmux (assuming default keybindings):

        1. Enter copy mode with Ctrl+b, [
        2. Position the cursor at the start of the text to be copied, press Ctrl+SPACE to start copying
        3. Position the cursor at the end of the text, press Alt+w or Ctrl+w to copy into the tmux buffer
        4. Press Ctrl+b, ] to paste, possibly into different pane :)

        By ‘copy’, I meant between different tmux panes/windows.

        If you open tmux on your host, split it into two panes and SSH into the server in one of them, then you can use this copy functionality. I’m personally not aware of a way to copy between a remote and local tmux session.

        •  Rescuer6394   ( @Rescuer6394@feddit.nl ) 
          2•2 years ago

          ah yes sorry i meant copy to system clipboard.

          i succeed in configuring vim so it uses the system clipboard on both local and remote sessions.

          i would like to do the same with tmux, but as you said too, it does not seem to be a way.

          •  𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍   ( @sxan@midwest.social ) 
            4•2 years ago

            You absolutely can. You just have to use a clipboard command as the copy/paste. Add this to your ~/.tmux.conf

            bind-key -T copy-mode-vi y send-keys -X copy-pipe-and-cancel "xsel -i -b"
bind-key -T copy-mode-vi Enter send-keys -X copy-pipe-and-cancel "xsel -i -b"

            or use your favorite cli clipboard command. Note that those are using the vi bindings; you might have to adapt the config.