Hi
After giving it a thought, I would say that adding a new custom
variable to control the default options might do the trick.
Something like (in .dir-locals.el format):
#+BEGIN_SRC elisp
(org-latex-fontspec-default-features
. (("Path" . "../fonts/")
("Extension" . ".otf")
;-) Look at the last commits in the feature branch.
I hope they will help to provide a cleaner integration path in the future.
Best, /PA
On Fri, 13 Jun 2025 at 20:49, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > We can further discuss in the next meetup.
>
> As discussed
Hi Ihor,
there you are
On Fri, 13 Jun 2025 at 21:03, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > attached is a ZIP file with the presentation and the anabasis MWE I
> showed
> > yesterday during the meetup.
>
> Thanks!
> Do you also have presentation in .org format? (Th
Ihor Radchenko writes:
> It's just a variable rename. Should be safe for bugfix I think.
Great, thank you. I've pushed to bugfix and merged into main.
Karthik Chikmagalur writes:
> I would like to submit the org-latex-preview patchset for review and
> merging now. I will be losing my FSF copyright assignment soon, so I'm
> hoping to see it merged before then even if there are some minor issues
> remaining to be addressed.
As discussed during
Pedro Andres Aranda Gutierrez writes:
> attached is a ZIP file with the presentation and the anabasis MWE I showed
> yesterday during the meetup.
Thanks!
Do you also have presentation in .org format? (Then, I can directly put
it into the notes; it is rather short)
--
Ihor Radchenko // yantar92
Ihor Radchenko writes:
> Thanks for the patch, but I think it only partially solves the problem.
> You addressed targets, but not radio-targets and named references.
> I think that it will be more appropriate to call `org-html--reference'
> directly rather than trying to repeat its logic. Same fo
Pedro Andres Aranda Gutierrez writes:
> We can further discuss in the next meetup.
As discussed, feel free to do things the easiest way. After things are
working, and after we finalize the general API/user interfaces, we will
come back to ensuring backwards compatibility.
--
Ihor Radchenko //
-- Forwarded message -
From: Pedro Andres Aranda Gutierrez
Date: Fri, 13 Jun 2025 at 19:02
Subject: Re: babel (LaTeX) support in feature/all-tex-fonts branch
To: Jacob S. Gordon
Hi again
answers inline...
On Fri, 13 Jun 2025 at 18:39, Jacob S. Gordon
wrote:
> Hey Pedro,
>
>
Jack Kamm writes:
> Ihor -- normally I would just push this to main, but I think it might be
> worth pushing this to bugfix branch instead, so I wanted to check with
> you first if it's alright for me to do that.
It's just a variable rename. Should be safe for bugfix I think.
--
Ihor Radchenko
martinoidar writes:
> Hi,
> Any reuse of the variable named =f= in python session
> causes an error.
>
> Minimal example:
>
> #+begin_src python :session *PY* :results output
> f = 2
> print(f)
> #+end_src
>
> #+RESULTS:
> : 2
>
> #+begin_src python :session *PY* :results output
> print(f)
> #+en
Hey Pedro,
On 2025-06-13 01:27, Pedro Andres Aranda Gutierrez wrote:
> The idea behind the current structure is that there might be other
> things beyond the mode that go in the feature list, therefore I
> didn't want it to be that specific
Makes sense! I just mentioned it since the trailing ':'
Thanks, I will send a patch for the docs to mention this when I get the
time.
Nikolaos
On Fri, Jun 13, 2025, 2:35 AM Christian Moe wrote:
> Nikolaos Chatzikonstantinou writes:
> > When I set `org-html-table-default-attributes' it will not use those
> > attributes on my tables for HTML5 (it's do
13 matches
Mail list logo
