From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: exec-path not changed in autostart
Date: Fri, 19 Dec 2014 23:13:25 +0100 [thread overview]
Message-ID: <87y4q39tkq.fsf@wanadoo.es> (raw)
In-Reply-To: 40f1582d-1ec2-463b-8624-5e92530d65c0@googlegroups.com
Xin Jin <zariskij@gmail.com> writes:
> On Friday, December 19, 2014 1:58:45 PM UTC-8, Xin Jin wrote:
>> On Friday, December 19, 2014 1:54:34 PM UTC-8, Xin Jin wrote:
>> > No, it doesn't. I added some paths to $PATH in .bashrc, and clearly they do not show up in exec-path by default.
>> >
>> > On Friday, December 19, 2014 1:46:31 PM UTC-8, Eli Zaretskii wrote:
>> > > > Date: Fri, 19 Dec 2014 13:09:19 -0800 (PST)
>> > > > From: Xin Jin <zariskij@gmail.com>
>> > > > Injection-Date: Fri, 19 Dec 2014 21:09:20 +0000
>> > > >
>> > > > I use the following code to add the paths from the shell environment to exec-path:
>> > > >
>> > > > (setq exec-path
>> > > > (append
>> > > > (split-string-and-unquote (getenv "PATH") ":")
>> > > > exec-path))
>> > >
>> > > Why do you need that? exec-path already includes the directories from
>> > > $PATH, so the above sounds redundant.
>>
>> Hmm, so is that the .bashrc is processed too slowly so that $PATH hasn't updated?
>>
>> But even if I add (sleep 10s && emacs24 --daemon), it still doesn't work. Maybe I should try longer.
>
> Even sleep 20s does not work.
It is not about of timing. The init scripts execute when the OS starts,
while your .bashrc executes when you log in. The OS will not allow you
to log in until all init scrips are finished executing.
next prev parent reply other threads:[~2014-12-19 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 21:09 exec-path not changed in autostart Xin Jin
2014-12-19 21:46 ` Eli Zaretskii
[not found] ` <mailman.16507.1419025590.1147.help-gnu-emacs@gnu.org>
2014-12-19 21:54 ` Xin Jin
2014-12-19 21:58 ` Xin Jin
2014-12-19 22:01 ` Xin Jin
2014-12-19 22:13 ` Óscar Fuentes [this message]
[not found] ` <mailman.16510.1419027237.1147.help-gnu-emacs@gnu.org>
2014-12-19 23:03 ` Xin Jin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4q39tkq.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).