From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Lundin Subject: Re: Re: refile headline with inherited tags Date: Sun, 05 Apr 2009 11:19:00 -0500 Message-ID: References: <938fae2d0904041500x9312564sbf875a2ad366eba0@mail.gmail.com> <938fae2d0904050731w2be22005o352ae68aa022bbc3@mail.gmail.com> <938fae2d0904050736i3589154cx1871fc57813ed991@mail.gmail.com> <871vs79kav.fsf@legolas.norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LqV3w-0006N7-LR for emacs-orgmode@gnu.org; Sun, 05 Apr 2009 12:19:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LqV3q-0006Mu-Vj for emacs-orgmode@gnu.org; Sun, 05 Apr 2009 12:19:11 -0400 Received: from [199.232.76.173] (port=60273 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LqV3q-0006Mr-Sb for emacs-orgmode@gnu.org; Sun, 05 Apr 2009 12:19:06 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:58617) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LqV3q-0003eX-L2 for emacs-orgmode@gnu.org; Sun, 05 Apr 2009 12:19:06 -0400 In-Reply-To: <871vs79kav.fsf@legolas.norang.ca> (Bernt Hansen's message of "Sun\, 05 Apr 2009 11\:44\:56 -0400") 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: Bernt Hansen Cc: Eraldo Helal , Org-Mode Bernt Hansen writes: > I would definitely _not_ want this behaviour by default. I'm okay with > it being an option if it's useful. My tasks inherit tags from > #+FILETAGS: and I don't want those moving between files. Agreed. I would not want this to be default behavior (not that anyone is suggesting that it will be) because I rely heavily on filetags.=20 It seems to me that the whole reason for inherited tags is to allow context to determine the tags. Therefore, when I move an item to a different context, it's usually because I *want* it to have a different set of inherited tags.=20 Best, Matt > Eraldo Helal writes: > >> I am not sure if you understood what I meant... >> >> to calrify: >> when refiling headline1 to another file (C-c C-w) this headline does not= have the tag :tag1: in the new file. >> did your test refile it with the inherited tag? >> >> On Sun, Apr 5, 2009 at 16:31, Eraldo Helal wrote: >> >> On Sun, Apr 5, 2009 at 08:44, Carsten Dominik wrote: >> >> On Apr 5, 2009, at 12:00 AM, Eraldo Helal wrote: >> >> Today I refiled a headline that was part of a tree using inh= erited tags: >>=20=20=20=20=20=20=20=20=20=20=20=20 >> * topic1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :tag1: >> ** headline1 >> ** headline2 >> * topic2 >>=20=20=20=20=20=20=20=20=20=20=20=20 >> If I refile headline1 to another file... the tag "tag1" is n= ot on it anymore... >>=20=20=20=20=20=20=20=20=20=20=20=20 >> I am not sure if the best way to handle such cases is to add= the tag by hand and then refile it >> ... or if it could also be an option to apply all inherited = tags to it while refiling. >> >> I cannot reproduce this. =C2=A0What org version are you using? >>=20=20=20=20 >> org-mode version 6.25b >> >> - Carsten