emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Wiesner <lunaryorn@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: HTML export and info: links
Date: Wed, 3 Jul 2013 17:57:02 +0200	[thread overview]
Message-ID: <CALf2awQ7UfwJNgrtosa_v43+W+sU4ZgaLwUmog3d0r-LRJB89Q@mail.gmail.com> (raw)
In-Reply-To: <87wqp83pvj.fsf@bzg.ath.cx>

2013/7/3 Bastien <bzg@gnu.org>:
> Sebastian Wiesner <lunaryorn@gmail.com> writes:
>
>> Ideally the HTML exporter would consult this database when exporting
>> info links, to find out where the corresponding HTML manual is
>> published.
>
> I see, thanks.  Is it safe to assume that htmlxref.cnf will always
> be located in /usr/share/texinfo/?  E.g. is it for you?

It's not actually located there at all.  My Texinfo is installed via
Homebrew into "~/.homebrew", hence my "htmlxref.cnf" is  at
"~/.homebrew/share/texinfo/htmlxref.cnf".  There is no
"/usr/share/texinfo/htmlxref.cnf".

Texinfo doesn't read a single file anyway, but all of these, and
merges them into a single file.  For my manual, I use an additional
"htmlxref.cnf" right next to the ".texi" source to add some missing
links.

The Org exporter should take all of these files, and merge them by the
same rules.  For system-wide configuration files, it should either try
to get the right prefix out of the "makeinfo" executable in
"exec-path" (as returned by "executable-find"), or take the list of
files from a customization option.  The latter is probably easier, and
more predictable to the user.

Implementing this likely amounts to a fair bit of work, which I was
somewhat disappointed to learn that Org doesn't do it already :)

  reply	other threads:[~2013-07-03 15:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 23:04 HTML export and info: links Sebastian Wiesner
2013-06-30 20:58 ` Bastien
2013-07-02 15:45   ` Sebastian Wiesner
2013-07-03  8:05     ` Bastien
2013-07-03  8:31       ` Sebastian Wiesner
2013-07-03  9:42         ` Bastien
2013-07-03 10:04           ` Sebastian Wiesner
2013-07-03 10:21             ` Bastien
2013-07-03 15:57               ` Sebastian Wiesner [this message]
2013-07-03 16:37                 ` Bastien
2013-07-03 16:42                   ` Sebastian Wiesner
2013-07-03 16:43                     ` Bastien
2013-07-03 17:00                       ` Sebastian Wiesner
2013-07-03 17:05                         ` Bastien
2013-07-03 17:09                           ` Sebastian Wiesner

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=CALf2awQ7UfwJNgrtosa_v43+W+sU4ZgaLwUmog3d0r-LRJB89Q@mail.gmail.com \
    --to=lunaryorn@gmail.com \
    --cc=bzg@gnu.org \
    --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).