On 10/21/2014 07:44 PM, Yamaban wrote:
On Tue, 21 Oct 2014 19:30, Andrei Borzenkov wrote:
On Tue, 21 Oct 2014 19:21, Yamaban wrote:
On Tue, 21 Oct 2014 19:05, Claudio Freire wrote:
On Tue, Oct 21, 2014 at 1:15 PM, Erwin Waterlander wrote:
Andreas Schwab schreef op 2014-10-21 14:13:
Erwin Waterlander
writes: > Andreas Schwab schreef op 2014-10-21 12:55: >> Erwin Waterlander writes: >>> Andreas Schwab schreef op 2014-10-21 10:38: >>>> Erwin Waterlander writes: {snip} Well, TBH, I don't think putting an executable script in /tmp is a good idea either. I'm pretty sure the security guys will complain if done like that. I prefer something in home than in /tmp. In that sense, while ~/bin isn't the right place (I'd rather go for ~/tmp if it was standard), it's the safest choice ATM. The function only has to be really sure it's not clobbering any existing script there, and that folder permissions are not too permissive. Hmm, how about a folder "wcd" under "~/.local"?
$XDG_RUNTIME_DIR?
.local/ is in /etc/skel, and is conform to the freedesktop standards, OTOH, maybe the dir ~/.config/ is better, but you have to create it with mode 0700 if it isn't there already (not in skel).
The trouble with $XDG_* is that I can not get that to work well without having a valid Xsession. Not so good for remote work via ssh.
That is why I brought ~/.local/{program} and ~/.config/{program} into the discussion.
Yes, testing for /run/user/{UID}/ can also be done, but I still find systems without /run/user/ or /var/run/user/ structure.
I find backward compatibility and portability very important. Wcd is still compatible with the first version, and many shells are supported. I'm not optimizing for specific Unix (like) systems. regards, Erwin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org