emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: John Wiegley <johnw@newartisans.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: GTD: Solving the bottleneck of converting incoming mails to NEXT actions
Date: Tue, 25 Sep 2007 11:45:15 +0200	[thread overview]
Message-ID: <m3641z13kk.fsf@cerebro.fsfeurope.org> (raw)
In-Reply-To: <m2odfrn1ht.fsf@newartisans.com> (John Wiegley's message of "Mon, 24 Sep 2007 18:26:54 -0400")


[-- Attachment #1.1.1: Type: text/plain, Size: 386 bytes --]

On Mon, 24 Sep 2007 18:26:54 -0400
John Wiegley <johnw@newartisans.com> wrote: 

 jw> This is almost exactly what the Remember support provides for you,
 jw> if you have prompting turned on.  It will even add the link back to
 jw> the original e-mail.

I tried that, but it does not seem to work as described in the manual.

When trying to emulate what exists so far, I put


[-- Attachment #1.1.2: Type: application/emacs-lisp, Size: 344 bytes --]

[-- Attachment #1.1.3: Type: text/plain, Size: 663 bytes --]


into the .emacs.el. When calling remember, I get what I expect in terms
of being able to edit a note. But when trying to save an additional NEXT
action into one of the existing files, it always wants to overwrite the
file with the exact contents of the editing buffer.

Is this a known problem? Is there something I should look out for?

Regards,
Georg

-- 
Georg C. F. Greve                                 <greve@fsfeurope.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Join the Fellowship and protect your freedom!     (http://www.fsfe.org)
What everyone should know about DRM                   (http://DRM.info)

[-- Attachment #1.2: Type: application/pgp-signature, Size: 306 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2007-09-25  9:46 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 [this message]
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
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=m3641z13kk.fsf@cerebro.fsfeurope.org \
    --to=greve@fsfeurope.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=johnw@newartisans.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).