emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Richard Kim <emacs18@gmail.com>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: patch for HTML links to GNU documents
Date: Mon, 28 Mar 2016 06:25:11 +0200	[thread overview]
Message-ID: <87d1qfb55k.fsf@mbork.pl> (raw)
In-Reply-To: <CAFq8O8uJhF5h=_Wcv8W83wqdaMn2KSxFoVs+Nc83Ey0hS45gJg@mail.gmail.com>


On 2016-03-28, at 00:55, Richard Kim <emacs18@gmail.com> wrote:

> Attached patch affects how 'info' links in org mode are converted to HTML
> links.  Today info links such as
>
>     [[info:emacs#List Buffers]]
>
> are converted to this HTML link:
>
>     <a href="emacs.html#List-Buffers">emacs#List Buffers</a>
>
> With the patch applied, the HTML link generated would be
>
>     <a href="
> http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#List-Buffers">emacs#List
> Buffers</a>
>
> The general idea is that couple of list variables describe how to map
> info file names to URLs so that those URL's would be used if available.
>
> One motivation for this patch is to make it easy for elisp package
> authors to to create links to wonderful emacs documents, because writing
> an org info-link to emacs manual in org files is trivial once you know
> the info node name.

That looks great; if it's accepted, I /immediatelly/ fetch the
bleeding-edge Org and start using it!!!

My use case is writing blog posts about Emacs using Org.

Thanks,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

  reply	other threads:[~2016-03-28  4:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27 22:55 patch for HTML links to GNU documents Richard Kim
2016-03-28  4:25 ` Marcin Borkowski [this message]
2016-03-28  8:59 ` Nicolas Goaziou
2016-03-29  5:24   ` Richard Y. Kim
2016-03-30 13:58     ` Nicolas Goaziou

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=87d1qfb55k.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=emacs-orgmode@gnu.org \
    --cc=emacs18@gmail.com \
    /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).