From: Bastien <bastien.guerry@wikimedia.fr>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Syntax to trigger org-capture (Re: camel.el, for CamelCase links)
Date: Fri, 06 Aug 2010 11:06:37 +0200 [thread overview]
Message-ID: <87eiec8602.fsf_-_@gnu.org> (raw)
In-Reply-To: <87zkx14bst.fsf@gmx.de> (Sebastian Rose's message of "Thu, 05 Aug 2010 12:02:42 +0200")
When you think of CamelCase and on-the-fly creating of non-existing
files/headlines, it's just another way of *capturing* stuff.
Why not defining some simple syntax to trigger the capture mechanism
from special links?
For example:
"I write a reference to a >c:newfile which I can create later."
- The ">c:newfile" is a link.
- The ">c" is a link abbreviation.
- The ">" part is the syntax for link abbrevations to trigger a capture.
- The "c" part is the keybinding of capture template to call.
- The "newfile" would be passed on as a variable for the (nth 3) of the
template (we could have several variables separated by "#"
This would combine the flexibility of on-the-fly file creation and of
the capture mechanism, allowing multiple templates.
What do you think?
--
Bastien
next prev parent reply other threads:[~2010-08-06 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:36 camel.el, for CamelCase links David O'Toole
2010-08-03 16:27 ` Bastien
2010-08-04 20:50 ` Olivier Berger
2010-08-04 22:28 ` Michael Gilbert
2010-08-05 5:36 ` Olivier Berger
2010-08-05 10:02 ` Sebastian Rose
2010-08-06 9:06 ` Bastien [this message]
2010-08-07 6:31 ` Syntax to trigger org-capture (Re: camel.el, for CamelCase links) Carsten Dominik
2010-08-07 6:47 ` camel.el, for CamelCase links Carsten Dominik
2010-09-13 17:45 ` Marcelo de Moraes Serpa
2010-09-15 18:56 ` Marcelo de Moraes Serpa
2010-09-19 21:40 ` Bastien
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=87eiec8602.fsf_-_@gnu.org \
--to=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian_rose@gmx.de \
/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).