From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: Best way to implement project specific captures Date: Thu, 23 Aug 2012 16:39:06 +0530 Message-ID: <87a9xl27cd.fsf@gmail.com> References: <878vd79en7.fsf@altern.org> <874nnv9ekc.fsf@altern.org> <87a9xmyns1.fsf@altern.org> <84119130-9EE5-4516-B230-AB578DF615FB@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:60471) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T4VH6-00006X-Ev for emacs-orgmode@gnu.org; Thu, 23 Aug 2012 07:08:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T4VH4-0000PG-Ey for emacs-orgmode@gnu.org; Thu, 23 Aug 2012 07:08:32 -0400 Received: from mail-pz0-f41.google.com ([209.85.210.41]:53985) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T4VH4-0000PB-8b for emacs-orgmode@gnu.org; Thu, 23 Aug 2012 07:08:30 -0400 Received: by dadi14 with SMTP id i14so353146dad.0 for ; Thu, 23 Aug 2012 04:08:29 -0700 (PDT) In-Reply-To: <84119130-9EE5-4516-B230-AB578DF615FB@gmail.com> (Carsten Dominik's message of "Thu, 23 Aug 2012 12:36:06 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: Bastien , Sylvain Rousseau , emacs-orgmode@gnu.org May be dir local variables could be used? Carsten Dominik 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 wrote: > >> Sylvain Rousseau 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 > > > > > --