From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: About HOME in OS X
Date: Tue, 11 Jun 2013 12:45:09 -0400 [thread overview]
Message-ID: <barmar-6F5B49.12450911062013@news.eternal-september.org> (raw)
In-Reply-To: mailman.1403.1370966034.22516.help-gnu-emacs@gnu.org
In article <mailman.1403.1370966034.22516.help-gnu-emacs@gnu.org>,
Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Tue, 11 Jun 2013 19:27:46 +0800
> > From: Xue Fuqiao <xfq.free@gmail.com>
> >
> > On Tue, Jun 11, 2013 at 7:22 PM, Xue Fuqiao <xfq.free@gmail.com> wrote:
> > > Hi list,
> > >
> > > On my system (OS X 10.8.4):
> > >
> > > ELISP> (getenv "HOME")
> > > "/Users/xfq"
> > > ELISP> (expand-file-name "$HOME/foo")
> > > "/Users/xfq/emacs-repo/bzr/trunk/nextstep/Emacs.app/Contents/MacOS/$HOME
> > > /foo"
> > >
> > > I'm confused here. Why don't the result of two evaluations be the same?
>
> Could be a symlink or something similar?
No, it just means that he did it while his current directory was
/Users/xfq/emacs-repo/bzr/trunk/nextstep/Emacs.app/Contents/MacOS.
"$HOME/foo" is a relative path, so it's appended to the current
directory.
As someone else pointed out, expand-file-name doesn't expand environment
variables.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2013-06-11 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 11:22 About HOME in OS X Xue Fuqiao
2013-06-11 11:27 ` Xue Fuqiao
2013-06-11 15:53 ` Eli Zaretskii
[not found] ` <mailman.1403.1370966034.22516.help-gnu-emacs@gnu.org>
2013-06-11 16:45 ` Barry Margolin [this message]
2013-06-11 17:05 ` Peter Dyballa
[not found] ` <mailman.1410.1370970844.22516.help-gnu-emacs@gnu.org>
2013-06-11 17:20 ` Barry Margolin
2013-06-11 21:38 ` Peter Dyballa
2013-06-11 20:25 ` Thien-Thi Nguyen
2013-06-11 11:30 ` Kevin Montuori
2013-06-11 15:13 ` Peter Dyballa
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=barmar-6F5B49.12450911062013@news.eternal-september.org \
--to=barmar@alum.mit.edu \
--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).