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: Thu, 4 Feb 2010 07:30:15 -0800 [thread overview]
Message-ID: <666B4094E55B408781676FA54BAEFB83@us.oracle.com> (raw)
In-Reply-To: <ADA78DC8F99942C5A11DEC8752DCFCC9@us.oracle.com>
> 99% of the time, I use it that way, too. But when debugging
> some elisp code, I sometimes add markers there, like Drew
> pointed out. So how about this idea:
>
> - *Messages* is read-only
> - `q' buries the buffer
> - `m' is bound to a new command that... provides an
> interface to `message'
I said:
> So this comes down to a choice, I think:
>
> 1. View-mode by default, so `q' quits, and you need to do
> `C-x C-q' to make it writable.
>
> 2. Writable by default, and you need to do `C-x 0' (or `C-x
> k') to get rid of it.
>
> And the same or similar considerations probably apply to *Pp
> Eval Output*. I still vote for #2, but I don't feel strongly about it.
Again, I'm OK with either. I too use it without editing most of the time.
And I don't think we need undo (with its cost) in *Messages*.
The same applies to *Pp Eval Output*. But undo there would be useful. Quitting
read-only should put *Pp Eval Output* back in Emacs-Lisp mode.
I don't see the point (need) for the proposed `m' binding in `Messages'. If it's
just in order to be able to add to the buffer text without turning off read-only
(C-x C-q), then turning it off and editing is handier, IMO. But I'm probably
missing the point here.
If we choose #1, then `q' should do what it does in other, similar situations. I
think that's more likely to be `quit-window' than `bury-buffer'. (FWIW, with my
use of frames, `bury-buffer' is almost never the behavior I want.) Let `q' do
what it does in Dired, for instance (`quit-window').
next prev parent reply other threads:[~2010-02-04 15:30 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=666B4094E55B408781676FA54BAEFB83@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 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.