emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: A nice feature to suggest
Date: Sun, 18 Feb 2007 22:09:42 +0100	[thread overview]
Message-ID: <d95b12669a35e9ef17af33c3b5b88b4f@science.uva.nl> (raw)
In-Reply-To: <m2lkj5vv38.fsf@sl392.st-edmunds.cam.ac.uk>


On Feb 11, 2007, at 11:37, Leo wrote:

> On 2007-02-11, Carsten Dominik said:
>
>> Why don't you "misuse" the ARCHIVE tag for this?  You could change
>> the name of the tag to LOCK or something?  Or maybe we could have a
>> list of tags that causes this behavior.
>
> For example, if I set "#+ARCHIVE: ::* Archived Tasks" and ARCHIVE tag
> "* Archived Tasks", then future archiving (org-archive-subtree) will
> create another "* Archived Tasks". Is this intended?

I have fixed this bug for 4.66.  Is there then still need for an 
additional way to lock entries from unfolding?

- Carsten


>
>> Hmmm, I guess you still want these to contribute to sparse trees and
>> the agenda.... ?
>>
>> - Carsten
>> On Feb 10, 2007, at 5:05, Leo wrote:
>>
>>> Hello Carsten,
>>>
>>> In org, if a subtree has a ARCHIVE tag, it will stay collapsed in
>>> visibility cycling. I found this functionality useful in two cases:
>>>
>>>   - When archive location is in the same file as .org file
>>>   - A tree with REPEATing items.
>>>
>>> Thus, I suggest if a heading of a subtree starts with '+', it will
>>> behave similar to a ARCHIVE tag during visibility cycling. For
>>> example, "** +Arhived Tasks...".
>>>
>>> Comments?
>>>
>>> Regards,
>>> -- 
>>> Leo <sdl.web AT gmail.com>                         (GPG Key: 
>>> 9283AA3F)
>>>
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>
>>>
>
> -- 
> Leo <sdl.web AT gmail.com>                         (GPG Key: 9283AA3F)
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>

--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477

  reply	other threads:[~2007-02-18 21:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10  4:05 A nice feature to suggest Leo
2007-02-11  6:32 ` Carsten Dominik
2007-02-11 10:37   ` Leo
2007-02-18 21:09     ` Carsten Dominik [this message]
2007-02-23  4:56       ` Leo
2007-02-25 19:54         ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2007-02-26  8:57 Egli Christian (KIRO 43)
2007-02-26 10:25 ` Bastien
2007-02-26 18:59   ` Daniel J. Sinder
2007-02-26 22:07     ` Bastien

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=d95b12669a35e9ef17af33c3b5b88b4f@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=sdl.web@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).