From: Roland Winkler <roland.winkler@physik.uni-erlangen.de>
To: drew.adams@oracle.com
Cc: emacs-devel@gnu.org
Subject: RE: Bind `q' to `quit-window' or similar in *Messages*
Date: Wed, 03 Feb 2010 19:28:40 -0600 [thread overview]
Message-ID: <87636d94c7.fsf@regnitz.physics.niu.edu> (raw)
In-Reply-To: 49F60829322A48C886BC62810DDB0147@us.oracle.com
> Absolutely I want that. I want to be able to write in *Messages*.
> Yes, I can toggle read-only, but if `q' quits, then that defeats
> the purpose.
>
> I sometimes find myself with tons of messages being logged, and
> when I make several successive tests I sometimes type stuff in
> Messages to distinguish test sequences etc. And I kill sections of
> text there, or copy text (including text I've added) to other
> buffers, and so on.
I understand your point. Yet my typing in this buffer is purely
accidental / unintentional. And I find it annoying that the
*Messages* buffer does not have an undo history. So from that
perspective, it appears to me that the original design did not have
in mind the possibility of editing this buffer. So I want to suggest
two things:
- *Messages* should not have buffer-undo-list set to t
(Of course, I do not know whether this would collide with anything
else.)
- Some customization that allows one to toggle between a read-only
*Messages* buffer (with q bound to quit-window) and an edit mode
where one can do whatever one likes to do.
(How do the normal entries in *Messages* find their way into this
buffer? Does this mechanism care whether this buffer is read-only
or not? I just tried it and it appears to gives no errors.)
Roland
next reply other threads:[~2010-02-04 1:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 1:28 Roland Winkler [this message]
2010-02-04 1:41 ` Bind `q' to `quit-window' or similar in *Messages* Drew Adams
2010-02-04 2:32 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2010-02-04 3:24 Roland Winkler
2010-02-04 4:27 ` Miles Bader
2010-02-04 8:15 ` Tassilo Horn
2010-02-04 8:24 ` Tassilo Horn
2010-02-04 15:33 ` Stefan Monnier
2010-02-04 23:40 ` Miles Bader
2010-02-03 9:48 Deniz Dogan
2010-02-03 10:27 ` Tassilo Horn
2010-02-03 15:48 ` Drew Adams
2010-02-03 15:54 ` Lennart Borgman
2010-02-03 15:59 ` Tassilo Horn
2010-02-03 17:03 ` Drew Adams
2010-02-04 15:30 ` Drew Adams
2010-02-04 16:23 ` Tassilo Horn
2010-02-04 18:01 ` Thierry Volpiatto
2010-02-15 13:46 ` Deniz Dogan
2010-02-16 16:42 ` 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=87636d94c7.fsf@regnitz.physics.niu.edu \
--to=roland.winkler@physik.uni-erlangen.de \
--cc=drew.adams@oracle.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).