From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: session management restores Emacs twice
Date: Mon, 28 Jul 2003 11:30:35 -0400 [thread overview]
Message-ID: <E19h9xL-0000I8-Ty@fencepost.gnu.org> (raw)
In-Reply-To: <200307271341.h6RDfXMb005243@utx.utx.cz> (message from Stanislav Brabec on Sun, 27 Jul 2003 15:41:33 +0200)
I am using GTK2 version of Emacs in gnome-session (wm metacity).
Emacs session is saved correctly (but metacity complains about
improper session management implementation).
While restoring session during next login, Emacs is started twice.
The same behavior occur for KDE session, too.
I don't know how these things work--is there any chance you or someone
can figure out what is wrong in the information that Emacs sends?
next parent reply other threads:[~2003-07-28 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200307271341.h6RDfXMb005243@utx.utx.cz>
2003-07-28 15:30 ` Richard Stallman [this message]
2003-08-21 20:00 ` session management restores Emacs twice Jan D.
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=E19h9xL-0000I8-Ty@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.
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).