From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: ispell/hunspell/Windows: a fully-worked example
Date: Sat, 05 Apr 2014 09:49:17 +0300 [thread overview]
Message-ID: <83ppkw8e4y.fsf@gnu.org> (raw)
In-Reply-To: <87zjk0zrl6.fsf@robertthorpeconsulting.com>
> From: Robert Thorpe <rt@robertthorpeconsulting.com>
> Date: Fri, 04 Apr 2014 22:56:37 +0100
> Cc: help-gnu-emacs@gnu.org
>
> Let's say you install a new version of Emacs. Instead of installing
> the new menus and links with "addpm.exe" you just change the
> executable path in the icon link file on your desktop. In that case
> the new version of Emacs is starting in the current directory of the
> old version. That can make Emacs confused if it searches for things
> in the current directory.
Emacs never searches for things "in the current directory", it always
fully resolves file names relative to the current buffer's value of
default-directory, before passing them to system-call APIs. The
"Start in" directory set by the desktop shortcut only affects the
*scratch* buffer; every other buffer will have some other directory as
its default one. E.g., buffers that visit files have that file's
directory as their default-directory.
So I wonder whether you could show a real-life case where this problem
is indeed at work. I think such cases don't really exist, except when
you evaluate expressions in *scratch*.
next prev parent reply other threads:[~2014-04-05 6:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 7:39 ispell/hunspell/Windows: a fully-worked example djc
2014-04-04 7:41 ` djc
2014-04-04 10:29 ` AW
2014-04-04 10:42 ` Eli Zaretskii
2014-04-04 12:47 ` AW
2014-04-04 13:03 ` Eli Zaretskii
2014-04-04 14:00 ` AW
2014-04-04 14:30 ` AW
2014-04-04 21:56 ` Robert Thorpe
2014-04-05 6:49 ` Eli Zaretskii [this message]
2014-04-05 9:43 ` Robert Thorpe
[not found] ` <mailman.18956.1396680552.10748.help-gnu-emacs@gnu.org>
2014-04-05 6:59 ` David Masterson
2014-04-05 8:13 ` Eli Zaretskii
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=83ppkw8e4y.fsf@gnu.org \
--to=eliz@gnu.org \
--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).