emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Lex Fridman <lexfridman@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Auto-Fill (aka Word Wrap) of Headline Text
Date: Fri, 10 Jun 2011 10:41:02 -0300	[thread overview]
Message-ID: <4df21ef4.4f76e50a.09c9.6b7b@mx.google.com> (raw)
In-Reply-To: <BANLkTimexNpjc43uQMSnbq4_K2_w+4ajeQ@mail.gmail.com>



Yes, the best way is to start the TODO description in the next line without
the the stars (otherwise it would be another headline). I usually try to
create short headlines, specially if that headline has a bunch of tags. For
instance
: * TODO Some TODO item
:   Some length description of that TODO item or some steps I need to do
:   to. Here I can use auto-fill without a problem,

If the reason you wanted a long TODO item is to provide enough information
in the agenda, then tags and the CATEGORY property are a better option
IMHO.

For simpler TODO items (that is, no schedule, deadlines, tags, etc) you may
prefer a list with check-boxes such as
: - [ ] This may also be used as a king of TODO item. Notice that
:   differently from headlines you can use auto-fill here without any
:   problem.
: - [X] You can toggle the state as "done" and "not done" with "C-c C-c" in
:   the first line.

I find lists with check-boxes specially useful when I have TODO items that
can be broken down into a sequence of steps. In that case I create the TODO
item and put the bullet list inside. Such as
: * TODO Some task [/]
:   - [ ] Step 1
:   - [ ] Step 2
:   - [ ] Etc.
If you put "[/]" in the TODO headline then whenever you mark one step as
done with "C-c C-c" then org will update it to "[1/3]" and so on.

Of course you can also use sub-headlines also with the TODO keyword for the
steps if that is better for you. Then you can schedule each step
separately, for instance. In that case it starts to look more like a
project then a simple task, but just do the way that fits better for you.

--
Darlan

At Fri, 10 Jun 2011 00:12:12 -0400,
Lex Fridman <lexfridman@gmail.com> wrote:
> 
> So, for a to-do list, if I want to write a lengthy description for a
> to-do item, do I need to start the description on the next line
> without the stars (*) at the beginning?
> 
> I guess that makes sense. See, I thought of the headlines more as a
> bulleted list and not just a section heading tree...
> 
> If you have any suggestions or guidance, let me know. Either way,
> thanks for the sanity check.
> 
> - Lex
> 
> On Thu, Jun 9, 2011 at 11:58 PM, Darlan Cavalcante Moreira
> <darcamo@gmail.com> wrote:
> >
> > I think this is the correct behaviour, since headlines cannot span multiple
> > lines (as far as I know).
> >
> > This is also the case for the fill-paragraph command. If you try to call
> > fill-paragraph in a headline nothing happens.
> >
> > --
> > Darlan
> >
> > At Thu, 9 Jun 2011 17:56:02 -0400,
> > Lex Fridman <lexfridman@gmail.com> wrote:
> >>
> >> I enable auto-fill (aka word wrap) with:
> >> (add-hook 'org-mode-hook 'turn-on-auto-fill)
> >>
> >> Now, while editting an org file, I check the minor modes with "C-h m",
> >> and Auto-Fill is one of them. So when I type a long line it should
> >> automatically wrap, right? It does for regular text but NOT for when
> >> it's a headline (line starts with one or more *'s).
> >>
> >> I'm sorry if this is a trivial question, but I simply have not been
> >> able to find a solution. I'm using org-mode version 7.4 in emacs
> >> 23.2.1 on Ubuntu 11.04.
> >>
> >

  reply	other threads:[~2011-06-10 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 21:56 Auto-Fill (aka Word Wrap) of Headline Text Lex Fridman
2011-06-10  3:58 ` Darlan Cavalcante Moreira
2011-06-10  4:12   ` Lex Fridman
2011-06-10 13:41     ` Darlan Cavalcante Moreira [this message]
2011-06-10 14:23     ` Jambunathan K

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=4df21ef4.4f76e50a.09c9.6b7b@mx.google.com \
    --to=darcamo@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lexfridman@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).