From: Richard Stallman <rms@gnu.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 11298@debbugs.gnu.org
Subject: bug#11298: 24.0.95; (WISH) Re-look scratch buffers
Date: Sun, 22 Apr 2012 10:11:21 -0400 [thread overview]
Message-ID: <E1SLxVZ-0001l3-Tn@fencepost.gnu.org> (raw)
In-Reply-To: <81r4vgq07a.fsf@gmail.com> (message from Jambunathan K on Sun, 22 Apr 2012 02:20:01 +0530)
Instead of creating one scratch buffer, make changes such a way that N
scratch buffers are created. N = 0, 1, 2, 3 etc etc.
rename-uniquely is a good way to do that. Whenever you want a new one,
go to *scratch* and type M-x rename-uniquely. Then the next thing
that tries to make *scratch* will create a new one.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call
next prev parent reply other threads:[~2012-04-22 14:11 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 [this message]
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
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=E1SLxVZ-0001l3-Tn@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=11298@debbugs.gnu.org \
--cc=kjambunathan@gmail.com \
/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).