From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 44895@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#44895: Add Info-copy-permalink
Date: Fri, 27 Nov 2020 10:40:21 +0200 [thread overview]
Message-ID: <83czzzp4zu.fsf@gnu.org> (raw)
In-Reply-To: <X8C1WjMTdy+HKJlS@protected.rcdrun.com> (message from Jean Louis on Fri, 27 Nov 2020 11:14:18 +0300)
> Date: Fri, 27 Nov 2020 11:14:18 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: 積丹尼 Dan Jacobson <jidanni@jidanni.org>,
> 44895@debbugs.gnu.org
>
> This is similar to partial functions of `org-store-link' and to key
> `w' in *eww*, or to `c' to copy Node name in the Info buffer, with
> addition that capturing the hyperlink to the reference would construct
> the shareable link or could invoke integration to quickly send it to
> somebody.
>
> If it is meant to obtain quick reference to be shared with somebody,
> partial construction of URL could be obtained with:
>
> User could press let us say: `C' on the "14.18 Optional Mode Line
> Features" page, then the WWW hyperlink could be constructed in memory
> pointing to:
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Optional-Mode-Line.html
> or snippet could be constructed with the title and URL such as:
>
> Emacs Manual: 14.18 Optional Mode Line Features
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Optional-Mode-Line.html
>
> then by yanking snippet into email it can be shared easily with
> third party.
Are we talking only about "sharing" stuff in manuals related to Emacs?
What about any other Info manual? And what about manuals that don't
have a Web site?
IOW, this proposed feature needs more detailed specification, IMO.
next prev parent reply other threads:[~2020-11-27 8:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 21:39 bug#44895: Add Info-copy-permalink 積丹尼 Dan Jacobson
2020-11-26 23:06 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czzzp4zu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44895@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=jidanni@jidanni.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 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.