From: Jari Aalto <jaalto@cante.net>
To: emacs-orgmode@gnu.org
Subject: [PATCH] org-link-abbrev-alist improve docstring "linkword"
Date: Mon, 23 Feb 2009 01:30:09 +0200 [thread overview]
Message-ID: <87d4darqwu.fsf@jondo.cante.net> (raw)
> [Carsten Dominik]
> please send your reports to emacs-orgmode@gnu.org, there I have
> them in one place, and a public record is created of your question
> and any answers - and, most importantly, someone else might
> answer for me.
>
> Link abbreviation starts with a "linkword" similar to http or so,
> and the conventions in Org require it to be a word, starting
> with a character, followed by letters, numbers, "-" and "_".
Let's move that information available for C-h v.
Jari
2009-02-22 Jari Aalto <jari.aalto@cante.net>
* org.el (org-link-abbrev-alist-local): Document what characters
are allowed in linkword.
From dff73c60674054b5054f10a2d2d1dc66f00eb4fb Mon Sep 17 00:00:00 2001
From: Jari Aalto <jari.aalto@cante.net>
Date: Mon, 23 Feb 2009 01:16:41 +0200
Subject: [PATCH] org.el: improve doctring org-link-abbrev-alist-local
Signed-off-by: Jari Aalto <jari.aalto@cante.net>
---
lisp/org.el | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index c0fd99f..d43bba1 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -928,6 +928,9 @@ links in Org-mode buffers can have an optional tag after a double colon, e.g.
[[linkkey:tag][description]]
+NOTE: The 'linkkey' must be a word word, starting with a
+character, followed by letters, numbers, characters '-' or '_'.
+
If REPLACE is a string, the tag will simply be appended to create the link.
If the string contains \"%s\", the tag will be inserted there. Alternatively,
the placeholder \"%h\" will cause a url-encoded version of the tag to
--
1.5.6.5
reply other threads:[~2009-02-22 23:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87d4darqwu.fsf@jondo.cante.net \
--to=jaalto@cante.net \
--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).