emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien <bzg@altern.org>, Sylvain Rousseau <thisirs@gmail.com>,
	emacs-orgmode@gnu.org
Subject: Re: Best way to implement project specific captures
Date: Thu, 23 Aug 2012 16:39:06 +0530	[thread overview]
Message-ID: <87a9xl27cd.fsf@gmail.com> (raw)
In-Reply-To: <84119130-9EE5-4516-B230-AB578DF615FB@gmail.com> (Carsten Dominik's message of "Thu, 23 Aug 2012 12:36:06 +0200")


May be dir local variables could be used?

Carsten Dominik <carsten.dominik@gmail.com> writes:

> Hi Sylvain and Bastien,
>
> this is an interesting idea!
>
> 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.
>
> That would require a setup which defines a selection letter, and then
> an a list of (sets of) conditions and the corresponding template
> definition.
>
> Or am I going overboard here?
>
> - Carsten
>
> On 23 aug. 2012, at 11:13, Bastien <bzg@altern.org> wrote:
>
>> Sylvain Rousseau <thisirs@gmail.com> writes:
>> 
>>>> One possible enhancement: allow using only the capture/agenda
>>>> template instead of the full template in
>>> `org-context-capture-alist'
>>>> and `org-context-agenda-alist'.
>>> 
>>> Good idea! Adding it to my todo list with org-context ;-)
>> 
>> Actually I love your idea so much I just implemented it in core.
>> 
>> See these new options:
>> 
>>  org-agenda-custom-commands-contexts
>>  org-capture-templates-contexts
>> 
>> The basic idea is the same than yours, except you only need to
>> define rules for the agenda/capture keys.  It's also extending
>> the notion of context by allowing to check against modes, not
>> only files.
>> 
>> Please let me know what do you think.  And thanks again for this
>> simple and beautiful idea.
>> 
>> -- 
>> Bastien
>> 
>
> - Carsten
>
>
>
>
>

-- 

  reply	other threads:[~2012-08-23 11:08 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 [this message]
2012-08-23 15:08             ` Bastien
2012-08-23 17:16             ` Sylvain Rousseau
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=87a9xl27cd.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=bzg@altern.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=thisirs@gmail.com \
    /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).