From: Carsten Dominik <email@example.com> To: Leo <firstname.lastname@example.org> Cc: email@example.com Subject: Re: [help] A org agenda command Date: Fri, 6 Feb 2009 08:51:21 +0100 [thread overview] Message-ID: <AC774E0F-66C3-4481-B9D2-FD537C550056@uva.nl> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Leo, I am afraid there is no "good" solution to this problem, you can always look at this two ways. Would you like to suggest a place where this behavior could be documented? - Carsten On Feb 4, 2009, at 4:34 PM, Leo wrote: > On 2009-02-04 14:22 +0000, Carsten Dominik wrote: >>> On Feb 4, 2009, at 10:41 AM, Leo wrote: >>> >>>> On 2007-04-24 11:18 +0100, Carsten Dominik wrote: >>>>> LEVEL=2/-DONE means that the search for stuck projects should >>>>> consider >>>>> any level 2 entry (i.e. starting with **) as a project, but should >>>>> immediately exclude projects where the top headline is marked >>>>> DONE. >>>> >>>> I remember we had a discussion to make LEVEL=2 respect >>>> `org-odd-levels-only' i.e. LEVEL=2 would mean headings starting >>>> with >>>> three "*" when org-odd-levels-only is t. >>>> >>>> However, after using this for such a long time I realise this is >>>> counter >>>> intuitive. Thus if possible please revert the change. > [...] >> Hi Leo, > > Hi Carsten, long time no 'see'. > >> this is possible, but will break what people use, I am afraid. > > I re-read our discussion. Realising that org-odd-levels-only can be > set > on a per file basis, now I think it is better to keep current > change. The remaining issue is to find a place to document the meaning > of LEVEL in org-stuck-projects. > > Actually I have removed customisation of org-stuck-projects and use > its > default value. With the flowing of so many new features into org, I > find > less need to inspect stuck projects. > >> - Carsten > > Best wishes, > -- > .: Leo :. [ sdl.web AT gmail.com ] .: I use Emacs :.
prev parent reply other threads:[~2009-02-06 8:24 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-18 23:15 Leo 2007-04-19 15:06 ` Jason F. McBrayer 2007-04-23 13:24 ` Carsten Dominik 2007-04-23 19:11 ` Carsten Dominik 2007-04-23 19:21 ` Leo 2007-04-24 8:58 ` Leo 2007-04-24 9:22 ` Leo 2007-04-24 10:18 ` Carsten Dominik 2007-04-24 10:58 ` Leo 2007-04-24 11:11 ` Leo 2007-04-24 11:38 ` Carsten Dominik 2009-02-04 9:41 ` Leo 2009-02-04 14:22 ` Carsten Dominik 2009-02-04 15:34 ` Leo 2009-02-06 7:51 ` 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=AC774E0F-66C3-4481-B9D2-FD537C550056@uva.nl \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [help] A org agenda command' \ /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).