emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Greg Minshall <minshall@acm.org>
To: org-mode <emacs-orgmode@gnu.org>
Subject: exporting link abbreviations
Date: Sat, 29 Mar 2014 17:57:34 +0100	[thread overview]
Message-ID: <9769.1396112254@gregminhallsmbp> (raw)

hi.  i'm playing with the example in the manual of a google map link
(gmap:).  technology is wonderful, and it's amazing (to simple-minded
me) to see the map pop up with the locations.

but, i'm less happy with how these links look when i've provided no
description and they are exported.  if i have a link like:
----
[[gmap:123 Main Street, Our Town, California, United States]]
----

what is *shown* on the exported web page (say) is something ugly like:
----
http://maps.google.com/maps?q=123%20Main%20Street,%20Our%20Town,%20California,%20United%20States
----

i'd rather not specify the address twice (once in the link tag, a second
time in the link description), out of laziness, i guess (but also for
2nd-normal-form'ity).

what i'd *like* the user to see on the web page is the address ("123
Main Street, Out Town, California, United States", in this example).

i could define a macro:
----
#+MACRO: gmap   [[gmap: $1][$1]]
----
and invoke it with
----
{{{gmap(123 Main Street Los Altos California United States)}}}
----

but then
1) i'd have to get rid of the commas in the address (it might
be nice to have a "$*" or some such to give the entire argument ); and

2) i wouldn't have the link active in my org-mode buffer itself
(something i find so magical, plus it helps entering the info to be able
to check the map before exporting).

i wonder if there's something i've missed?  or, if something could be
added?

cheers, Greg Minshall

next             reply	other threads:[~2014-03-29 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 16:57 Greg Minshall [this message]
2014-03-29 18:48 ` exporting link abbreviations Nicolas Goaziou
2014-03-29 21:42   ` Greg Minshall

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=9769.1396112254@gregminhallsmbp \
    --to=minshall@acm.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

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).