From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r100117: Run kill-emacs when exiting for display closed or SIGTERM/HUP.
Date: Mon, 03 May 2010 20:08:06 +0200 [thread overview]
Message-ID: <4BDF1106.7060200@swipnet.se> (raw)
In-Reply-To: <jwv63343n4c.fsf-monnier+emacs@gnu.org>
Stefan Monnier skrev 2010-05-03 19.43:
>> For this bug report, yes. But for the more general session management
>> handling, it really is "start where we stopped".
>
> But that's the whole problem: what do you define as "where we stopped"?
> As I said, there are as many current directories as there are buffers.
Yes there is, it is what getcwd returns. That is where the process is
started. That is the current directory according to the OS. A process can
only have one current directory, and Emacs is no different.
>
>> Who knows what other/future packages save in the current directory?
>
> There's really no such thing as "Emacs's current directory".
>
Yes there is, it is what getcwd returns. Anything else is just cosmetics and
not the current directory of the Emacs process.
>> Relative filenames perhaps? Not to mention the fact that I personally
>> get irritated that C-x C-f from *scratch* starts with the wrong
>> directory in this case.
>
> Then desktop should save the default-directory of *scratch* (and
> maybe/probably other buffers as well). IIUC you can do that by adding
> default-directory to desktop-locals-to-save.
>
>> That is too simplified, Emacs has more state than just the desktop file.
>
> But "--chdir" is too simplified, Emacs has many more current directories
> than just "the one" ;-)
>
No, a process can only have one current directory, and so does Emacs,
it is what getcwd returns.
Jan D.
next prev parent reply other threads:[~2010-05-03 18:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1O8efK-0003y3-Sb@internal.in.savannah.gnu.org>
2010-05-02 19:24 ` [Emacs-diffs] /srv/bzr/emacs/trunk r100117: Run kill-emacs when exiting for display closed or SIGTERM/HUP Stefan Monnier
2010-05-02 20:53 ` Jan Djärv
2010-05-03 0:55 ` Stefan Monnier
2010-05-03 8:21 ` Jan D.
2010-05-03 17:43 ` Stefan Monnier
2010-05-03 18:08 ` Jan Djärv [this message]
2010-05-04 2:38 ` Stefan Monnier
2010-05-04 7:59 ` Jan Djärv
2010-05-04 11:49 ` Stephen J. Turnbull
2010-05-04 13:03 ` Jan D.
2010-05-04 13:48 ` Stefan Monnier
2010-05-04 14:42 ` Jan D.
2010-05-04 3:03 ` Stephen J. Turnbull
2010-05-04 8:06 ` Jan Djärv
2010-05-04 11:33 ` Stephen J. Turnbull
2010-05-04 12:51 ` Jan D.
2010-05-04 13:54 ` Stefan Monnier
2010-05-04 14:26 ` Jan D.
2010-05-04 18:50 ` Stefan Monnier
2010-05-05 5:17 ` Stephen J. Turnbull
2010-05-05 7:21 ` Jan Djärv
2010-05-05 14:00 ` Stefan Monnier
2010-05-05 16:18 ` Jan Djärv
2010-05-05 18:24 ` Stefan Monnier
2010-05-04 16:45 ` Juri Linkov
2010-05-04 18:50 ` Jan Djärv
2010-05-04 19:55 ` Juri Linkov
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=4BDF1106.7060200@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.