From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Session management patch, please comment.
Date: Wed, 20 Feb 2002 15:13:32 -0700 (MST) [thread overview]
Message-ID: <200202202213.g1KMDWN13533@aztec.santafe.edu> (raw)
In-Reply-To: <3C72B1AF.6090202@mbox200.swipnet.se> (Jan.Djarv@mbox200.swipnet.se)
Well, actually I didn't even want this function, but I could not find
another way to call C from lisp. It is not meant to be "external",
rather a link between the C part and the lisp part of the session
management code.
It is a good idea to document it clearly anyway, even though it is not
meant for general use. The doc string can say "Don't call this
yourself."
"End interaction as a response to save_yourself.
A session manager can tell Emacs that the window system is shutting down
by sending Emacs a save_yourself message. Emacs then executes functions
in `save-yourself-hook'. After that, this function shall be called to
inform the session manager that it can continue or abort shutting down
the window system.
If the argument CANCEL is non-nil, Emacs will tell the session manager
to cancel the shutdown."
That is good, except for "this function shall be called", which is vague.
What code is supposed to call this function?
How about this (a bit long perhaps):
"The previous session id Emacs got from session manager.
If Emacs is running on a window system that has a session manager, the
session manager gives Emacs a session id. It is feasible for Emacs lisp
code to use the session id to save configuration in, for example, a file
with a file name based on the session id...
That is good.
The idea was that as functions in save-yourself-hook are executing, they
might interact with the user, for instance pop up a dialog. That dialog
can have the possibility to cancel the whole window system shutdown. If
the lisp code wants to do that, it shall set this variable to something
non-nil.
Please document that clearly (but don't use "shall").
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-20 22:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-17 19:11 Session management patch, please comment Jan D.
2002-02-19 6:37 ` Richard Stallman
2002-02-19 8:40 ` Kim F. Storm
2002-02-19 20:13 ` Jan D.
2002-02-19 20:12 ` Jan D.
2002-02-19 22:43 ` Kim F. Storm
2002-02-20 20:29 ` Jan Djärv
2002-02-20 22:50 ` Kim F. Storm
2002-02-21 19:57 ` Jan D.
2002-02-21 21:18 ` Kim F. Storm
2002-02-26 22:49 ` New session management patch Jan D.
2002-02-27 5:51 ` Richard Stallman
2002-02-27 10:23 ` Eli Zaretskii
2002-02-27 15:25 ` Andreas Schwab
2002-02-27 18:11 ` Colin Walters
2002-02-28 4:08 ` Richard Stallman
2002-02-27 19:43 ` Jan D.
2002-02-28 18:22 ` Richard Stallman
2002-02-28 15:36 ` Kim F. Storm
2002-03-01 1:11 ` Richard Stallman
2002-02-22 4:32 ` Session management patch, please comment Richard Stallman
2002-02-20 22:13 ` Richard Stallman [this message]
2002-02-21 20:01 ` 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=200202202213.g1KMDWN13533@aztec.santafe.edu \
--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).