unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@mbork.pl>,
	"60190@debbugs.gnu.org" <60190@debbugs.gnu.org>
Subject: bug#60190: 29.0.50; Improve `Info-goto-node-web'
Date: Mon, 19 Dec 2022 17:23:07 +0000	[thread overview]
Message-ID: <SJ0PR10MB54887B0EB5CAE1CB6A1BBC4CF3E59@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87a63jdi8r.fsf@mbork.pl>

> I am extremely happy because of `Info-goto-node-web', but it would be
> even better if two changes were made.
> 
> 1. It could work in "An Introduction to Programming in Emacs Lisp" and
> Org mode manual, too.
> 
> 2. It could put the URL on the kill ring when called with a prefix
> argument.

FWIW:

The command is originally from Info+ (see bug #44895).

There, a prefix arg reverses the effect of the current
value of option `browse-url-new-window-flag', which
decides whether a new browser window is used instead
of the current one.
___

A prefix arg could (1) do that or (2) use a separate
browser tab, and also (3) do what you ask, depending
on its value (e.g., plain C-u, plain -, =< 0, >= 0).

Or there could be separate commands
(*-other-tab|window|frame), since vanilla Emacs
doesn't like to let a prefix arg do multiple things.
___

And an option could decide whether by default the URL
is copied to the kill-ring (prefix arg here flipping
that behavior).

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

I agree with Eli that it would be good for any list
of manuals to use to be the value of a (user)
variable, as opposed to being hardcoded.

Its default value should come (at runtime) from the
manuals you get by default in your context (it can
vary a lot).  E.g., ` info--manual-names', which
can be limited to the manuals currently visited.
___


https://www.emacswiki.org/emacs/InfoPlus





  parent reply	other threads:[~2022-12-19 17:23 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 [this message]
2022-12-19 19:24   ` Marcin Borkowski
2022-12-19 20:33     ` Drew Adams
2022-12-20  6:00       ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB54887B0EB5CAE1CB6A1BBC4CF3E59@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=60190@debbugs.gnu.org \
    --cc=mbork@mbork.pl \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).