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 /usr/local/
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)))
> ```
>
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
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
>>> times
On 31 May 2022, Ihor Radchenko wrote:
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/)
Can you tr
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`.
I checked the repository and the problem is in commit 1f617727f1, which
added to this function the following code block:
```
- (let*
On 27/05/2022 22:18, Ihor Radchenko wrote:
Max Nikulin writes:
With this exact init.el, trying to run
(let ((process-connection-type nil))
(start-process-shell-command "1" nil "xdg-open ~/.bashrc"))
Does it mean that you can not reproduce it with emacsclient instead of
xdg-open? Anyway I
Hi Ihor,
Thank you for the investigation, verify insight, I'll avoid this snapshot from
my org files.
And changing the "CAPTION" to "PROPERTY" in the foot script, is it correctly?
Thanks
B.R.
Lin
On 02/06/2022 12:02, Phil Estival wrote:
Still, the writing experience is much improved
when comments are allowed inside paragraphs
without disrupting the publication, and this
definitely worth a few modifications.
There are at least a couple of workarounds for inline comments, however
some ca
On 01/06/2022 17:33, Alessandro Bertulli wrote:
> P.S. Alessandro, could you, please, response to mails using "reply"
> button. You messages lack of In-Reply-To and References headers, so at
> least thunderbird does not group messages into a thread.
Sure, no problem. I usually use vanilla com
Looks like I was trying to be too clever. :)
I used org-mode to write the bug report. The problem isn't that the formatting
fails in source code blocks. I put it in one so that it would appear verbatim.
If you copy the contents of the block into a normal paragraph, you should be
able to see the
Ihor Radchenko writes:
> This should not happen, AFAIU. Instead of suggesting unintuitive
> workarounds in the manual, we need to fix the original problem.
I looked into this further. Org actually behaves correctly in your
example. Please refer to 16.7 Exporting Code Blocks.
Basically, the defa
Lin Sun writes:
> When I try to export follow org document to html, there is an error message:
> Unable to resolve link: "Test".
>
> The foot script in section "Internal Link" of org-mode manual says:
>
>> When targeting a ‘NAME’ keyword, the ‘CAPTION’ keyword is mandatory in order
>> to get pr
Hi,
When I try to export follow org document to html, there is an error message:
Unable to resolve link: "Test".
The foot script in section "Internal Link" of org-mode manual says:
> When targeting a ‘NAME’ keyword, the ‘CAPTION’ keyword is mandatory in order
> to get proper numbering
Adding
14 matches
Mail list logo
