From: Matthew Lundin <email@example.com> To: Bernt Hansen <firstname.lastname@example.org> Cc: Eraldo Helal <email@example.com>, Org-Mode <firstname.lastname@example.org> Subject: Re: Re: refile headline with inherited tags Date: Sun, 05 Apr 2009 11:19:00 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Bernt Hansen's message of "Sun\, 05 Apr 2009 11\:44\:56 -0400") Bernt Hansen <email@example.com> 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. 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. Best, Matt > Eraldo Helal <firstname.lastname@example.org> 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 <email@example.com> wrote: >> >> On Sun, Apr 5, 2009 at 08:44, Carsten Dominik <firstname.lastname@example.org> wrote: >> >> On Apr 5, 2009, at 12:00 AM, Eraldo Helal wrote: >> >> Today I refiled a headline that was part of a tree using inherited tags: >> >> * topic1 :tag1: >> ** headline1 >> ** headline2 >> * topic2 >> >> If I refile headline1 to another file... the tag "tag1" is not on it anymore... >> >> 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. What org version are you using? >> >> org-mode version 6.25b >> >> - Carsten
next prev parent reply other threads:[~2009-04-05 16:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-04 22:00 Eraldo Helal 2009-04-05 6:44 ` Carsten Dominik 2009-04-05 14:31 ` Eraldo Helal 2009-04-05 14:36 ` Eraldo Helal 2009-04-05 15:44 ` Bernt Hansen 2009-04-05 16:19 ` Matthew Lundin [this message] 2009-04-05 16:18 ` Carsten Dominik
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Re: refile headline with inherited tags' \ /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
Code repositories for project(s) associated with this 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).