My fellow nerds: a question about your personal machines:
What is your favourite quality-of-life tweak you've made to your system?
An alias? A utility, a setting, something in .bashrc or ~/bin?
I'd like to know.
My fellow nerds: a question about your personal machines:
What is your favourite quality-of-life tweak you've made to your system?
An alias? A utility, a setting, something in .bashrc or ~/bin?
I'd like to know.
I remap Caps as my Compose key
$ setxkbmap -option compose:caps
and use it DOZENS of times every day.
It's especially handy if you create your own ~/.XCompose file where you can include the system one
include "%L"
and then define your own atop it, so I have added some custom arrows, vertical ellipsis, the "Enter" key (⏎), and a number of emoji like
<Multi_key> <greater> <colon> <parenright> : "😈" U1F608 # SMILING FACE WITH HORNS
Also, it pays to skim through all the `<Multi_Key>` items in the system file to learn what's in there. Em- and En-dashes, horizontal ellipsis, diacritics, superscript/subscript numbers, and so much more.
@mhoye Definitely my aliases. When I discovered those it changed the command line for me.
The best ones are just being able to type the name of one of my machines and have it ssh straight into it. Another one does the ssh but then runs a command to get the temp (it can get hot) and exits.
And I can never remember the command that this alias runs:
alias ns='netstat -alnp --protocol=inet | grep -v CLOSE_WAIT | cut -c-6,21-94 | tail -n +2'
but I use that a lot.
While I use a few aliases, I find that shell-functions are more predictable, especially with how they handle arguments. But yes, such time-savers, especially for convoluted/obtuse arguments.
I really need to move some of my common shell-history items into more static/persistent entries as aliases/functions in my shell RC file so I'm not relying on history quite so much 😬
@stevenixon @mhoye yeah mine is `rbash` (remote bash) and it takes the name of a system and name of an environment as arguments. Handles ssh or kubectl or whatever else under the hood to just get me bash on some server, container, or pod.
`rbash cms production`
heh. Using a super simple window manager like LXQt. No fancy animations, no transparency, just simple, highly responsive controls and displays. Is it perfect? No. But, man is it less distracting.
Not fully related, but I will say that the fn
key is remarkably well named.
As in:
"Dammit! Where the heck is the fn
key!?"
@mhoye I pull my shell configuration into a separate folder, so that I can organize it better. This makes it so you can conditionally load it in the actual shell RC file, with minimum edits.
EG: I have a `$HOME/.bash.d` folder with files used for various tools (asdf, aliases, work-specific tools, etc.), then do an `if [[ -d "$HOME/.bash.d" ]]; then` and source each file present.
@mhoye
1. Running Linux
2. Cinnamon DE (although Plasma 6/Wayland is okay too)
3. Firefox (based) browser with uBlock and uMatrix
All the other stuff is secondary benefits, although Arch based distro and the AUR rank at the top of those secondary benefits.
@mhoye this one alias:
alias l='ls -Nlrt'
then: install micro, the text editor
then: create ~/bin for all the weird little toadstools that accrue on my systems.
@mhoye i have `h` aliased[0] to a history of directories, navigable with fzf[1].
i have various uses of fzf sprinkled all over my setup, and it's been a huge improvement in everything i've applied it to.
[0]. https://code.p1k3.com/gitea/brennen/bpb-kit/src/branch/main/home/.sh_common#L169
[1]. https://github.com/junegunn/fzf
@dianaprobst @dcoderlt @mhoye
People don't understand the constraints of the typefaces (I refuse to use the word font for this) were under at the time.
It had to function at very low resolutions on computer screens AND look good in print AND line up the columns of text the same in either display format, while maintaining legibility.
The idea that it was possible to use a "handwritten" style font to display menus and title bars was wild, and I used it as a system typeface at one point.
@mhoye
As an experience designer that works with several & various development teams - using ephemeral containers with mounted directory as prototype/development environments, effortlessly using different versions of the same programming language and different languages as long as there’s memory and storage.
Also have a “remove crud.sh” script that clears unneeded cache directories and storage-guzzling auto-update applications.
I work with multiple dev teams that require arduous & OS specific instructions for development environment setup for UI + UI API microservices, where I’m reviewing UI code or even writing/updating the CSS to reflect the intended experience.
By running that code in an ephemeral container (not image) with git repo directory mounted, I completely skip “arduous setup instructions”. I also can run a multi-project “polyglot” language set up.
I have a presentation on this approach from 2017.