From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: adjusting tags/keywords/priorities within remember templates Date: Tue, 11 Dec 2007 12:30:22 +0000 Message-ID: <20071211123022.GB12375@atlantic.linksys.moosehall> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J24Fn-0004GL-O7 for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 07:30:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J24Fm-0004Ez-Gr for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 07:30:26 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J24Fm-0004El-6v for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 07:30:26 -0500 Received: from mail.beimborn.com ([70.84.38.100]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1J24Fl-0005nk-TM for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 07:30:26 -0500 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id lBBCUO5A016267 for ; Tue, 11 Dec 2007 06:30:25 -0600 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id lBBCUOqW016262 for emacs-orgmode@gnu.org; Tue, 11 Dec 2007 12:30:24 GMT Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: org-mode mailing list My TODO.org files have per-file custom keyword (#+SEQ_TODO) and tag (#+TAGS) settings. I noticed a few areas for improving editing remember notes w.r.t. these: a) If editing a note in a *Remember* buffer which came from a template containing a custom keyword e.g. "NEXT", the org major-mode in the *Remember* buffer does not parse this as a keyword, which means that the usual shortcuts for changing priority and keyword treat "NEXT" as part of the description text. Fixing this in the case that the template has already specified a fixed destination file should be fairly easy - presumably by copying the per-file settings into the *Remember* buffer. In the other case where the destination file is not yet known, I agree that there is no easy way of doing this. b) %^g does not honour keystroke shortcuts for tags. c) %^g does not honour existing tags within the template. For example I would like to be able to include a tag string ":foo:" within the template and have the %^g code pre-select "foo", just as if the point was on an item tagged ":foo:" within a normal org file and I'd just pressed C-c C-c.