I get your point. Since a .tar.zst
file can be handled natively by tar
, using .tzst
instead does make sense.
I get your point. Since a .tar.zst
file can be handled natively by tar
, using .tzst
instead does make sense.
Yep, my Sway config has
input type:touchpad natural_scroll enabled
I know; I’m not talking about ./
. I put the slash outside the inline codeblock in the parent comment.
My shell is setup with a chdir hook to [[ -r. /.autoenv.zsh ]] && . ./.autoenv.zsh
.
(Edit: Jerboa is bugged with “&” in codeblocks, that should be a “&&”, not &&
)
(NOTE: A lot of my more interesting “aliases” are actually short functions, but I’m keeping myself to alias
.)
Some of mine that I haven’t seen yet:
# Simple python calculator
alias pycalc='python3 -ic "
from math import *\nimport cmath as C
try:
import numpy as np
except:
pass
i, j = 1j, 1j
"'
# Defaults
alias cp='cp --interactive --reflink=auto'
alias gcc='gcc -fdiagnostics-color=auto'
# Lemmy doesn't handle ampersands in codeblocks correctly
alias rg='rg --max-columns=$((COLUMNS > 60 && ! ZSH_SUBSHELL ? COLUMNS - 30 : 0))'
alias rj='rg --json'
alias rm='rm -s'
alias rscp='rsync -azP --human-readable --info=flist0,progress2,stats1'
alias rust-c='rustc --out-dir build -O'
# Shorter forms
alias g=git
alias v=$VISUAL
alias py=python
alias jfeu='journalctl --user -xfeu'
alias sys='systemctl --user'
alias Jfeu='journalctl -xfeu'
alias Sys=systemctl
# Desktop stuff
alias trash='gio trash'
alias ud=udisksctl
alias y=wl-copy
alias Y='wl-copy -p'
alias p=wl-paste
alias P='wl-paste -p'
# Colorize with acolor/grc
alias GRC='grc -es'
alias LA='acol ls -lFAhb --color'
alias LS='acol ls -lFhb --color'
alias df='GRC df -hT'
alias dig='GRC dig'
alias docker='GRC docker'
alias docker-machine='GRC docker-machine'
alias env='acol env'
alias lsblk='acol lsblk'
alias lsmount='command mount | rg --color=never "^/" | acol -i -o mount'
alias lspci='acol lspci'
alias mount='acol mount'
alias nmap='acol nmap'
alias ping='GRC ping'
alias ps='GRC ps --columns $COLUMNS'
alias traceroute='GRC traceroute'
That would make my shell unusable, since some plugins use .
/source
.
I have it on Steam Deck since it can be launched with a CLI argument to force a 1280x800 window.
Vivaldi pretends to be Edge when visiting Bing to unlock GPT-4, and prefer that to Edge on my other devices. (Secondary to Firefox, ofc)
Well, those requires D-Bus. The wlroots project decided early on to support non-dbus software stacks, so wlroots compositors expose Wayland protocol extensions which could either be used directly or wrapped by the xdg-desktop-portal-wlr
daemon.*
*(Well… many wlroots devs argued that the ecosystem should have chosen WP extensions instead of dbus, but I think most relented when Pipewire entered the equation.)
I was curious about what they’d say next. Their argument is “most users don’t need more than Xorg, so it’s ‘silly’ to expect investment in Wayland”.
I found some agreement in “as more people need Wayland features, investment will grow”, especially with the Valve and KDE/wlroots/gamescope. Also Automotive Grade Linux embracing libweston.
14 years later the need is slowly growing so the support is slowly growing
Yes! I agree wholeheartedly. Adoption has been slow because Wayland did not meet the needs of most people more than Xorg did. Cinnamon isn’t moving any time soon because the value-add isn’t enough for the average desktop user.
But…
build something that people need
People have needed HDR and VRR for years. HDR is essential for professionals in video and image editing. They needed Wayland years ago, and it was being built with them in mind, not just the average desktop user in 2012.
Not every feature is used by every user of that software. I used X-forwarding over SSH once, ever. It did not add any value to me. SSH forwarding adds no value to the average user either. But it is essential to someone.
They are becoming more essential by the day. HDR and VRR is supported by just about every graphics card for the last 5 years, and displays which support both can be found for $200 or less. Valve had a reason to add HDR support to Gamescope/Steam Deck; it is a highly requested feature.
I will agree with you on one point: Xorg is not bad code. Xorg is an awesome project, and has developed and changed to the needs of users exceedingly well for decades. But X11 itself is tech debt. The first ten years of Wayland were spent paying that debt off (while simultaneously continuing Xorg development).
If the features aren’t what you need, then Wayland wasn’t built to support you today. But you might find yourself in 6 years looking at a gorgeous HDR display which works out-of-the-box on your favorite Linux distro thanks to Wayland.
features
It was the inability to add features like mixed refresh which caused Xorg devs to push for a new protocol. Otherwise it would be yet another series of janky patches to break assumptions made in a 40 year old protocol.
Other devs have been working on it. Valve’s contributions to wlroots, KDE, and gamescope can’t be understated.
type -p
is a shell builtin though, and one character shorter :)
Although you may prefer tool=$(command -v tool)
Comparing Arch’s base + base-devel is kinda unfiar, there’s only 54 packages total there.
awk
for the modern age
Valve should get on this for gamescope, imagine Steam Deck doing a system update without closing your game.
My experience is still pretty good there. Back in ~2015 my family got an USB WiFi card which needed an out-of-tree module, which the manufacturer had on Github, complete with DKMS instructions. It was upstreamed after about a year, though!
The only completely unsupported device I’ve had is my laptop’s fingerprint sensor.
I think this is a good default.
An impossible dream of mine would be to check a list of devices with haptic touchpads, and disable tap-to-click on those.
Yep, I’m finding about half of my Reddit usage satisfied. I’ve got all the technical talk I want, but no gaming or writing communities.
I look forward to the day that Synapse is deprecated in favor of Dendrite or Conduit.
If you use EndeavourOS, know that you shouldn’t ask for support on the Arch forums, its a policy they have.