From: "Davis Herring" <herring@lanl.gov>
To: "David Reitter" <david.reitter@gmail.com>
Cc: emacs- devel <emacs-devel@gnu.org>
Subject: Re: *scratch* buffer (was: A wish, a plea)
Date: Wed, 27 Jun 2007 18:06:44 -0700 (PDT) [thread overview]
Message-ID: <33953.128.165.123.18.1182992804.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <93CF6922-CA47-4100-9644-D2BC7C182FAF@gmail.com>
> I am also intending to make the *scratch* buffer persistent across
> sessions.
> That way, users will not be bothered to give it a name and to
> explicitly save it. But they will retain its contents across crashes
> and intentional restarts. If the desktop is a good analogy: when I
> come into my office in the morning, all my scratch papers are still
> on my desk. Even in companies that operate a "clean desk policy", the
> cleaners are not instructed to throw away everything that's on
> people's desks at 7am. (Or do they?)
I realize that Mac does not believe in running two copies of the same
application (process), but taking that to be a Bad Assumption, I ask: how
does this deal in any even moderately graceful way with simultaneous
Emacses? We have a persistent state, automatically saved, with no name,
that is surely to conflict with other *scratch*es.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2007-06-28 1:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 10:48 *scratch* buffer (was: A wish, a plea) David Reitter
2007-06-22 11:57 ` Jason Rumney
2007-06-22 14:17 ` David Reitter
2007-06-22 14:58 ` Juanma Barranquero
2007-06-28 1:07 ` Davis Herring
2007-06-28 9:58 ` David House
2007-06-28 15:04 ` Davis Herring
2007-06-22 21:53 ` Richard Stallman
2007-06-28 1:06 ` Davis Herring [this message]
2007-06-29 16:42 ` *scratch* buffer Juri Linkov
2007-07-02 16:16 ` Davis Herring
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=33953.128.165.123.18.1182992804.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=david.reitter@gmail.com \
--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).