From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.bugs Subject: bug#60190: 29.0.50; Improve `Info-goto-node-web' Date: Tue, 20 Dec 2022 07:00:40 +0100 Message-ID: <874jtqd37b.fsf@mbork.pl> References: <87a63jdi8r.fsf@mbork.pl> <877cynci3z.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33186"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.1.0; emacs 29.0.50 Cc: "60190@debbugs.gnu.org" <60190@debbugs.gnu.org> To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Dec 20 07:01:26 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p7Vgs-0008Si-52 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 20 Dec 2022 07:01:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p7Vgb-0006xz-8R; Tue, 20 Dec 2022 01:01:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p7VgV-0006up-7t for bug-gnu-emacs@gnu.org; Tue, 20 Dec 2022 01:01:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1p7VgU-0000M2-7e for bug-gnu-emacs@gnu.org; Tue, 20 Dec 2022 01:01:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p7VgU-0006hN-2t for bug-gnu-emacs@gnu.org; Tue, 20 Dec 2022 01:01:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Marcin Borkowski Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 20 Dec 2022 06:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60190 X-GNU-PR-Package: emacs Original-Received: via spool by 60190-submit@debbugs.gnu.org id=B60190.167151604825732 (code B ref 60190); Tue, 20 Dec 2022 06:01:02 +0000 Original-Received: (at 60190) by debbugs.gnu.org; 20 Dec 2022 06:00:48 +0000 Original-Received: from localhost ([127.0.0.1]:42639 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p7VgG-0006gy-2a for submit@debbugs.gnu.org; Tue, 20 Dec 2022 01:00:48 -0500 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:57894) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p7VgE-0006gr-P3 for 60190@debbugs.gnu.org; Tue, 20 Dec 2022 01:00:47 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 5B6912271598; Tue, 20 Dec 2022 07:00:44 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOsRHCqY1NMB; Tue, 20 Dec 2022 07:00:41 +0100 (CET) Original-Received: from localhost (178235147073.dynamic-3-poz-k-0-1-0.vectranet.pl [178.235.147.73]) by mail.mojserwer.eu (Postfix) with ESMTPSA id BB52D2271589; Tue, 20 Dec 2022 07:00:40 +0100 (CET) In-reply-to: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:251495 Archived-At: On 2022-12-19, at 21:33, Drew Adams 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 =E2=80=93 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. --=20 Marcin Borkowski http://mbork.pl