From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: What's the flow for adding info: links in Org documents?
Date: Wed, 13 Apr 2022 18:36:13 +0700 [thread overview]
Message-ID: <t36cje$nms$1@ciao.gmane.io> (raw)
In-Reply-To: <CAFyQvY1GUMJ2v_1ELvU9hGG6ijhhUCzQ4g0dfEH=uMqm4mj2pA@mail.gmail.com>
On 13/04/2022 01:26, Kaushal Modi wrote:
> On Mon, Apr 11, 2022 at 10:57 AM Max Nikulin wrote:
>
>> There are a some problems with info links outside of Emacs:
>> - Export to PDF
>
> Yeah, I recently realized that I will need to add custom support for
> exporting info: links using ox-hugo. I made a small blog post out of
> this learning: https://scripter.co/linking-and-exporting-org-info-links/.
I would prefer
info "(org) Top"
to
Org Info: Top
since the former may be pasted to M-x : or to shell command prompt. And
the link target ideally should be https://orgmode.org/manual/index.html
Unfortunately there is no way to customize mapping of documents.
>> - Links to single page manuals as the result of export to HTML. E.g.
>> Emacs manual is really huge
>
> I did not understand this. The HTML exports convert an Info node to a
> hyperlink of the same manual page online.
For <info:emacs#Browse-URL> export to html produces the following link:
https://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Browse_002dURL
I think, a better variant is
https://www.gnu.org/software/emacs/manual/html_node/emacs/Browse_002dURL.html
even though for the Org manual I often prefer single-page HTML version.
Maybe several months ago there was a thread or at least message
concerning some problems with info links export (PDF?), but I can not
find it. The word "info" is too general and "ol-info" is present in
almost every bug reports. Too much noise.
next prev parent reply other threads:[~2022-04-13 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 12:35 What's the flow for adding info: links in Org documents? Kaushal Modi
2022-04-11 12:47 ` Kaushal Modi
2022-04-11 14:50 ` Max Nikulin
2022-04-12 18:26 ` Kaushal Modi
2022-04-13 11:36 ` Max Nikulin [this message]
2022-04-16 3:07 ` Kaushal Modi
2022-04-17 11:42 ` Max Nikulin
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='t36cje$nms$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).