tell me the most ass over backward shit you do to keep your system chugging?
here’s mine:
sway struggles with my dual monitors, when my screen powers off and back on it causes sway to crash.
system service ‘switch-to-tty1.service’
[Unit]
Description=Switch to tty1 on resume
After=suspend.target
[Service]
Type=simple
ExecStart=/usr/local/bin/switch-to-tty1.sh
[Install]
WantedBy=suspend.target
‘switch-to-tty1.service’ executes ‘/usr/local/bin/switch-to-tty1.sh’ and send user to tty1
#!/bin/bash
# Switch to tty1
chvt 1
.bashrc login from tty1 then kicks user to tty2 and logs out tty1.
if [[ "$(tty)" == "/dev/tty1" ]]; then
chvt 2
logout
fi
also tty2 is blocked from keyboard inputs (Alt+Ctrl+F2) so its a somewhat secure lock-screen which on sway lock-screen aren’t great.
I have a folder full of scripts tied to aliases that fix various things when they go wonky, and I’ve long since forgotten what any of them do. I just know if
xxx
app stops working, I typefix_xxx
into the terminal and then it does a bunch of stuff and then it works again lol.Also I have a bunch of aliases tied to common tasks, like
e1
= reboot,e2
= shutdown etc. I have no idea where that habit came from.I dare you to try
grep -Irn alias
in your home dir.I’m not even sure what that would do! Presumably list every time the word alias appears in every file across the whole home directory or something like that?
Rtfm!
No, seriously, -I avoids binaries, -r recursively, -n print matching file and line number.
Alright, I’m gonna try it and see how long this takes!
edit: about 8 minutes. Not as spectacular as I’d hoped lol
If you have games there, yeah. Ripgrep is way faster. But grep is good enough in most cases.
Btw, did you find your aliases?
I did! I know where they are and which scripts they point to, but as for going into the scripts and trying to remember what they’re actually doing… I’ll get to it some day lol
now im really curious about that
xxx
app…