From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Is LAST_REPEAT needed?
Date: Sat, 7 Jul 2012 10:06:32 -0700 [thread overview]
Message-ID: <CAJcAo8vkLtF779QHgY6fqyK-tZbf2ccAfYS9r3VKYDHJ_TJfuA@mail.gmail.com> (raw)
Unless I misunderstand, you can set
org-log-repeat to 'time to log state changes and also store
a LAST_REPEAT, or to nil to not log state changes and also
not store a LAST_REPEAT. You can't tell it to do one and
not the other.
I want to log state changes but not store LAST_REPEAT unless
it is algorithmically necessary. This is
because the information is often redundant.
Would it be possible to allow the user to set org-log-repeat accordingly?
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
reply other threads:[~2012-07-07 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJcAo8vkLtF779QHgY6fqyK-tZbf2ccAfYS9r3VKYDHJ_TJfuA@mail.gmail.com \
--to=samologist@gmail.com \
--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).