I sort of understand (but don't agree with) the "design philosophy" behind this decision, but having to use something like tabbed for a basic feature creates a configuration mess and breaks things.
I had to use devilspie2 to remove window decorations from tabbed, because it doesn't have an option to remove them (Alacritty does).I tried tabbed as per suggestion, but it had a number of issues: Like I use Byobu/tmux for tabs (and I have multiple sessions, each with their own tabs), but I like to use my terminal app's tabs for different hosts (I don't want to nest local and remote tmux sessions, it gets messy fast). The default file comes when installing from source, or else can be copied from their github repository.It's a shame that Alacritty doesn't (and likely won't) support tabs. So first, I copied default alacritty.yml to my home directory. Then I found out that zellij can be launched with specific shell as an argument, and alacritty has an option to choose which shell to run in its configuration, which was great because I didn't want to change system default shell to nu (its still in beta). But quickly I found out I was wrong, as after starting nushell, it would first run zellij, which would keep running with default bash shell, and thus nushell would not actually run until I quit zellij. Initially I though setting the startup command in nushell to zellij would work, as startup command are run at start of each shell session. First, I wanted to integrate zellij with alacritty and nushell, so that it can manage multiple sessions.
Alacritty wsl2 install#
Installation process was quite straightforward, using cargo, and for nushell I had to install some other libraries for extra features using apt-get, but it went smoothly following the instructions on their pages :Īfter the installation, it was time to set it all up together, where I hit a couple of issues. Now I had to install and setup nushell and zellij. I had already installed alacritty as per their installation guide, as well as had starship set up. With this, I decided to convert all my terminal setup to Rust. This time it didn't felt as complex, as well as its features looked awesome (you can "preview" an image in the terminal itself 😲 😲 ). While checking out zellij, I remembered nushell, and went back to its site to check that out as well. (It is really well writter, do check it out!) I had checked out nushell about a year ago, and it seemed very interesting, but then I felt it was a little too complex, and I felt like I wouldn't need all the features it provides, so I didn't try using it.įew days back, I came across this retweeted by official Rust twitter account, which explained how zellij, a rust terminal workspace solved some of the performance issues. In this, I kept starship, as I really liked it, and it was quite useful. Unfortunately, I didn't want to install and setup another program to make it work, and I needed the functionality of multiplexed terminals in single window, rather than opening a new window each time which is why I moved back to gnome terminal emulator. I was used to doing this using the tabs of gnome emulator, and as Alacritty has clearly specified in its Readme, it has no intention of adding a terminal multiplexer, and users would need to use an external one such as tmux to do that (Which makes sense). The main reason I switched back was that a lot of times I ran multiple processes in parallel, such as running react frontend and node backend. Note : nushell and zellij both are still in their beta versions, and have few known issues, so if you want an absolutely reliable env, use bash/fish/zsh for shell and screen/tmux for terminal multiplexer.īefore changing this, I had already installed Alacritty and starship and had used it for few days before switching back to default gnome terminal emulator with starship. There were some hiccups in making it all work together, but in the end, my new setup is : I recently oxidized my terminal setup, by converting all of my terminal programs to rust based programs.
0 kommentar(er)
