From: Jambunathan K <kjambunathan@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 11298@debbugs.gnu.org
Subject: bug#11298: Scratch buffer (Summary of Xah's proposals, as I see it)
Date: Tue, 24 Apr 2012 22:03:06 +0530 [thread overview]
Message-ID: <81r4vd9jjx.fsf@gmail.com> (raw)
In-Reply-To: <4F96AF1D.2090806@gmx.at> (martin rudalics's message of "Tue, 24 Apr 2012 15:48:13 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> Emacs has a notion of buffers that are *not* and *never will be (?)*
>> file-visiting.
>
> A user is always able to save _any_ buffer to a new file (if there's
> sufficient space) so the "*never will be (?)*" is not a valid notion.
What will be lost if Emacs forbids such a write?
I can mark the buffer, switch to a file-visiting buffer and yank my
scratch contents there.
next prev parent reply other threads:[~2012-04-24 16:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 15:55 bug#11298: 24.0.95; (WISH) Re-look scratch buffers Jambunathan K
2012-04-21 19:53 ` Stefan Monnier
2012-04-21 20:50 ` Jambunathan K
2012-04-22 14:11 ` Richard Stallman
2012-04-24 10:21 ` Jambunathan K
2012-04-23 19:39 ` Stefan Monnier
2012-04-23 20:09 ` Lennart Borgman
2012-04-23 20:11 ` Drew Adams
2012-04-24 1:39 ` Stefan Monnier
2012-04-24 13:42 ` Drew Adams
2012-04-24 10:57 ` bug#11298: Recipe to surface *code-conversion-work* buffer Jambunathan K
2012-04-24 11:39 ` martin rudalics
2012-04-24 12:54 ` Jambunathan K
2012-04-24 12:20 ` bug#11298: Scratch buffer (Summary of Xah's proposals, as I see it) Jambunathan K
2012-04-24 12:31 ` Jambunathan K
2012-04-24 13:48 ` martin rudalics
2012-04-24 16:33 ` Jambunathan K [this message]
2012-04-24 14:17 ` Jan D.
2012-04-24 16:26 ` Jambunathan K
2012-04-25 12:33 ` Jan D.
2012-04-24 18:42 ` Stefan Monnier
2013-11-15 5:06 ` bug#11298: 24.0.95; (WISH) Re-look scratch buffers Jambunathan K
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=81r4vd9jjx.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=11298@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.