Ihor Radchenko writes:
>>> It was a slip when the patch was applied.
>>> May you please explain more about {{{results(=value=)}}} problem?
>>> Isn't it sufficient to do src_elisp[:results verbatim]{'value}
>>> {{{results(=value=)}}}?
>>
>> The issue is the opposite I think. Currently the default
Max Nikulin writes:
>>
>>> I consider the following as a kind of graceful degradation
>>>
>>> (defun org-sort-function-fallback-downcase
>>> (a b &optional LOCALE IGNORE-CASE)
>>>(if ignore-case
>>> (string-collate-lessp (downcase a) (downcase b) locale ignore-case)
>>> (strin
Ihor Radchenko writes:
> Morgan Smith writes:
>
>> * lisp/org/org-compat.el: Add definition of 'org-imenu-flatten'.
>> (org-imenu-get-tree): Use 'org-imenu-flatten'.
>> ---
>>
>> Hello!
>>
>> I've been using this patch for a bit and I quite like it. One would think
>> there would be an option i
András Simonyi writes:
> ... Some comments on the proposed changes:
> ...
Thanks for the comments!
See the attached updated version of the patch with all your comments
addressed.
>> At least one =PRINT_BIBLIOGRAPHY= keyword must be present in the
>> document to render citations on export.
>
> T
Ihor Radchenko writes:
>> A new Ispell process started on export.
> ...
> Confirmed.
> This is because `org-html-final-function' uses `mhtml-mode' to indent the
> resulting html file. `mhtml-mode' unconditionally runs `prog-mode-hook'
> thus starting Ispell.
>
> We may try `delay-mode-hooks' ar
JV writes:
> `org-agenda-tree-to-indirect-buffer' does not respect the
> `org-indirect-buffer-display' value of 'current-window unless invoked
> with a prefix arg.
>
> The function does respect all other values for
> `org-indirect-buffer-display'. And it does respect the value
> 'current-window
Bastien Guerry writes:
> Ihor Radchenko writes:
>
>> Bastien, may you check which name is used in the FSF records?
>
> I've taken this offlist.
The name in the FSF records should be correct now.
--
Best,
Amy
Dear All,
since bibtex and biblatex requires title fields to be in title case
but CSL assumes that they are in sentence-case, citeproc-el converts
title fields in bib(la)tex bibliography databases into sentence-case
before processing them except for entries with an explicit non-English
langid valu
Ihor Radchenko writes:
> Amy Grinn writes:
>
>> First of all, I would like to change (defalias) the function name
>> org-babel-noweb-wrap to org-babel-noweb-make-regexp. I think this in
>> more in line with other functions which create regular expressions.
>
> +1
> You may even use obsolete alia
I see there are a lot of test cases for org-find-olp (which is the function
I believe processes the outline path argument).
testing/lisp/test-org.el
2861:(ert-deftest test-org/org-find-olp ()
2862: "Test `org-find-olp' specifications."
2875:(should (org-find-olp '("Headline") t))
2876:(sh
Joris Caravati via "General discussions about Org-mode."
writes:
> I've been archiving tasks automatically using
> `org-after-todo-state-change-hook' but I've been recently bit with a
> note (entering a todo state configured with '@') being placed where the
> task was before its archival.
>
> Thi
On 2024-05-10, 18:09 +0700, Max Nikulin wrote:
> Thank you for the explanation. Reading "lists all" I expected something
> like list of all info manuals in the case of M-x info RET when there are
> no info buffers yet.
I see. I replaced the term "lists all" with "shows all" to avoid this conf
András Simonyi writes:
> since bibtex and biblatex requires title fields to be in title case
> ...
Are you sure? AFAIK, bibtex and biblatex (depending on the bibstyle)
does not care about capitalization and instead applies its own, unless
the title explicitly protects the capitalization/case wit
Nafiz Islam writes:
> I see there are a lot of test cases for org-find-olp (which is the function
> I believe processes the outline path argument).
>
> testing/lisp/test-org.el
> 2861:(ert-deftest test-org/org-find-olp ()
> 2862: "Test `org-find-olp' specifications."
> 2875:(should (org-find
Greetings all,
This patch adds a new option `'mixed' to `org-md-headline-style' that
when enabled allows for exporting the first two headline levels in
Setext-style, and the rest in ATX-style. I like the mixed style for
certain situations, and I couldn't find a way to export in this manner.
I've
Lee Thompson writes:
> This patch adds a new option `'mixed' to `org-md-headline-style' that
> when enabled allows for exporting the first two headline levels in
> Setext-style, and the rest in ATX-style. I like the mixed style for
> certain situations, and I couldn't find a way to export in this
Hi Ihor,
> But isn't (setq org-md-headline-style 'setext) do exactly what you describe?
My apologies, I should have included an example. What I'm trying to
achieve is that instead of this: (set to setext)
> One
> ===
>
>
> Two
> ---
>
> 1. Three
>
> 1. Four
Or even something like this: (atx
17 matches
Mail list logo
