Thank you. Happy that I found a real error and didn't just waste everyone's
time. Also happy to report that I updated org to 9.5.4 and all is well.
Best,
R
On 3 Jun 2022, at 9:08, Ihor Radchenko wrote:
> Ihor Radchenko writes:
>
>>> I am running Emacs 25 (Aquamacs). So, maybe this code
Hi Ihor,
Clear! Thank you so much!
Please just ignore this patch, and close this ticket.
B.R.
Lin
Ihor Radchenko writes:
>> I am running Emacs 25 (Aquamacs). So, maybe this code requires Emacs 26?
>> If so, it would be nice if org-mode 9.5.3 was tagged as incompatible
>> with Emacs 25? (It would also be nice if package mode supported
>> roll-back, but that's OT here!)
>
> Thanks for
Gregor Zattler writes:
>>> org-parse-time-string: Not an Org time string: [20zznn22-05-30 Mo 11:34]
>>>
>>> And then there is a dangling
>>>
>>> CLOCK:
>>>
>>> line without timestamps at the expected line in my org file.
>>>
>>> It took a while till I realized that there was a corrupted
>>>
Robert Goldman writes:
> I just updated org-mode using package.el and got release 9.5.3
>
> Now I get an error in `org-at-timestamp-p` (OATP), which is invoked when
> calling `org-agenda`.
> ```
> (rx (or (regexp org-ts-regexp3) ; here
> (regexp org-element--timestamp-regexp)))
> ```
>
William Denton writes:
>> For me, this looks like either a mixed installation (please post the
>> output of M-x org-version) or some third-party package misbehaving.
>
> M-x org-version says:
>
> Org mode version 9.5.3 (release_9.5.3-511-g8e69ad @
> /usr/local/src/org-mode/lisp/)
Is
Max Nikulin writes:
> On 30/05/2022 10:14, Ihor Radchenko wrote:
>> I applied the discussed two patches onto main via 1525a5a64 and
>> f6f26d4ce. The suggested amendments were incorporated.
>
> So Greg's feature request is implemented and it is great.
>
> I am less confident with
Ihor Radchenko writes:
> Instead of fontifying elements individually via regexps, we can leverage
> org-element-map, org-element-parse-buffer, org-element-cache, and
> jit-lock-mode. Each type of Org element/object can be assigned with a
> fontification function accepting a single argument - the
Hi everyone,
is there support for abbreviations in org-mode? Something like what the
acro package provides for latex, i.e., assemble a list of all used
abbreviations, use a full form when an abbreviation is used for the
first time, the abbreviated form afterwards. If that does not exist:
What
Ihor Radchenko writes:
> 1. org-protecting-blocks is an internal auxiliary variable used to
>determine which blocks should be fontified using different major
>mode.
>It's value is ("src" "example" "export")
>So, #+begin_src lang and #+begin_export lang are fontified according
>
Ihor Radchenko writes:
> Ihor Radchenko writes:
>
>> Instead of fontifying elements individually via regexps, we can leverage
>> org-element-map, org-element-parse-buffer, org-element-cache, and
>> jit-lock-mode. Each type of Org element/object can be assigned with a
>> fontification function
Thanks, I'll take a look at it.
Cheers,
On Thu, Jun 02 2022, Ihor Radchenko wrote:
> "Daniel E. Doherty" writes:
>
>> Again, thanks for your thoughts. All, however, ruin the look of the
>> tables. Could you, perhaps, point me to where in the vast org code,
>> strings are converted to numbers
Lin Sun writes:
> And changing the "CAPTION" to "PROPERTY" in the foot script, is it correctly?
> Thanks
Adding PROPERTY works by accident. (I am wondering what is the logic
behind this idea - there is no meaningful semantic meaning for PROPERTY
keyword in this context)
When you have
13 matches
Mail list logo
