Re: Best way to implement project specific captures

[Jambunathan K <kjambunathan@gmail.com>]

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
>
>
>
>
>

--