From: ST <smntov@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Emacs-orgmode@gnu.org
Subject: Re: Link abbreviations: include abbreviation table and linkwords with spaces
Date: Tue, 13 Mar 2018 10:51:05 +0200 [thread overview]
Message-ID: <1520931065.1930.4.camel@gmail.com> (raw)
In-Reply-To: <87r2ooanzd.fsf@nicolasgoaziou.fr>
> > after reading "4.6 Link abbreviations" of the manual I have two
> > questions:
> >
> > 1. is it possible to define linkwords with spaces, like this: [[Harry
> > Potter:Chapter1]], it looks much more nice than
> > [[Harry_Potter:Chapter1]]?
>
> I think so.
If yes, then it's really worth mentioning this fact in the manual (4.6
Link abbreviations) because ones get the impression that only - and _
are allowed. One of the most strong sides of org is its readability as
raw text and in this case space makes link more readable.
>
> > 2. is it possible to define a "links catalog" of abbreviations, like
> >
> > #+LINK: bugzilla http://10.1.2.9/bugzilla/show_bug.cgi?id=
> > #+LINK: google http://www.google.com/search?q=%s
> >
> >
> > and then include them in all possible org files with
> >
> > #+INCLUDE: "links_catalog.org"
>
> SETUPFILE would be more appropriate. Also, you can define abbreviations
> globally. See `org-link-abbrev-alist'.
I wanted to avoid `org-link-abbrev-alist' as it is Emacs specific, while
#+INCLUDE: is part of the org-mode standard which should work also on
other platforms (theoretically).
Thank you!
next prev parent reply other threads:[~2018-03-13 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 20:35 Link abbreviations: include abbreviation table and linkwords with spaces ST
2018-03-12 23:11 ` Nicolas Goaziou
2018-03-13 8:51 ` ST [this message]
2018-03-13 9:18 ` Nicolas Goaziou
2018-03-13 11:53 ` ST
2018-03-14 14:02 ` Nicolas Goaziou
2018-03-14 18:32 ` ST
2018-03-16 7:38 ` ST
2018-03-16 21:57 ` Nicolas Goaziou
2018-03-18 9:20 ` ST
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=1520931065.1930.4.camel@gmail.com \
--to=smntov@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).