emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: gnus org and tags
Date: Sat, 15 Oct 2016 13:14:30 +0000	[thread overview]
Message-ID: <87eg3hvjnt.fsf@mat.ucm.es> (raw)
In-Reply-To: 87shrz8isr.fsf@ucl.ac.uk

>>> "Eric" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:

   > On Thursday, 13 Oct 2016 at 16:02, Nick Dokos wrote:
   > [...]

   >> I have a single notes.org file (not an agenda file), where I do exactly what
   >> Eric described and I have defined keys to get to it fast: no more "where did I

   > As do I.  I guess this is a key part of this use case: it must be easy
   > to find those notes.  My (abridged) capture template looks like this:

   > #+begin_src emacs-lisp
   >   (setq org-capture-templates
   >         '(
   >           ("m" "Mail options")
   >           ("mt" "mailtodo"
   >            entry (file+datetree "~/s/notes/tasks.org")
   >            "* TODO %^{Task} : %:subject %^G\nSCHEDULED: %t\n- From :: %:from\n- Subject :: %:subject\n- Email :: %a\n\n%?" :kill-buffer t)
   >           ("mn" "mailnote"
   >            entry (file+headline "~/s/notes/notes.org" "general notes and tasks")
   >            "* %^{Title} : %:subject %^G\n- From :: %:from\n- Subject :: %:subject\n- Email :: %a\n\n%?\n\n%U")
   >           ))
   > #+end_src

Ok that is relatively cool.


   > Tag search etc. in org makes finding the notes relatively painless.  

How do you search, starting where?

   > As a bonus, the "mt" template is to allow me to get to INBOX 0 by making
   > sure I don't leave emails lying around unread or ticked.  If they need
   > further processing, an appropriate TODO task is created which links back
   > to the email.  This task is scheduled for immediate action by default
   > but obviously easily changed during the capture, very often by
   > unscheduling but adding a deadline, for instance.

For the imap backend?

  reply	other threads:[~2016-10-15 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d0bee8fd76144d01aca1878f3bb5fbb4@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-13  8:14 ` gnus org and tags Eric S Fraga
2016-10-13 11:10   ` Uwe Brauer
2016-10-13 16:02     ` Nick Dokos
     [not found]     ` <4b55752816294d39b6537391ad54a2b1@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-14  7:57       ` Eric S Fraga
2016-10-15 13:14         ` Uwe Brauer [this message]
     [not found]         ` <2c9fee5d1491480280cb0c85ebda9352@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-15 14:15           ` Eric S Fraga
2016-10-12  8:42 Uwe Brauer
2016-10-12 19:10 ` Eric Abrahamsen
2016-10-13 11:11   ` Uwe Brauer

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=87eg3hvjnt.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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).