From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: GTD: Solving the bottleneck of converting incoming mails to NEXT actions
Date: Tue, 25 Sep 2007 18:29:54 +0200 [thread overview]
Message-ID: <87myvad7y5.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m3myvau3ri.fsf@cerebro.fsfeurope.org> (Georg C. F. Greve's message of "Tue, 25 Sep 2007 18:08:17 +0200")
"Georg C. F. Greve" <greve@fsfeurope.org> writes:
> and when making "~/Tools/Org/E.org" the default file name, things seem
> to work fine with the one exception that instead of creating the heading
> that was specified as default, it creates a "* Notes" heading.
I cannot reproduce this. Anyway, since the headings defined in the
templates are created once, you can create them by hand for now then
leave the rest of the config untouched.
> If a heading is created, why not creat the default?
It's what Org does for me.
> On changing the file names, I wanted to avoid that, because the file
> names are used in generating the agenda, and I don't want to lose four
> characters in the compact view.
The agenda display also uses the #+CATEGORY property. So that you can
have long-filenames-are-fun.org, if the category for this file is LFNAF
then the agenda will show LFNAF :)
> "Georg's Email TODO Org File -*- mode: org; -*-"
Agreed!
> So I consider that necessity a bug. The user has explicitly specified
> that this is an Org file, remember should not consider itself smarter
> than the user and insist on the file name extension.
Did you try to remember a note with "~/Tools/Org/E" and the string
"-*- mode: org; -*-"? The test is done with (org-mode-p), so the string
on the first line should be okay.
> b) remove file name extension sensitivity for Org mode files, or make
> it smart enough to *actually* read the buffer to see what mode it is
> in, because it should have to open the file to add the item.
This is currently the case.
--
Bastien
next prev parent reply other threads:[~2007-09-25 16:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 20:44 GTD: Solving the bottleneck of converting incoming mails to NEXT actions Georg C. F. Greve
2007-09-24 22:26 ` John Wiegley
2007-09-25 9:45 ` Georg C. F. Greve
2007-09-25 12:52 ` Bastien
2007-09-25 14:05 ` Georg C. F. Greve
2007-09-25 15:44 ` Bastien
2007-09-25 16:08 ` Georg C. F. Greve
2007-09-25 16:29 ` Bastien [this message]
2007-09-25 17:34 ` Carsten Dominik
2007-09-25 22:24 ` Georg C. F. Greve
2007-09-25 16:07 ` Carsten Dominik
2007-09-25 17:35 ` Nuutti Kotivuori
2007-09-25 18:20 ` Carsten Dominik
2007-09-24 22:52 ` Adam Spiers
2007-09-24 23:04 ` Adam Spiers
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=87myvad7y5.fsf@bzg.ath.cx \
--to=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).