all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dmitri Paduchikh <dpaduchikh@gmail.com>,
	24577@debbugs.gnu.org, ivan@siamics.net
Subject: bug#24577: 25.1; Proposal to improve C-u C-h c behavior
Date: Tue, 08 Feb 2022 07:48:55 +0100	[thread overview]
Message-ID: <87v8xpsvjc.fsf@gnus.org> (raw)
In-Reply-To: <83vaxcl9kv.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Oct 2016 12:09:20 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> >>       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.
>
> Then perhaps we could have both behaviors, one after a single "C-u",
> the other after two "C-u"s.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

In my opinion, this would complicate this command needlessly because I
don't think this would be used a lot.  The user can always jump to the
*Messages* buffer if they want to yank the message, and that works for
all commands like this, not just `C-h c'.

So I'm therefore closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-02-08  6:48 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
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 [this message]
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=87v8xpsvjc.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=24577@debbugs.gnu.org \
    --cc=dpaduchikh@gmail.com \
    --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.