Commit graph

7 commits

Author SHA1 Message Date
690df57f00
Set compromise XDG_RUNTIME_DIR if necessary
It's not ideal to set XDG_RUNTIME_DIR in your shell environment,
rather than from your session manager (or systemd, or whatever), since
then you can't reliably provide the same lifetime guarantees that
XDG_RUNTIME_DIR is supposed to have? But this is still preferable to not
having an XDG_RUNTIME_DIR at all, so I'm gonna go with it.
2022-07-12 11:05:11 +10:00
Danielle McLean
f06071e7c7
Drop fragile XDG_RUNTIME_DIR support
An XDG runtime directory cannot be provided reliably by the shell,
because it's supposed to have the same lifetime as the user's login
session, and the shell doesn't have a reliable way to keep track of that
lifetime. There are probably nonportable ways to get a conforming
directory, such as making a request to PAM, but PAM is supposed to set
XDG_RUNTIME_DIR itself anyway and also doesn't exist on Macs, which I
use most of the time.

My configuration isn't actually using XDG_RUNTIME_DIR anyway, so I don't
want to provide the misleading impression that a runtime directory with
proper behaviour conforming to the specification is definitely
available.
2021-09-22 10:27:09 +10:00
Danielle McLean
2018821e9f
Add support for XDG_STATE_HOME 2021-09-22 10:27:08 +10:00
f43d8a36fa
Clean up XDG_RUNTIME_DIR on last logout 2016-10-23 14:48:29 +11:00
735d3dac4d
Properly handle zsh init when $TMPDIR and/or $USER aren't available in the environment 2016-10-22 21:39:28 +11:00
ea4bacbb57
Actually create XDG_RUNTIME_DIR when the variable is set in zshenv 2016-10-22 21:12:09 +11:00
68d5f293cf
Using stow-rename, unhide all the files :3 2016-10-07 23:13:58 +11:00
Renamed from .zshenv (Browse further)