From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 44895@debbugs.gnu.org
Subject: bug#44895: Add Info-copy-permalink
Date: Fri, 27 Nov 2020 05:39:35 +0800 [thread overview]
Message-ID: <874klbn6g8.5.fsf@jidanni.org> (raw)
c runs the command Info-copy-current-node-name.
That's great but not powerful enough.
Let's say I am reading
(info "(emacs) Optional Mode Line")
and stumble upon the fact that
On graphical displays, the mode line is drawn as a 3D box.
I think, "This is great. I'll be sure to tell Mrs. Nerblefield. She'll
switch editors right away."
Well, most other programs' manuals have a "share" or "copy permalink"
button, most alas except for emacs.
> We don't keep track of our URLs. Google is your friend.
Sure, but I'll probably end up finding Bill Snortfield's 1989 copy of
that page, and sending her the link to that.
> Well, find the search result with "gnu.org" in it.
Yeah, but there are more than one.
> Well then don't use Google. Just copy and paste the page's text, and
> send her that.
Yes, but she used to work at Wikipedia, so she will ask for proof.
> Well, go to gnu.org and put the title in the search box. Maybe that
> will find the link you need.
Maybe, but how about instead, along with Info-copy-current-node-name,
there was a command, Info-copy-current-node-permalink, or just
Info-copy-permalink. that would copy it for us?
> We don't hardwire https URLs into the manual. Sorry.
Yes you do. (info "(emacs) Distrib") has plenty. And that page even
knows about itself:
(1) This manual is itself...
As a bonus, mid-page anchor # fragments could even go directly to the
places in the page there online, just like they do in the offline manual.
emacs-version "27.1"
next reply other threads:[~2020-11-26 21:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 21:39 積丹尼 Dan Jacobson [this message]
2020-11-26 23:06 ` bug#44895: Add Info-copy-permalink Drew Adams
2020-11-26 23:20 ` 積丹尼 Dan Jacobson
2020-11-27 0:29 ` Drew Adams
2020-11-27 5:34 ` Richard Stallman
2020-11-27 7:24 ` Eli Zaretskii
2020-11-27 10:44 ` Stefan Kangas
2020-11-27 10:57 ` Jean Louis
2020-11-27 12:32 ` Eli Zaretskii
2020-11-28 7:47 ` Stefan Kangas
2020-11-28 8:21 ` Eli Zaretskii
2020-11-27 18:51 ` Drew Adams
2020-11-27 7:23 ` Eli Zaretskii
2020-11-27 8:14 ` Jean Louis
2020-11-27 8:40 ` Eli Zaretskii
2020-11-27 8:47 ` Jean Louis
2020-11-27 20:19 ` Tomas Nordin
2020-11-27 23:27 ` 積丹尼 Dan Jacobson
2020-11-27 9:45 ` Stephen Berman
2020-11-27 10:21 ` Jean Louis
2020-11-27 18:46 ` Drew Adams
2021-11-11 7:11 ` Lars Ingebrigtsen
2021-11-11 17:26 ` bug#44895: [External] : " Drew Adams
2021-11-11 17:40 ` Juri Linkov
2021-11-11 17:58 ` Drew Adams
2021-11-12 3:32 ` Lars Ingebrigtsen
2021-11-12 7:41 ` Robert Pluim
2021-11-12 7:48 ` Lars Ingebrigtsen
2021-11-12 17:17 ` Drew Adams
2021-11-14 0:06 ` 積丹尼 Dan Jacobson
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=874klbn6g8.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=44895@debbugs.gnu.org \
/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).