manually call the others
Yeah, most distros will set up source
chains to make things nicer for users.
manually call the others
Yeah, most distros will set up source
chains to make things nicer for users.
Yeah, I’d write this as a single update
script with options to update vimplugins
or update pkg
or update all
.
I see that you want it to be a function so you can get the chdir as a side effect, but mixing that with updating doesn’t make sense to me.
When in doubt, ~/.zshrc
. It’s the right choice 99% of the time. Otherwise, there’s a chance you fuck up scripts you’ve installed which assume no shell options have been changed in non-interactive contexts.
What kind of functions do you write which you share between your scripts? Generally if I’m wanting to reuse a non-trivial function, I extend the functionality of the first script instead.
Select the color which matches the steps before filenames ((non-)login and (non-)interactive), then follow that arrow the rest of the way. There’s more colors in Bash because Bash makes a distinction between remote and local shells.
Another way to look at the same data for Zsh (note: $ZDOTDIR
will be used instead of $HOME
if it’s defined at any step along the way):
File | neither | interactive | login | both |
---|---|---|---|---|
/etc/zshenv |
x | x | x | x |
${ZDOTDIR:-$HOME}/.zshenv |
x | x | x | x |
${ZDOTDIR:-$HOME}/.zprofile |
x | x | ||
${ZDOTDIR:-$HOME}/.zshrc |
x | x | ||
${ZDOTDIR:-$HOME}/.zlogin |
x | x | ||
${ZDOTDIR:-$HOME}/.zlogout |
x | x |
One confusion on the Bash side of the diagram is that you see branching paths into ~/.profile
, ~/.bash_profile
and ~/.bash_login
. Bash will use for ~/.bash_profile
, ~/.bash_login
, and ~/.profile
, in that order, and execute only the first one that exists and is readable.
CSS is turing conplete.
You could still NAT between v6’s though.
I care mostly about shell scripting, so I’m focusing on those bits. Via the HackerNews thread, mostly from a-french-anon:
That’s a latrine. They’re talking about a fancy light fixture.
Nope. If you open a nonexistent path and you have permissions to write to that directory, then that file is created.
Move the keyboard to the floor
*Thank you engineers who happen to be working at Facebook
Thought I’d check on the Linux source tree tar. zstd -19
vs lzma -9
:
❯ ls -lh
total 1,6G
-rw-r--r-- 1 pmo pmo 1,4G Sep 13 22:16 linux-6.6-rc1.tar
-rw-r--r-- 1 pmo pmo 128M Sep 13 22:16 linux-6.6-rc1.tar.lzma
-rw-r--r-- 1 pmo pmo 138M Sep 13 22:16 linux-6.6-rc1.tar.zst
About +8% compared to lzma. Decompression time though:
zstd -d -k -T0 *.zst 0,68s user 0,46s system 162% cpu 0,700 total
lzma -d -k -T0 *.lzma 4,75s user 0,51s system 99% cpu 5,274 total
Yeah, I’m going with zstd all the way.
Video files are just a bunch of zip files in a trenchcoat.
It used to use project folders, but due to confusion/user error was changed in 3.0.
It requires a phone number to log in. That already kills any hope for anonymity. I use it to message family and close friends, of which the fact that I’m messaging them is not surprising.
I run my Nextcloud behind Tailscale, and Caddy handles theTailscale https certs.
Excuse me, OCI container, we’re a runtime-agnostic family here.
I know that “Vanity Addresses” are a common thing for onion sites, and there are tools which generate tons of keys looking for prefixes. I haven’t seen such a tool for ssh host keys though.