Hi Takafumi,
Takafumi Arakaki aka@gmail.com writes:
Anyway, I tried the head of master
(580add2f4148fea949a4db5550577911ee6d756e) and it works fine for me.
But I couldn't reproduce this behavior:
Note that timestamps need to be well formatted. If there is
a +3d repeat cookie and the
Hi, Bastien
Thanks for the patch and I am sorry for this late reply (especially
because I pushed maintainers to review my patch before...).
Anyway, I tried the head of master
(580add2f4148fea949a4db5550577911ee6d756e) and it works fine for me.
But I couldn't reproduce this behavior:
Note that
Hi Takafumi,
Takafumi Arakaki aka@gmail.com writes:
No comments? No one wants to have +3h in SCHEDULED?
I applied this patch, thanks.
Note that timestamps need to be well formatted. If there is
a +3d repeat cookie and the original timestamp doesn have any
indication for the hour, it
Hi Takafumi,
Takafumi Arakaki aka@gmail.com writes:
Basically, this patch changes all occurrence of [dwmy] with
[hdwmy] and adds (h . hour) to whata of org-auto-repeat-maybe.
I like this idea and I worked on a more complete patch.
I didn't replace dwmy by a constant though, this is not
Hi Takafumi,
Takafumi Arakaki aka@gmail.com writes:
No comments? No one wants to have +3h in SCHEDULED?
please be patient. Developers are working on their free time.
Also, please refine the ChangeLog of your patch by adding an Emacs
changelog entry with `C-x 4 a'. Because the patch is
No comments? No one wants to have +3h in SCHEDULED?
--
Takafumi
Hi,
Basically, this patch changes all occurrence of [dwmy] with
[hdwmy] and adds (h . hour) to whata of org-auto-repeat-maybe.
I think it is better to have some constant to indicate dwmy. So,
this pull request is rather a proof-of-concept and a feature request.
I didn't try to do it by myself
