Re: [Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread Axel Liljencrantz
2009/2/24 Axel Liljencrantz > Just to throw my two öre into the discussion - I think both your > interpretations of the word cache are perfectly reasonable, and if is > entirely unclear to me from the standard which should be the correct one. > I'm going to fire off a question to the xdg mailing

Re: [Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread Axel Liljencrantz
Just to throw my two öre into the discussion - I think both your interpretations of the word cache are perfectly reasonable, and if is entirely unclear to me from the standard which should be the correct one. I'm going to fire off a question to the xdg mailing list and see if I can get a clarificat

Re: [Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread Martin Baehr
On Tue, Feb 24, 2009 at 03:16:52PM -0500, James Vega wrote: > I don't know of anything that automatically cleans ~/.cache (like is > commonly done with /tmp). it may not be now, but someone may come up with it, or even i may want to be able to easely wipe the cache to gain space. > I think the in

Re: [Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread James Vega
On Tue, Feb 24, 2009 at 09:00:15PM +0100, Martin Baehr wrote: > > If the intended purpose were logging (which implies auditing), then you > > wouldn't want to delete commands from the history. This currently > > happens in the fact that duplicate commands are elided from the history > > even if th

Re: [Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread Martin Baehr
On Tue, Feb 24, 2009 at 02:15:15PM -0500, James Vega wrote: > Considering its primary use is to avoid typing commands again and it's a > lossy store, it definitely seems like cache info to me. The impact from > removing ~/.config/fish/fish_history is minimal -- having to type a full > command inst

Re: [Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread James Vega
On Tue, Feb 24, 2009 at 05:36:02PM +0100, Martin Bähr wrote: > On Tue, Feb 24, 2009 at 11:09:58AM -0500, James Vega wrote: > > According to the XDG specification[0], "user-specific non-essential > > (cached) data" should be stored in $XDG_CACHE_HOME. This seems like a > > fitting place to put fish

Re: [Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread James Vega
On Tue, Feb 24, 2009 at 11:09:58AM -0500, James Vega wrote: > According to the XDG specification[0], "user-specific non-essential > (cached) data" should be stored in $XDG_CACHE_HOME. This seems like a > fitting place to put fish_history (and potentially fishd.$HOSTNAME). > > The attached patch d

Re: [Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread Martin Bähr
On Tue, Feb 24, 2009 at 11:09:58AM -0500, James Vega wrote: > According to the XDG specification[0], "user-specific non-essential > (cached) data" should be stored in $XDG_CACHE_HOME. This seems like a > fitting place to put fish_history (and potentially fishd.$HOSTNAME). i don't consider history

[Fish-users] [Patch] Store fish_history and fishd.$HOSTNAME under $XDG_CACHE_HOME

2009-02-24 Thread James Vega
According to the XDG specification[0], "user-specific non-essential (cached) data" should be stored in $XDG_CACHE_HOME. This seems like a fitting place to put fish_history (and potentially fishd.$HOSTNAME). The attached patch does this. The code changes to share/functions/__fish_config_interacti