From: "Daniel J. Sinder" <djsinder@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: A nice feature to suggest
Date: Mon, 26 Feb 2007 10:59:50 -0800 [thread overview]
Message-ID: <45E32E26.8090607@gmail.com> (raw)
In-Reply-To: <m2lkilrzaz.fsf@hartur.local>
Bastien wrote:
> "Egli Christian (KIRO 43)" <christian.egli@credit-suisse.com> writes:
>
>>> **: a headline
>>> It would be convenient when you need to store inline tasks that are
>>> neither proper headlines nor list items. Such a headline wouldn't
>>> (un)fold, not because its content must stay invisible, but because it
>>> has no content.
>> What is the use case for this?
>
> For example :
>
> * A new project
>
> Here is some content describing the expected process for a project.
> Then i want to list some preliminary scheduled tasks to organize a
> few things :
>
> **: SOMEDAY Build a website
> **: NEXT Set up a discussion list
>
> Then i continue describing the project. My point is that this very
> three lines of content are not related to the headline "Set up a
> discussion list", but to the headline "A new project".
>
> For now, i use list items like this :
>
> - [ ] Build a website
> - [ ] Set up a discussion list
>
> But i can't add tags, schedule or archive them, etc., as you do with
> other kinds of (headlined) tasks. Does this describtion make more
> sense for you ?
>
> ...
>
> I'm aware this might first be confusing for the user, because this is
> not the general approach of org-mode. And i'm also aware this might
> be a very specific need. But i like org-mode for its flexibility and
> this was just a suggestion concerning "unfoldable" headline (while we
> were at it).
>
> Hope that makes more sens now :)
>
> Best,
>
This is much clearer to me, for one, and I see how the need can
arise. But it appears somewhat redundant in that you could always
re-organize your file to achieve the same effect (at the cost of a
deeper hierarchy). For example:
* A new project
** Expected process
Here is some content, etc.
*** SOMEDAY Build a website
*** NEXT Set up a discussion list
** Additional details
Then continue describing the project.
Dan
next prev parent reply other threads:[~2007-02-26 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 8:57 Re: A nice feature to suggest Egli Christian (KIRO 43)
2007-02-26 10:25 ` Bastien
2007-02-26 18:59 ` Daniel J. Sinder [this message]
2007-02-26 22:07 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2007-02-10 4:05 Leo
2007-02-11 6:32 ` Carsten Dominik
2007-02-11 10:37 ` Leo
2007-02-18 21:09 ` Carsten Dominik
2007-02-23 4:56 ` Leo
2007-02-25 19:54 ` 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=45E32E26.8090607@gmail.com \
--to=djsinder@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/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).