From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [ANN] New Org duration library
Date: Tue, 21 Feb 2017 19:22:54 +0100 [thread overview]
Message-ID: <87d1ebxv29.fsf@Rainer.invalid> (raw)
In-Reply-To: 8760k3toq2.fsf@nicolasgoaziou.fr
Nicolas Goaziou writes:
>> You seem to have (some of) these aliased to org-duration format somehow.
>> This breaks a lot of things because the format of the former variables
>> is not recognized. I got a bunch of errors about :hour not being a list
>> for instance. There surely must be a better way to handle the
>> transition?
>
> Fixed. Thank you.
Thanks, but will there be some helper function to migrate the old
customizations? I didn't even remember that I had customized this
variable until I couldn't clock in or out anymore (I remember now that I
customized it so it would record durations in hours, not days/hours).
>> Also, I find the documentation to be completely impenetrable.
>
> Great. Suggestions welcome.
I'd first need to understand what the options there really mean. It
seems that the variable can be set to just a symbol or (maybe) a string
or a list of conses. The conses form refer to org-duration-units, but
there the units are all defined as strings and no mention of the symbol
special that apparently is another possibility. I don't really see why
you'd mix symbols and strings in the same position. I have no idea what
"mixed mode" is supposed to be and what happens if I specify both
(special . h:mm) and ("h" . nil) for instance. Is the order of these
important?
>> Customization has offered to create a setting for org-duration-format
>> that's not even mentioned in the documentation.
>
> Would it be possible, by any chance, to get a glimpse of that setting?
I've set it to the symbol h:mm (shown as H:MM in customize) via the
value menu in customize. I might read the documentation incorrectly,
but to me it seems to say it should be the string "h:mm" instead. I'm
left to wonder if (h:mm) is the same or different from ((special . h.mm)).
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2017-02-21 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 14:10 [ANN] New Org duration library Nicolas Goaziou
2017-02-14 8:17 ` Detlef Steuer
2017-02-14 9:01 ` Nicolas Goaziou
2017-02-14 9:10 ` Detlef Steuer
2017-03-03 2:31 ` David Mann
2017-03-03 2:46 ` David Mann
2017-03-03 11:24 ` Nicolas Goaziou
2017-02-21 17:24 ` Achim Gratz
2017-02-21 17:53 ` Nicolas Goaziou
2017-02-21 18:22 ` Achim Gratz [this message]
2017-02-21 18:51 ` Nicolas Goaziou
2017-02-21 19:47 ` Achim Gratz
2017-02-22 10:56 ` Nicolas Goaziou
2017-02-22 11:50 ` Malcolm Purvis
2017-03-17 8:00 ` Nicolas Goaziou
2017-02-22 15:33 ` Aaron Ecay
2017-02-22 19:01 ` Nicolas Goaziou
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=87d1ebxv29.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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 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.