Ken Mankoff writes:
> On 2018-12-08 at 09:47 -0800, Leo Gaspard wrote:
>> However, I think it may be a good idea to allow eg. this kind of
>> timestamps:
>> <2018-02-04 Tue evening> That would be handled as though it
>> was eg. <2018-02-04 Tue 18:00-22:00> (which would be configurable),
Hi Leo,
Leo Gaspard writes:
> In the process of migrating all my self-organization to org-mode, I
> noticed there is something that cannot currently be encoded in
> timestamps: fuzzy times, where an appointment is made for “Dec 4, Tue,
> evening” but with the hours not yet fixed.
> ...
> To be
Hi,
I realize I'm running an older version of org-mode (8.3.3), but things are
working for me generally and I'm not in a position to monkey around with my
environment right now.
Anyway, something strange. A few months ago, I was able to export to ODT and
the file would open in LibreOffice.
On Mon, 10 Dec 2018 07:25:13 +0800 briangpowell
wrote
> * Suggest you try changing this:
>
> ("\\.odt\\'" . "libreoffice6.0 %s"
> * To this instead:
>
> ("\\.odt\\'" . "libreoffice %s"
> --since "libreoffice6.0" is a specific link that is subject to change--not
> only by
On 2018-12-09 at 17:45 -0800, James Harkins wrote:
> Anyway, the solution for now, as I'm under some time pressure, is to
> declare that ODT export is broken on my system until I can scrape
> together some time to upgrade org. PDF export is actually OK for now
> (and working fine).
But export
Hi all,
I'm playing around with `org-batch-agenda-csv'. My question is, what is
"String with extra planning info"? A quick experiment shows that it is
what is displayed in the "normal" agenda right after the category.
Also, what is "numerical priority" and how is it computed? I could find
any
Hi Richard,
Richard Lawrence writes:
> What about just adding a tag (:evening:, :morning:, etc.) to represent a
> fuzzy time, with a plain date stamp, like <2018-12-04>?
>
> That would allow you to easily create a custom agenda view containing
> just entries with fuzzy times (if they have a
* Suggest you try changing this:
("\\.odt\\'" . "libreoffice6.0 %s"
* To this instead:
("\\.odt\\'" . "libreoffice %s"
--since "libreoffice6.0" is a specific link that is subject to change--not
only by you but by your chosen operating system package manager
Unless of course, you
Hello,
Allen Li writes:
> Attached patch fixing this.
>
> This was caused by a bug in a feature that I did not realize existed
> (prefixing each line in %i). I have also included patches to clarify
> the documentation.
I applied the documentation patch. Thank you.
Regards,
--
Nicolas
