Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

On 02/01/11 07:11pm, Moritz Wilhelmy wrote: > Imagine different computers mounting home directories over NFS: probably not > all of them have the same set of applications. As this is not the default > case, > the sysadmin on these machines should be able to edit dmenu_run to fit his > needs. Have

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

Excerpts from Džen's message of Sun Jan 02 18:56:53 +0100 2011: > On 02/01/11 08:01pm, anonymous wrote: > > dmenu cache should be stored under $HOME because different users use > > different $PATH. > I guess this is the main reason why the location of the dmenu cache file > shouldn't be changed --

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

On 02/01/11 08:01pm, anonymous wrote: > dmenu cache should be stored under $HOME because different users use > different $PATH. I guess this is the main reason why the location of the dmenu cache file shouldn't be changed -- storing it outside $HOME doesn't make sense to me, it overcomplicates thin

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

Excerpts from Bjartur Thorlacius's message of Sun Jan 02 18:01:34 +0100 2011: > > Maybe /var/tmp/ would be a better choice than /tmp? > Or you know, /var/cache? /tmp and /var/tmp are world-writable and sticky, /var/cache and /var/run are not. > For sockets, /var/run, which is always wiped on boot,

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

On Sat, Jan 01, 2011 at 06:04:45PM +, Bjartur Thorlacius wrote: > On 12/30/10, Anselm R Garbe wrote: > > On 30 December 2010 20:47, Jon Raphaelson wrote: > >> Attached is a patch to dmenu_path which (if enabled in the config.mk) > >> changes the cache file location to be XDG Base Directory Sp

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

$home/tmp

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

Quoting > System programs that maintain transient UNIX-domain sockets must place them > in this directory. I don't even know what 'transient' means, but this seems to apply to X IPC sockets. On 1/2/11, Bjartur Thorlacius wrote:

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

> Maybe /var/tmp/ would be a better choice than /tmp? Or you know, /var/cache? For sockets, /var/run, which is always wiped on boot, seems appropriate.

Re: [dev] [dvtm] Graphics in madtty.c

Now I understand the mystery better. At home I do get the graphics (using HEAD), but not at work. And the reason is that at home I use en_US.utf8 while at work I'm stuck with AIX boxes that don't have that locale installed, just en_US. So, the UTF8 code within dvtm prints the actual UTF8 graphic c

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

Excerpts from Troels Henriksen's message of Sun Jan 02 12:29:19 +0100 2011: > /tmp is wiped on system reboot, while you might like your dmenu cache to > live a little longer than that. Not necessarily. This depends on your distribution. A few examples: Slackware doesn't purge it by default, debi

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

On Sun, Jan 2, 2011 at 6:29 AM, Troels Henriksen wrote: > Anselm R Garbe writes: >> On Sat, Jan 01, 2011 at 06:04:45PM +, Bjartur Thorlacius wrote: >>> I think storing cache files under $HOME is even odder. $HOME is quite >>> often accessed over a network. Storing it under /var seems saner. >

Re: [dev] [dmenu] Patch for XDG Base Directory specification of dmenu_path

Anselm R Garbe writes: > On Sat, Jan 01, 2011 at 06:04:45PM +, Bjartur Thorlacius wrote: >> I think storing cache files under $HOME is even odder. $HOME is quite >> often accessed over a network. Storing it under /var seems saner. > > Or /tmp as it was in the earlier days. /tmp is wiped on sy