Pan Xie writes:
> I recently found that the environment variable substitution does not
> apply to inline image paths. Supposing I use a path
> “/home/pxie/$Gallery/” to store all my image files, “$Gallery”
> should be substituted with its corresponding value. The file link DOES
> substitute the e
Stefan Nobis writes:
> One minor nitpick: I would prefer a function like
> ~org-element-property-1~ to be named e.g. ~org-element-property-lazy~
> (or something similar), because the "-1" is just obfuscation to me.
foo-...-1 is actually frequently used in Emacs code for semi-internal
helper func
John Kitchin writes:
> I use flyspell, and it looks like org-mode
> sets flyspell-generic-check-word-predicate to be org-mode-flyspell-verify.
Not directly. Rather we do
(put 'org-mode 'flyspell-mode-predicate 'org-mode-flyspell-verify)
Then, flyspell uses this symbol value as the defa
"Loris Bennett" writes:
> I have a lisp function for syncing my appointments from 'calendar.org'
> to a Nextcloud instance via Caldav. The variable org-caldav-inbox is
> set to 'calendar.org' and org-caldav-files is set to 'nil'.
>
> However, when I run the function, all the files which contain
Fantastic!! Thanks for your help. I can remove my ugly override codes.
BTW, Please keep in mind that the org export codes also need to
substitute the environment variables. My proposal only works for the org
file itself, When exports the org file to html, the image file path will
still include
In ob-C.el, line 339 has the format specifier
(`floatp '("double" "%f"))
to print literal floats. However, that format specifier rounds, which
can result in errors. I think the correct approach is to print the
float without rounding or padding or trying to guess at the desired
accurac
Ihor Radchenko writes:
> Kierin Bell writes:
>
>> 3. I have implemented a check to verify that `org-id-ts-relative-function' is
>> only called in Org mode buffers. But since I am uncertain about all of
>> the possible contexts in which `org-id-new' can be called, I am not
>> completely sure if i
org-lint might need changing too?
On 5/31/23, Pan Xie wrote:
> Fantastic!! Thanks for your help. I can remove my ugly override codes.
>
> BTW, Please keep in mind that the org export codes also need to
> substitute the environment variables. My proposal only works for the org
> file itself, When
I think that depends on whether the linter will verify the existence of
each file path. Strictly speaking, it should, thus the org-lint also
need changing. On the other hand, if the tool just verify the grammar of
the org file itself, then it might be OK without changing. I never use
the linter
