emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Samuel Wales <samologist@gmail.com>
Cc: cesar mena <cesar.mena@gmail.com>,
	Leo Gaspard <orgmode@leo.gaspard.io>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: please read: bug when marking tasks done
Date: Sun, 27 Jan 2019 22:08:24 +0100	[thread overview]
Message-ID: <87zhrlx0zb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJcAo8vVhcH7ZZQ-BQ-Drr3nFUd1w-1sZZdmiVNT8UfW97amLg@mail.gmail.com> (Samuel Wales's message of "Tue, 15 Jan 2019 16:11:38 -0700")

Hello,

Samuel Wales <samologist@gmail.com> writes:

> commented repeater cookies does not have any of the above drawbacks.
> it might require a 3rd party tool to update its re if that tool uses
> repeaters.  this is not unprecedented.  the inactive repeater feature
> might already require a 3rd party tool to update its re.
>
> so upon reflection i think i'd go for commentable repeater cookies.
> it has a bonus too: whenever you turn off a repeater, it can be
> annoying that it zeroes out the interval.  commenting would fix that.
>
> perhaps there is a better, unmentioned solution?

I think commented repeaters add unnecessary overhead to the already
loaded timestamp syntax. This is, IMO, not a common enough need to
warrant even a minor syntax change.

However, we still need to move forward. So, I suggest to revert the
change about inactive timestamps. Inactive timestamps cannot be
repeated. This is less disruptive than the current situation. 

However, I also suggest to add a new hook, run after repeating
timestamps. With this hook, and a proper, user-specific, markup, it
should be possible to pick inactive timestamps in the section and
"repeat" them manually, i.e., on a case-by-case basis.

WDYT?

Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2019-01-27 21:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06  0:13 please read: bug when marking tasks done cesar mena
2019-01-06 23:49 ` Nicolas Goaziou
2019-01-07 14:52   ` Bernt Hansen
2019-01-07 15:20   ` cesar mena
2019-01-08 10:24     ` Nicolas Goaziou
2019-01-08 14:29       ` Bernt Hansen
2019-01-08 20:07       ` cesar mena
2019-01-09 22:50         ` Nicolas Goaziou
2019-01-10 14:15           ` cesar mena
2019-01-12 11:24             ` Nicolas Goaziou
2019-01-12 14:23               ` cesar mena
2019-01-12 19:37                 ` Samuel Wales
2019-01-12 21:02                   ` Samuel Wales
2019-01-13 15:00                   ` Nicolas Goaziou
2019-01-13 20:16                 ` Nicolas Goaziou
2019-01-13 21:52                   ` Samuel Wales
2019-01-15 14:24                     ` Bernt Hansen
2019-01-15 16:43                   ` cesar mena
2019-01-15 23:11                     ` Samuel Wales
2019-01-15 23:18                       ` Samuel Wales
2019-01-27 21:08                       ` Nicolas Goaziou [this message]
2019-01-29 14:58                         ` Robert Horn
2019-01-30 12:22                         ` cesar mena
2019-01-30 21:52                           ` Nicolas Goaziou
2019-01-31 10:25                             ` cesar mena
2019-01-31 23:17                               ` Samuel Wales

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=87zhrlx0zb.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=cesar.mena@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --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 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).