unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Sun, 2 May 2010 22:53:00 +0200	[thread overview]
Message-ID: <3D94147C-CA80-4DB1-AD11-4707C3077275@swipnet.se> (raw)
In-Reply-To: <jwvocgyt8gd.fsf-monnier+emacs@gnu.org>



2 maj 2010 kl. 21.24 skrev Stefan Monnier <monnier@iro.umontreal.ca>:

>>  Run kill-emacs when exiting for display closed or SIGTERM/HUP.
>>  * xsmfns.c (CHDIR_OPT): New define.
>>  (smc_save_yourself_CB): Add CHDIR_OPT to options to use when
>>  restarting emacs.
>
> Not sure what's the relationship between the kill-emacs part and the
> chdir part.  But I'm really wondering what this chdir thingy is
> good for.  I mean: the current directory of Emacs is something rather
> vague: Emacs has as many current directories as it has buffers, do  
> does
> it just refer to the default-directory of *scratch* and *Messages*?
> If so, why/when is that so important as to justify a startup option?
>

In some older Gnome versions, you could save current ditectory in the  
session manager and Emacs would then restart in that directory.

But now you can't so Emacs is restarted in a different directory.  If  
you are saving different desktops in different directories, restarting  
Emacs is kind of pointless unless you are in the right directory.

So making sure the desktop is saved wont solve the bug unless it is  
also read back properly.

         Jan D.




  reply	other threads:[~2010-05-02 20:53 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 [this message]
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
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

  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=3D94147C-CA80-4DB1-AD11-4707C3077275@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).