From: cesar mena <cmena@pobox.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Do you like to have your TODOs at the same headline level?
Date: Tue, 1 Sep 2015 09:15:14 -0400 [thread overview]
Message-ID: <CAL+-Aof1fHwVbTh3TE3bEhrgphenQ=7-on8crNiLiZD6FPoifQ@mail.gmail.com> (raw)
In-Reply-To: <86a8tdeuxk.fsf@example.com>
i do the same; 4 char states - with box around them
(setq org-todo-keyword-faces
'(("TODO" . (:foreground "pink"
:box (:line-width 1 :style none)))
("NEXT" . (:foreground "green"
:box (:line-width 1 :style none)))
("WAIT" . (:foreground "yellow"
:box (:line-width 1 :style none)))
("HOLD" . (:foreground "light blue"
:box (:line-width 1 :style none)))
("CNC!" . (:foreground "gray"
:box (:line-width 1 :style none)))
("DONE" . (:box (:line-width 1 :style none)))))
-cm
On Wed, Aug 26, 2015 at 3:00 PM, Sebastien Vauban
<sva-news@mygooglest.com> wrote:
> dboyd2@mmm.com (J. David Boyd) writes:
>> Sebastien Vauban <sva-news@mygooglest.com> writes:
>>> William Denton <wtd@pobox.com> writes:
>>>> I'm trying to spend more time in a sparse tree view where I just see
>>>> TODOs (C-c / t). I didn't like having the TODOs at different levels
>>>> of indentation, though. I prefer seeing them all lined up, so
>>>> I moved them all to be fourth-level headline. It's visually
>>>> pleasing, and I don't care if a second-level headline has
>>>> a fourth-level child without a third-level one.
>>>>
>>>> Do other people do this?
>>>
>>> No, and I don't think that's sane. It would be logical to expect
>>> problems at export time (to LaTeX, among others) and in Org-lint.
>>>
>>> I try to put all the tasks at the 2nd level, the 1st level being
>>> reserved for big sections such as "Administration", "Tasks", "Team",
>>> etc.
>>>
>>> I'm very rigorous about expecting that all my "project management"
>>> documents can be exported (without loosing subtrees or generating error)
>>> to HTML (as the very first goal) and to LaTeX (as the second one).
>>>
>>> OTOH, I don't deny your wish to get things aligned; that's why I've
>>> opted to 4-char todo states only!
>>
>> 4-char todo states? How about a list? I can't picture how to
>> abbreviate some things...
>
> Sure. Here it is:
>
> - TODO :: Open, not (yet) started.
> - STRT :: In progress, working on, doing.
> - WAIT :: On hold, assigned, feedback.
> - SDAY :: Someday, maybe, perhaps, wish.
> - DONE :: Completed, closed, resolved.
> - CANX :: Wontfix, rejected.
>
> The only exception, but that's on purpose is "NEW" for things going to
> the CollectBox.
>
> Best regards,
> Seb
>
> --
> Sebastien Vauban
>
>
prev parent reply other threads:[~2015-09-01 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 19:54 Do you like to have your TODOs at the same headline level? William Denton
2015-08-26 10:31 ` Sebastien Vauban
2015-08-26 16:08 ` J. David Boyd
2015-08-26 19:00 ` Sebastien Vauban
2015-09-01 13:15 ` cesar mena [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='CAL+-Aof1fHwVbTh3TE3bEhrgphenQ=7-on8crNiLiZD6FPoifQ@mail.gmail.com' \
--to=cmena@pobox.com \
--cc=emacs-orgmode@gnu.org \
--cc=sva-news@mygooglest.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).