all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: 24577@debbugs.gnu.org
Cc: Dmitri Paduchikh <dpaduchikh@gmail.com>
Subject: bug#24577: 25.1; Proposal to improve C-u C-h c behavior
Date: Sat, 01 Oct 2016 05:40:40 +0000	[thread overview]
Message-ID: <878tu8zkx3.fsf@violet.siamics.net> (raw)
In-Reply-To: <87zimovf4z.fsf@gmail.com> (Dmitri Paduchikh's message of "Sat, 01 Oct 2016 09:59:08 +0500")

>>>>> 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.

	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.

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

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

-- 
FSF associate member #7257  http://am-1.org/~ivan/      … 3013 B6A0 230E 334A





  reply	other threads:[~2016-10-01  5:40 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 [this message]
2016-10-01  6:54   ` Eli Zaretskii
2016-10-01  8:38     ` Dmitri Paduchikh
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=878tu8zkx3.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=24577@debbugs.gnu.org \
    --cc=dpaduchikh@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 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.