From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: #+HOMEPAGE in metadata - feature request?
Date: Fri, 21 Mar 2014 23:26:26 -0400 [thread overview]
Message-ID: <87a9cizzfh.fsf@gmail.com> (raw)
In-Reply-To: 20140322022316.1f414dd7@aga-netbook
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> Dnia 2014-03-22, o godz. 00:44:40
> Bastien <bzg@gnu.org> napisał(a):
>
>> Hi Marcin,
>>
>> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>>
>> > So the problem is: it would be (imho) useful to have a "homepage"
>> > added to general metadata, but it is not clear how to translate
>> > this to e.g. LaTeX's (rather ancient) concept of metadata.
>> > (Interestingly, some other classes, e.g. memoir, koma-script and
>> > titlepage, also do not seem to cater for this need. I'm going to
>> > ask on TeX.SE if there's any class/package enabling putting a url
>> > on the titlepage...) So while (I assume) adding a #+HOMEPAGE
>> > field/option in Org would be easy, it is not obvious how to render
>> > it for different exporters.
>>
>> Thanks for the explanations, I get it now; but unless I'm really tired
>> (could be), you only mention backends that do not support a concept of
>> "homepage"... right?
>
> Right. I did not really use other backends; what drives my suggestion
> is a /need/ for a url in the titlepage, not an /existence/ of such
> feature in other tools. (It would be hard for me to believe that I'm
> the only one needing this, btw...)
>
For latex, the ams classes (amsart, etc) provide a \urladdr macro.
I imagine something similar could be easily added to the standard
classes. Or you can cheat:
#+AUTHOR:
#+LATEX_HEADER: \author{A.U.Thor\thanks{http://www.foo.org}
--
Nick
prev parent reply other threads:[~2014-03-22 3:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 12:37 #+HOMEPAGE in metadata - feature request? Marcin Borkowski
2014-03-21 13:07 ` Bastien
2014-03-21 14:29 ` Waldemar Quevedo
2014-03-21 20:16 ` Marcin Borkowski
2014-03-21 23:44 ` Bastien
2014-03-22 1:23 ` Marcin Borkowski
2014-03-22 3:26 ` Nick Dokos [this message]
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=87a9cizzfh.fsf@gmail.com \
--to=ndokos@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).