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 12:20:39 +0100	[thread overview]
Message-ID: <BA0B7A6C-6AE7-4B04-A315-E94794AEADEE@gmail.com> (raw)
In-Reply-To: <8762t49f7l.fsf@gnu.org>


On Feb 1, 2011, at 12:17 PM, Bastien wrote:

> Osamu OKANO <okano.osamu@gmail.com> writes:
>
>>> I'd like to org-archive-subtree keeping inherited tags.
>>> Can I do like blow?
>> I have found the solution by defadvice.
>> (defadvice org-archive-subtree
>>  (before add-inherited-tags-before-org-archive-subtree activate)
>>    "add inherited tags before org-archive-subtree"
>>    (org-set-tags-to (org-get-tags-at)))
>
> Thanks for this hack, I added it to Worg/org-hacks.org
>
>  http://orgmode.org/worg/org-hacks.html

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...

Cheers

- Carsten

  reply	other threads:[~2011-02-01 11:20 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 [this message]
2011-02-01 16:34       ` Bastien
2011-02-01 16:42         ` 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 \
    --in-reply-to=BA0B7A6C-6AE7-4B04-A315-E94794AEADEE@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).