From: emacs18@gmail.com (Richard Y. Kim)
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Links to Info manuals in exported HTML/LaTeX
Date: Thu, 27 Aug 2015 19:10:29 -0700 [thread overview]
Message-ID: <qtmsi74xiwa.fsf@gmail.com> (raw)
In-Reply-To: <87io81xhwj.fsf@mbork.pl> (Marcin Borkowski's message of "Thu, 27 Aug 2015 10:19:40 +0200")
Marcin Borkowski <mbork@mbork.pl> writes:
> Hi all,
>
> it seems that links to Info manuals are broken in HTML and LaTeX export
> (and possibly in other backends, too).
>
> Would it make sense to make them work, i.e., link to the official web
> versions, at least for standard Info manuals, like Emacs manual, Elisp
> reference or Org manual?
It is not broken for my use case. I like the fact that
[[info:emacs#Top][Emacs Manual]]
is turned into
<a href="emacs.html#Top">Emacs Manual</a>
because I generated emacs.html, elisp.html, org.html, etc. all in
my ~/public_html/ or sub-directories. Hence
<a href="emacs.html#Top">Emacs Manual</a>
works fine for my use case. It is a lot faster to access GNU manuals
when they are all on local host.
Should the current behavior be the default? Perhaps not. I believe
makeinfo and/or texi2html generates html links pointing to the official
pages at gnu.org. This could be the default behavior, but I hope not
the *only* behavior. If current export code is to be changed, I would
like to see user selectable option so that I can choose to use the
current behavior.
next prev parent reply other threads:[~2015-08-28 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 8:19 Links to Info manuals in exported HTML/LaTeX Marcin Borkowski
2015-08-28 2:10 ` Richard Y. Kim [this message]
2015-08-28 8:41 ` Suvayu Ali
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=qtmsi74xiwa.fsf@gmail.com \
--to=emacs18@gmail.com \
--cc=emacs-orgmode@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/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).