From: Sylvain Rousseau <thisirs@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien <bzg@altern.org>, emacs-orgmode@gnu.org
Subject: Re: Best way to implement project specific captures
Date: Thu, 23 Aug 2012 19:16:01 +0200 [thread overview]
Message-ID: <CAJ8n8322jGseULZGpS-WhD77UCiDV5UJSXDnJjfXCgcoxKx36A@mail.gmail.com> (raw)
In-Reply-To: <84119130-9EE5-4516-B230-AB578DF615FB@gmail.com>
2012/8/23 Carsten Dominik <carsten.dominik@gmail.com>:
> I am wondering if the following feature would be useful as well: Context sensitivity sounds most interesting to me if the same key would do different things in different contexts. I am not sure if this is possible with the current implementation? For example, I might want to have a bug recording key which creates an entry in a bug tracker file, but the file is different for different source files, and also the template and target type definitions might be different in different contexts.
For what it's worth I have pushed changes to github implementing this
and offering the choice to override templates or put them in a submenu
as well as a "stealing" mechanism to modify existing templates'
target.
I do not have access to Bastien's changes yet but from what I
understood we might run out of letters to identify templates. For
example, if we have 10 projects with 3 different templates each, we
already have 30 items in `org-capture-templates'... Or did I miss
something?
Anyway, I'm glad to see that this feature will be in a future org release!
Sylvain.
next prev parent reply other threads:[~2012-08-23 17:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 3:00 Best way to implement project specific captures Richard Riley
2012-08-22 11:48 ` Sylvain Rousseau
2012-08-22 14:37 ` Bastien
2012-08-22 14:38 ` Bastien
2012-08-22 18:04 ` Sylvain Rousseau
2012-08-23 9:13 ` Bastien
2012-08-23 10:36 ` Carsten Dominik
2012-08-23 11:09 ` Jambunathan K
2012-08-23 15:08 ` Bastien
2012-08-23 17:16 ` Sylvain Rousseau [this message]
2012-08-22 21:12 ` Richard Riley
2012-08-22 22:04 ` Richard Riley
2012-08-22 22:54 ` Richard Riley
2012-08-23 8:52 ` Sylvain Rousseau
2012-08-23 17:52 ` Richard Riley
2012-08-24 12:25 ` Bastien
2012-08-24 19:38 ` Richard Riley
2012-08-24 20:00 ` Bastien
2012-08-24 20:01 ` Bastien
2012-08-26 6:18 ` Richard Riley
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=CAJ8n8322jGseULZGpS-WhD77UCiDV5UJSXDnJjfXCgcoxKx36A@mail.gmail.com \
--to=thisirs@gmail.com \
--cc=bzg@altern.org \
--cc=carsten.dominik@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).