From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Strangeness with devshell
Date: Thu, 21 May 2015 06:59:29 -0600 [thread overview]
Message-ID: <555DD6B1.8010608@mlbassoc.com> (raw)
I'm trying to run emacs inside of devshell. For some reason,
emacs can't find my startup files (emacs configuration). When
I look, I see very different startup behaviour for emacs when
I'm running in devshell vs. my normal shell (bash). Inside
the devshell it seems to be totally lost and I get messages
like "User gthomas has no home directory". Indeed when running
in the devshell, I can see that emacs is trying to access paths
like this:
/usr/share/emacs/23.2/site-lisp/~gthomas/.emacs.elc
What's even more odd is that emacs does manage to find _some_
of the correct files such as
/home/gthomas/.emacs.d/auto-save
/home/gthomas/.emacs.d/auto-save-list
Any idea why the confusion?
I'd really like to have emacs behave properly within devshell :-)
I can only imagine what else might be "weird" under the covers
while using devshell...
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
reply other threads:[~2015-05-21 12:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555DD6B1.8010608@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.