[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange behaviour with custom set HOME env variable

From: Matus Kmit
Subject: Re: Strange behaviour with custom set HOME env variable
Date: Sun, 8 Apr 2012 16:46:59 +0200

Hi Peter

Thanks for all those tips. I will try what suits me best.


On Tue, Apr 3, 2012 at 10:41 AM, Peter Dyballa <address@hidden> wrote:
> Am 2.4.2012 um 16:02 schrieb Matus Kmit:
>>>> Among them, as already explained in my previous email, I am currently
>>>> using:
>>>> 1. "site-start.el" which sets my custom HOME environmental variable
>>>> (path to my Dropbox folder)
>>> This is a Bad Thing®. Site-start.el is meant to adapt GNU Emacs to the 
>>> system it runs on. It's not really an user choice.
>> Which would be a better solution? I need to set that variable before
>> emacs loads my init file, so that it knows that it is located in
>> Dropbox.
> Other ways are to use shell aliases or shell functions. You're not limited to 
> typing the whole command every time but can use an "abbreviation". On the 
> command line you can make GNU Emacs execute code, so maybe this works:
>        emacs --eval '(setq user-init-file 
> "/home/nimaai/Dropbox/emacs/emacs-home-dir/.emacs")' &
> The ELisp code can also be put into a file:
>        emacs --script my-startup.el &
> The most easiest way should be this one (I also use, to set up some minimal 
> customisation for debugging):
>        emacs -q -l /home/nimaai/Dropbox/emacs/emacs-home-dir/.emacs &
> Instead of -q you could also use -Q.
> These lengthy commands can then be put into a shell alias (or function) to 
> save some typing.
> --
> Greetings
>  Pete
> Got Mole problems?
> Call Avogadro 6.02 x 10^23

reply via email to

[Prev in Thread] Current Thread [Next in Thread]