all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Drew Adams <drew.adams@oracle.com>
Cc: "60190@debbugs.gnu.org" <60190@debbugs.gnu.org>
Subject: bug#60190: 29.0.50; Improve `Info-goto-node-web'
Date: Tue, 20 Dec 2022 07:00:40 +0100	[thread overview]
Message-ID: <874jtqd37b.fsf@mbork.pl> (raw)
In-Reply-To: <SJ0PR10MB5488698BC261845A603811D5F3E59@SJ0PR10MB5488.namprd10.prod.outlook.com>


On 2022-12-19, at 21:33, Drew Adams <drew.adams@oracle.com> wrote:

>> > And maybe the option should cover not only this
>> > command but also commands that read a URL - IOW,
>> > maybe it should be a general user preference
>> > whether to add URLs (that you choose interactively)
>> > to the kill-ring.
>>
>> Not sure about this – why put a URL I _type_ into the kill ring?  Though
>> I agree that if the URL is somehow generated, this may be very useful.
>> For instance, if I had a function which could open DevDocs pages,
>> copying their URLs to the kill ring (or in this case, the system
>> clipboard) could make it easier to send their links to my teammates
>> (something I do fairly often).
>
> Why?  Why not?  Why type it twice or more?

Because if I "typed" it (read: put it there myself), it means that most
probably I just yanked it anyway, so why put it again onto the kill
ring?

> Not saying I'd use such a feature, or how much I
> would. But I can imagine that some users might.
> Till now I might not have thought that someone
> would want what you request: add the URL to the
> kill-ring for the Info case.
>
> IOW, I'm not sure either.  But if we're starting
> to think about such things then we might as well
> think them through a bit.

100% agree.

-- 
Marcin Borkowski
http://mbork.pl





      reply	other threads:[~2022-12-20  6:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  6:23 bug#60190: 29.0.50; Improve `Info-goto-node-web' Marcin Borkowski
2022-12-19  7:02 ` Eduardo Ochs
2022-12-19 12:31   ` Eli Zaretskii
2022-12-19 15:05     ` Eduardo Ochs
2022-12-19 15:27       ` Eli Zaretskii
2022-12-20  4:44         ` Stefan Kangas
2022-12-20 14:02           ` Eli Zaretskii
2022-12-20 15:20             ` Eduardo Ochs
2022-12-20 15:33               ` Eli Zaretskii
2022-12-21  1:05             ` Stefan Kangas
2022-12-21 12:04               ` Eli Zaretskii
2022-12-19 17:23 ` Drew Adams
2022-12-19 19:24   ` Marcin Borkowski
2022-12-19 20:33     ` Drew Adams
2022-12-20  6:00       ` Marcin Borkowski [this message]

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=874jtqd37b.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=60190@debbugs.gnu.org \
    --cc=drew.adams@oracle.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.