From: "Drew Adams" <drew.adams@oracle.com>
To: "'Tassilo Horn'" <tassilo@member.fsf.org>, <emacs-devel@gnu.org>
Subject: RE: Bind `q' to `quit-window' or similar in *Messages*
Date: Wed, 3 Feb 2010 07:48:31 -0800 [thread overview]
Message-ID: <49F60829322A48C886BC62810DDB0147@us.oracle.com> (raw)
In-Reply-To: <87636evclf.fsf@thinkpad.tsdh.de>
> Cause *Messages* is not read-only, and maybe you want to insert a q
> there. But does that anybody really want? I guess no. So I'd be in
> favor of making *Messages* read-only and bind `q' to `quit-window'
> there.
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.
What's wrong with `C-x 0' (or `C-x k')?
Please do not make *Messages* read-only. Likewise, *Pp Eval Output*.
next prev parent reply other threads:[~2010-02-03 15:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 9:48 Bind `q' to `quit-window' or similar in *Messages* Deniz Dogan
2010-02-03 10:27 ` Tassilo Horn
2010-02-03 15:48 ` Drew Adams [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2010-02-04 1:28 Roland Winkler
2010-02-04 1:41 ` Drew Adams
2010-02-04 2:32 ` Miles Bader
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
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=49F60829322A48C886BC62810DDB0147@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=tassilo@member.fsf.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).