all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitri Paduchikh <dpaduchikh@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24577@debbugs.gnu.org, Ivan Shmakov <ivan@siamics.net>
Subject: bug#24577: 25.1; Proposal to improve C-u C-h c behavior
Date: Sat, 01 Oct 2016 13:38:45 +0500	[thread overview]
Message-ID: <87shsgv4yy.fsf@gmail.com> (raw)
In-Reply-To: <83bmz4mudt.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Oct 2016 09:54:38 +0300")

Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Ivan Shmakov <ivan@siamics.net>
>> Date: Sat, 01 Oct 2016 05:40:40 +0000
>> Cc: Dmitri Paduchikh <dpaduchikh@gmail.com>
>> 
>> >>>>> Dmitri Paduchikh <dpaduchikh@gmail.com> writes:
>> 
>>  > C-u C-h c does not work in read-only buffers.  And even if the buffer
>>  > is writable it's rarely an appropriate place to insert info about key
>>  > bindings.  I think it would be better if C-u C-h c placed its output
>>  > into kill ring and printed it in the echo area instead of the current
>>  > behavior.
>> 
>>       I believe that this behavior is a common idiom in Emacs.
>>       For example, M-! date RET shows the current date and time in
>>       echo area, while C-u M-! date RET inserts it at point – with
>>       both actions making sense depending on the situation.

There is a difference here. You are calling C-u M-! at the place where
you want its output, whereas C-u C-h c has to be called at the place
when the key is defined, and that place is rarely the same where you
want to insert the key description.

>>       I guess C-u C-h c behavior is mainly useful when writing about
>>       Emacs itself (including writing bug reports, or conversing on
>>       IRC, etc.), but I can easily see it being handy nevertheless.

I agree that main use of C-u C-h c is when writing about Emacs itself,
but the part about being handy nevertheless I didn't understand. I
didn't propose to remove it, just make it more handy.

>>       Also, for read-only buffers, one can use C-h c without C-u, and
>>       then copy the result from the *Messages* buffer.

In other words, you are suggesting not to use C-u C-h c and simply work
around the issue. But since you prefer not to use it, then you won't
suffer from the behavior change.

>>       On the other hand, I’m not aware of any of Emacs commands adding
>>       the result of some operation directly to the kill ring.

I have seen the proposed behavior in emacs-w3m where w3m-print-this-url
behaves in this manner. It is convenient. Please note that message in
the echo area may contain the indication that the description has been
copied into kill ring. I think this would remove any possible confusion.

EZ> 100% agreement.

Regards,
Dmitri Paduchikh





  reply	other threads:[~2016-10-01  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01  4:59 bug#24577: 25.1; Proposal to improve C-u C-h c behavior Dmitri Paduchikh
2016-10-01  5:40 ` Ivan Shmakov
2016-10-01  6:54   ` Eli Zaretskii
2016-10-01  8:38     ` Dmitri Paduchikh [this message]
2016-10-01  9:09       ` Eli Zaretskii
2016-10-01 11:42         ` Dmitri Paduchikh
2016-10-01 12:09           ` Dmitri Paduchikh
2022-02-08  6:48         ` Lars Ingebrigtsen
2016-10-01  7:55   ` Andreas Schwab
2016-10-01 20:14   ` Marcin Borkowski

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=87shsgv4yy.fsf@gmail.com \
    --to=dpaduchikh@gmail.com \
    --cc=24577@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=ivan@siamics.net \
    /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.