From: Jambunathan K <kjambunathan@gmail.com>
To: 11298@debbugs.gnu.org
Subject: bug#11298: Scratch buffer (Summary of Xah's proposals, as I see it)
Date: Tue, 24 Apr 2012 17:50:12 +0530 [thread overview]
Message-ID: <81397tiao3.fsf@gmail.com> (raw)
In-Reply-To: <81397xm657.fsf@gmail.com>
Let me rephrase ideas in Xah's post -
http://lists.gnu.org/archive/html/help-gnu-emacs/2012-04/msg00260.html.
The recommendations involve,
1. "Menu->File->Visit New File" should be changed to "File->New". This
will create an 'Untitled N' buffer. This will mark the buffer as
`potentially-file-visiting'. Specifically it will not ask for the
name of the file.
2. Introduce "File->Save as" will mark a `potentially-file-visiting'
buffer as a `real-file-visiting-buffer'.
3. `potentially-file-visiting-buffer' should be queried for save on
exit.
Speaking of scratch buffer,
--------------------------
Emacs has a notion of buffers that are *not* and *never will be (?)*
file-visiting. Their only purpose is to do THROWAWAY work ("use and
throw") with an understanding that Emacs will promise /not/ to annoy the
user with "Should I save this THROWAWAY work? It seems valuable to me
even though you think otherwise".
(Hmm, I like the way Emacs gives primacy to throwaway work.)
1. It is useful to have scratch buffers. Though most users will have no
use for it.
2. There could be mutliple user-created scratch buffers and they could
be created in multiple programming lang modes, depending on user's
needs.
I think,
--------
If Emacs *deduces* file-visitedness based on the name of the buffer, I
think much of the problem could be elegantly dealt with.
1. C-x b => Create "Untitled N". It is potentially-file-visiting. Such
buffers always queried on exit.
2. C-u C-x b => Creates "*throway-%s*". Note that the default offered
to the user names the buffer specially with leading and trailing
asterisks, These are non-file-visiting buffers.
next prev parent reply other threads:[~2012-04-24 12:20 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 ` Jambunathan K [this message]
2012-04-24 12:31 ` bug#11298: Scratch buffer (Summary of Xah's proposals, as I see it) Jambunathan K
2012-04-24 13:48 ` martin rudalics
2012-04-24 16:33 ` Jambunathan K
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
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=81397tiao3.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=11298@debbugs.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).