emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: cesar mena <cesar.mena@gmail.com>
To: cesar mena <cesar.mena@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>,
	Leo Gaspard <orgmode@leo.gaspard.io>
Subject: Re: please read: bug when marking tasks done
Date: Tue, 15 Jan 2019 11:43:24 -0500	[thread overview]
Message-ID: <CAL+-AoetZ0h-rQ9+jX82203GGx9oH-SZW3iwjFaVF-5f1NrigQ@mail.gmail.com> (raw)
In-Reply-To: <87bm4kxqhn.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]

hello,

On Sun, Jan 13, 2019 at 3:16 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> cesar mena <cesar.mena@gmail.com> writes:
>
> > i'm ok going with the verbatim syntax - rescheduled lines will now look
> > like (w/o the double quotes?):
> >
> >   - Rescheduled from =[2019-02-05 Tue .1m]= on [2018-09-29 Sat 18:50]
>
> Thinking about it, another possibility is to add a variable, e.g.,
> `org-repeat-inactive-timestamps', letting the user choose what to do
> with inactive time stamps. I think it would default to nil.
>
> This would be a more conservative solution; however, this would
> contradict releases notes for Org 9.2.
>
> WDYT?
>
>
this works of course and it doesn't affect current workflows while allowing
for inactive repeating timestamps.

the caveat would be that in the case of repeating timestamps, setting both
`org-log-into-drawer' and `org-repeat-inactive-timestamps' to a true value
will overwrite "Rescheduling" entries from the :LOGBOOK:.  in some limited
sense the two are incompatible (which would require the verbatim syntax).

with that understanding, and the fact that repeating inactive timestamps is
a new "feature" my vote is for `org-repeat-inactive-timestamps'.  this
leaves room down the road, should the need arise, for verbatim syntax in
log entries.

regards,
-cm

[-- Attachment #2: Type: text/html, Size: 3293 bytes --]

  parent reply	other threads:[~2019-01-15 16:56 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 [this message]
2019-01-15 23:11                     ` Samuel Wales
2019-01-15 23:18                       ` Samuel Wales
2019-01-27 21:08                       ` Nicolas Goaziou
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=CAL+-AoetZ0h-rQ9+jX82203GGx9oH-SZW3iwjFaVF-5f1NrigQ@mail.gmail.com \
    --to=cesar.mena@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@leo.gaspard.io \
    /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).