emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: emacs-orgmode@gnu.org, Osamu OKANO <okano.osamu@gmail.com>
Subject: Re: Re: org-archive-subtree keeping inherited tags
Date: Tue, 1 Feb 2011 17:42:22 +0100	[thread overview]
Message-ID: <6A6A36FE-459E-4BF1-BB0F-EF5C6824DC26@gmail.com> (raw)
In-Reply-To: <87mxmflnnk.fsf@altern.org>


On Feb 1, 2011, at 5:34 PM, Bastien wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> It might be useful to consider making this as part of the normal  
>> archiving
>> procedure, when archiving to a different file.  Maybe subject to a  
>> variable
>> - but I do like the idea to be able to look at archived entries  
>> with all
>> tags in place.  Since in the Archive, entries are usually all  
>> siblings,
>> there is no useful inheritance. Explicitly copying the tags into each
>> archived entry is a good way to go to retain searchability of tags...
>
> I've now implemented this.
>
> You can customize `org-archive-subtree-add-inherited-tags' which
> defaults to 'infile so that infile subtree archiving will append
> inherited tags to the archived subtree.
>
> If `org-archive-save-context-info' contains the itags symbol,
> inherited tags will aslo be added to the ARCHIVE_ITAGS property.
>
> Thanks for this idea!

Great.

- Carsten

      reply	other threads:[~2011-02-01 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 14:16 org-archive-subtree keeping inherited tags Osamu OKANO
2011-01-28 13:47 ` Osamu OKANO
2011-01-28 18:20   ` Carsten Dominik
2011-02-01 11:17   ` Bastien
2011-02-01 11:20     ` Carsten Dominik
2011-02-01 16:34       ` Bastien
2011-02-01 16:42         ` Carsten Dominik [this message]

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 \
    --in-reply-to=6A6A36FE-459E-4BF1-BB0F-EF5C6824DC26@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bastien.guerry@wikimedia.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=okano.osamu@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).