On 05/12/2023 20:46, Ihor Radchenko wrote:
We definitely need something to fine-tune export properties inline.
However, I am skeptical about using links for this purpose in Org
proper, not individual user configs.
Sometimes links are really links, however some links require some
tuning. Globa
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
Raffael Stocker writes:
> Ihor Radchenko writes:
>
>> May you try the attached patch?
>
> I tried it with a selection of different states (final and not) and it
> worked in every case. Thanks!
Thanks for testing!
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=7
> On Dec 12, 2023, at 20:40, Aaron Madlon-Kay wrote:
>
> Locally redefining as follows results in the expected behavior:
The previous formulation was not very good. Actually it seems that the existing
function is correct except that the list case should be wrapped in (seq …).
(defun org-entitie
> On Dec 12, 2023, at 21:01, Aaron Madlon-Kay wrote:
>
>> On Dec 12, 2023, at 20:40, Aaron Madlon-Kay wrote:
>>
>> Locally redefining as follows results in the expected behavior:
>
> The previous formulation was not very good. Actually it seems that the
> existing
> function is correct except
Kenny Ballou writes:
> * org-capture.el (org-capture-fill-template): fill %K values using link
> value from `org-store-link', which respects `org-id-link-to-use-id'.
> * doc/ORG-NEWS: (Template variable expansion %K) Document new behavior.
>
> Reported-by: Nathaniel W Griswold
> Signed-off-by: K
Aaron Madlon-Kay writes:
> OK this was also wrong, because seq only matches a finite sequence. I couldn’t
> find a way to match an arbitrary-length list with pcase, so here’s my final
> attempt:
>
> ...
> This seems to handle all cases correctly, but again of course I leave the
> details to the d
Max Nikulin writes:
>> I believe that the right way to go here is what we previously discussed
>> as inline special block equivalent. That way, we will not need to create
>> workarounds with special link type.
>
> It is limitation of top-down parser that object of the same time can not
> be nest
> On Dec 12, 2023, at 23:15, Ihor Radchenko wrote:
>
> This particular change should fit within TINYCHANGE, I think. So, you do
> not need a copyright assignment (unless you have already exhausted the
> 15LOC limit on Emacs patches, which I do not see in git logs).
Ah, yes, that should be OK the
Aaron Madlon-Kay writes:
>> This particular change should fit within TINYCHANGE, I think. So, you do
>> not need a copyright assignment (unless you have already exhausted the
>> 15LOC limit on Emacs patches, which I do not see in git logs).
>
> Ah, yes, that should be OK then. Please see attached
Ihor Radchenko writes:
> Patches welcome.
* What is my status as far as submitting patches to documentation
(including docstrings)?
* Is there a write-up on the process of "patching" I can follow?
--
David Masterson
Is it possible to change the face of org blocks that don't start by "src"?
For example:
'(org-src-block-faces '(("ai" variable-pitch)))
I think it should affect to:
#+begin_ai blocks, but it doesn't seem to work for me.
Best regards
Let's say we have a file Basic.bib, like so, with one or two pairs of braces
around words that need special case preservation:
@book{friends,
title = {{LaTeX} and Friends},
author = {van Dongen, M.R.C.},
date = {2012},
location = {Berlin},
publisher = {Springer},
doi = {10.1007/978-3
13 matches
Mail list logo
