all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Samuel Wales <samologist@gmail.com>
Cc: Eric S Fraga <esflists@gmail.com>,
	Ken Mankoff <mankoff@gmail.com>,
	Leo Gaspard <orgmode@leo.gaspard.io>,
	emacs-orgmode@gnu.org
Subject: Re: Tasks performed on a certain day
Date: Thu, 08 Nov 2018 18:34:16 +0100	[thread overview]
Message-ID: <87lg63cw2v.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJcAo8s+PxihqGhfKp1bspC5hqRfgVAacbrQ77x+71tiSHApBg@mail.gmail.com> (Samuel Wales's message of "Wed, 7 Nov 2018 18:31:09 -0700")

Hello,

Samuel Wales <samologist@gmail.com> writes:

> i also call them event.
>
> i have code below that shows them in agenda as "Event:" in their own face.
>
> i think there was a proposal a while back to have them be in the
> planning line [the one just after the header] as EVENT: <...> along
> with closed, scheduled, and deadline.  i kinda liked that proposal
> [great for 3rd party tools, maybe even a bit faster, consistency] but
> it never went anywhere.  :]

It is tempting to add a new planning keyword, indeed. Agenda generation
would be much faster (looking for timestamps everywhere is the slowest
part of agenda generation).

However, I think some users need to have multiple so-called events in
the same headline, e.g., for irregularly repeating tasks.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2018-11-08 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 13:59 Tasks performed on a certain day Leo Gaspard
2018-11-06 17:38 ` Eric S Fraga
2018-11-07  1:10   ` Leo Gaspard
2018-11-07  1:49     ` Ken Mankoff
2018-11-07 11:33       ` Leo Gaspard
2018-11-07 11:45         ` Marcin Borkowski
2018-11-08  1:31           ` Samuel Wales
2018-11-08 17:34             ` Nicolas Goaziou [this message]
2018-11-09 10:41               ` Gregor Zattler
2018-11-07  8:04 ` Marcin Borkowski

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lg63cw2v.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=esflists@gmail.com \
    --cc=mankoff@gmail.com \
    --cc=orgmode@leo.gaspard.io \
    --cc=samologist@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.