When installing it, I found out that Terminal.app doesn’t support 24-bit color, which led me on a wild rabbit hole of discovery for a new terminal emulator that supported 24-bit color and didn’t suck. I am using the Ayu theme for fish and Vim. When tuned, kitty is twice as fast as the latter two, and tied with Sublime Text. Terminal.app and WezTerm follow closely behind, and kitty has a small lead over Alacritty and iTerm2. Out of the six terminal apps I tested on macOS, kitty has the lowest input latency at 29.2ms. So perhaps in the balance, it all evens out.Measuring terminal latency - Luke's Wild Website I will say that this management scheme may be over the top, but some folks like complicated terminal prompts. (You can learn more by exploring the dotfiles.) I put the decryption passphrase into a file, run make, and clean up everything with make clean. Whether I'm installing for the first time or updating existing dotfiles, I (of course) must have Ansible Vault, and to avoid having to install that everywhere, I put it in a container that I run with Docker, which I do have installed everywhere. All my secrets are stored in Git, encrypted with Ansible Vault. I find it useful to keep my secure data with everything else, and I solved this problem with Ansible Vault. Maybe you prefer your SSH config to be hidden, or maybe you're deploying credentials through a third-party system. Why all the tooling around security you ask? IT professionals and hobbyists alike need a robust way to put secure pieces of data on new systems. This pulls in my dotfile-specific deployment mechanism, which is also in GitHub. I use a series of Makefiles, hosted through GitHub, to manage my Mac setup. Beautifully complex dotfilesĬompared to my minimalist terminal, it's easy to see where I put my maximalist efforts: deploying my dotfiles, including my. I find it distracting in my terminals, so I enjoy those setups from afar. Some people enjoy transparency, and others prefer a lot of information on their prompts-from the time to the exit code and everything else. There is no doubt that I'm on the minimalist side, compared to some fancy terminals I've seen. So, my Bash PS1 is the boring cwd $, save for the Kubernetes context prefix. As an OpenShift Dedicated Site Reliability Engineer (SRE), I have to run commands with the appropriate context, and kubectx makes it easy to know where I am when I'm typing. The only fancy component I use is kubectx, which includes the current Kubernetes context. I don't include Git directory or exit code, and I only use a single line. I am one of those boring terminal prompt users. Free online course: RHEL technical overview. Learn more about what you can do with iTerm2 and enjoy the custom experience. To do so, navigate to Preferences > Profiles > Your Profile > Keys and enter the following. The first thing I do to make iTerm2 usable is to configure the Ctrl+Left and Ctrl+Right arrows to respect the classic terminal behavior of jumping to the start and end of a word boundary. For daily use, I prefer the Solarized Dark theme, but for presentations, I have a separate profile that enlarges the text and uses a plain black background with more vibrant colors. One of its key wins for me is that it's easy to transplant settings from Mac to Mac. Using iTerm2 on a Macįor a long time, my preferred terminal was the basic built-in Terminal.app, but I recently switched to iTerm2 because it has much better customization and profile support. There's no reason it can't port over to Linux (and it has!). Because of that history, I have a mix of features that will run on macOS but feel familiar to Linux users. At first, I felt a little shame, given my strong Linux background, but the Mac gives me a Unix-like shell and a great window manager. I have a confession to make: I have been a Mac user for more than 10 years now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |