On 1/2/11, Džen wrote:
> 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 dme
As I understand this discussion, having a config.mk flag for the cache
file sounds best to me, then the end user can decide if he likes the
default in $HOME/.dmenu_cache or somewhere else.
Also I believe that nfs mounted $HOME dirs are not that widespread
anymore and those who use this still shoul
On Tue, Jan 04, 2011 at 02:24:05PM +0100, Anselm R Garbe wrote:
> [...]
> Also I believe that nfs mounted $HOME dirs are not that widespread
> anymore and those who use this still should be able to change a flag
> in config.mk.
> [...]
Practically every university uses network mounted home directo
On 4 January 2011 14:56, Gregor Best wrote:
> On Tue, Jan 04, 2011 at 02:24:05PM +0100, Anselm R Garbe wrote:
>> [...]
>> Also I believe that nfs mounted $HOME dirs are not that widespread
>> anymore and those who use this still should be able to change a flag
>> in config.mk.
>> [...]
>
> Practic
You do both. Ideally you SSH into a machine running a NFS mounted home
directory on your own notebook. Of course, in that case, you're likely
not running dmenu, or even X.
Or that's my experience, at least.
On 4 January 2011 09:11, Anselm R Garbe wrote:
> On 4 January 2011 14:56, Gregor Best wro
On 1/2/11, anonymous wrote:
> dmenu cache should be stored under $HOME because different users use
> different $PATH. In my .profile I set
>
I like the notion of free-form $HOME, uncluttered of any autocreated files and
standardized (as in known at build-time). Rather, each user should have
subdi
