all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>,
	"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: Tue, 04 May 2010 10:06:18 +0200	[thread overview]
Message-ID: <4BDFD57A.3050808@swipnet.se> (raw)
In-Reply-To: <87633474hd.fsf@uwakimon.sk.tsukuba.ac.jp>

2010-05-04 05:03, Stephen J. Turnbull skrev:
> Jan Djärv writes:
>
>   >  >  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.
>
> You're taking the implementation way too seriously.  The question is,
> do any users (other than the one named "Jan Djärv", of course) think
> that what getcwd() returns is of interest?  I certainly don't, for one
> sample point.  And, if the do care at all, how does that rank compared
> to the local values of `default-directory'?
>
>

We are talking about restarting Emacs from the session manager.  So far no one 
has come up with a better solution.  Should we start an Emacs process for each 
unique default-directory?  Pick one at random?  Ignore the problem and let the 
session manager descide?

Put up a solution that addresses the problems:

Desktop file isn't loaded.
*scratch* and *Messages* and more get the wrong default directory.

It is nice of you to let us know that you don't care about getcwd, but not 
very helpful.

	Jan D.




  reply	other threads:[~2010-05-04  8:06 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
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 [this message]
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=4BDFD57A.3050808@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=stephen@xemacs.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.
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.