Hi again
After some experimentation, I'm a bit puzzled. So, let's check my
understanding:
1. the beamer exporter is a derived exporter and its parent is the latex
exporter
2. I'm over-writing the following option slots in :options-alist my tests:
(:latex-class "BEAMER_CLASS" nil "beamer" t)
Hi again!
Here is attached a new version of the patch for review. NEWS, commit
message and docstrings are placeholders until we get the code right.
The parameters of the menu are now customiseable, we have org-menu-mode,
and I have been using the current version for a couple of days writing my
th
> After debugging, I found that it is because dvisvgm omitts the default
> #000 color value when generating SVG file, and emacs has a unique way of
> displaying the SVG, which caused foreground color to be applied to it.
Just a note: this has been addressed in the upcoming org-latex-preview
rewr
>> Basically, we need a specialized parser that will guess that a given
>> paragraph of text is actually an incomplete or broken latex fragment.
>> You may try writing one. For example, by additionally checking paragraph
>> elements to be latex-like.
>
> Alternatively, why not fix Karthik's stated
On 16/04/2025 02:03, Leo Butler wrote:
On Tue, Apr 15 2025, Max Nikulin wrote:
I have found unicode-math-input.sty that may handle your specific
example in PdfLaTeX. At first glance it is more powerful than utf8x,
but it does not allow e.g. text Greek α. It forces math mode for it.
Thanks for
>> For syntax highlighting in LaTeX environments you can use
>>
>> (setq org-highlight-latex-and-related '(native))
>
> Ok, thanks, that works nicely. Why isn't that the default?
Ihor, I'm curious to know if the fontification of LaTeX export blocks
suffers from the same performance issues as set
1. Let's call the file a part of Emacs (we plan to move tests to Emacs
eventually)
For this I would need some additional support as I don't exactly
understand what you mean here. Do you mean where to put it as in like
"emacs/test/lisp" instead of "org-mode/testing/lisp"?
2. Please prefix t
Thanks, Ihor.It seems to be related to org-super-agenda.I started with
emacs -q and loaded just enough settings to be able to load org-mode and build
my agenda.
I also did not see the non-Org buffer warning. So I started adding packages
back in (well Org-related ones), and I got them al
I get the non-Org buffer warning when I use org-super-agenda and add a group
with :habit t. Adding other groups with properties like :time-grid,
:scheduled, :tag, :deadline all work as expected and without the non-Org buffer
warning. So far just the :habit causes the warning (and I have to hav
On Tue, Apr 15 2025, Ihor Radchenko wrote:
> Leo Butler writes:
>
>> Subject: [PATCH] doc/org-manual.org: update CDLaTeX url
>> ...
>> -[[https://staff.fnwi.uva.nl/c.dominik/Tools/cdlatex/]]. Do not use
>> +[[https://github.com/cdominik/cdlatex][CDLaTeX's Github repository]]. Do
>> not use
>
On Tue, Apr 15 2025, Max Nikulin wrote:
> On 15/04/2025 02:47, Leo Butler wrote:
>> I experience problems typesetting mathematical expressions. I cannot
>> find anything as good as the unicode-math package for lualatex.
>> Consider generating a preview of this fragment using pdflatex versus
>> lu
I understand what you mean. I think that the reason
Pandoc has disallowed putting periods at the end of citekeys
is that it truly does not represent a behavior that any users
engage in, and disallowing it massively simplifies the Markdown
or org syntax of a very common procedure: putting a period
Rob Davenport writes:
> Good to know it works be default,
(unless I screwed up my tests)
> ... so it's not org-mode itself but some interference with something
> else. I'll try narrowing down the problem. I've got a large set of
> packages and my config is split up into numerous files so it m
Leo Butler writes:
> Subject: [PATCH] doc/org-manual.org: update CDLaTeX url
> ...
> -[[https://staff.fnwi.uva.nl/c.dominik/Tools/cdlatex/]]. Do not use
> +[[https://github.com/cdominik/cdlatex][CDLaTeX's Github repository]]. Do
> not use
Better https://elpa.nongnu.org/nongnu/cdlatex.html
--
On Tue, Apr 15 2025, Yu Huang wrote:
> You may give a try to org-cdlatex-mode, provided by cdlatex.el. It
> offers plenty of useful and convenient snippets (functions) for
> inserting latex environment in org-mode.
Thanks for the suggestion, I will give it a try.
Patch to org-manual.org attache
[ Moving discussion to Org mailing list, where it belongs ]
Zac E writes:
>>> [cite:@cohen2003consum-repub.;@trentmann2016empire-things]
>> This is ambiguous. "." can be a part of citation key.
>> There is no bug here. Just a limitation that we cannot easily force end
>> of citation key in Org
Good to know it works be default, so it's not org-mode itself but some
interference with something else. I'll try narrowing down the problem. I've
got a large set of packages and my config is split up into numerous files so it
might take a while.I can try from both directions too. Strip
On Tue, Apr 15 2025, Rudolf Adamkovič wrote:
> Leo Butler writes:
>
>> Alternatively, why not fix Karthik's stated problem with some analogue
>> to `org-insert-structure-template'? E.g. `org-insert-latex-environment'.
>
> This would be a nice addition in general, IMO.
>
>> It would insert a late
Omar Antolín Camarena writes:
> I get warnings that org-refile-targets, org-capture-templates and
> org-capture-templates-contexts do not satisfy their defcustom :type
> specifications, and I believe the reason is that those type
> specifications are incorrect!
>
> 1. For org-refile-targets the d
Rudolf Adamkovič writes:
>> On the other hand, simply allowing to specify @example appears to be
>> safe (I may be wrong), even if we happen to use language name that is
>> not supported by the highlighter.
>
> Yes, this is all we need:
>
> 1. Look up BACKEND in `org-latex-src-block-backend'
>
Ihor Radchenko writes:
> May you please update your latest patch for ob-sql.el, converting it
> into (1) patch to sql.el; (2) patch for ob-sql.el that assumes changes
> to sql.el?
It has been a while since the last message in this thread.
Phil, do you need any help on this?
--
Ihor Radchenko /
Leo Butler writes:
> I see the same thing as Billy, both with an up-to-date Org main branch
> and 9.7.25. Applying his patch fixes the issue.
>
> Note that step 2 fails for me, with the message:
>
> make[1]: emacs-30-vcs: No such file or directory
> make[1]: *** [Makefile:64: org-version.el] Erro
Rudolf Adamkovič writes:
> Leo Butler writes:
>
>> Ok, thanks, that works nicely. Why isn't that the default?
>
> I would like to ask the same question. :)
1. It can significantly degrade performance
2. Not everyone is keen on too much fontification
--
Ihor Radchenko // yantar92,
Org mode mai
Leo Butler writes:
> Ok, thanks, that works nicely. Why isn't that the default?
I would like to ask the same question. :)
Rudy
--
"Chop your own wood and it will warm you twice."
--- Henry Ford; Francis Kinloch, 1819; Henry David Thoreau, 1854
Rudolf Adamkovič [he/him]
http://adamkovic.org
On Mon, Apr 14 2025, Ihor Radchenko wrote:
> Billy Lei writes:
>
>> When using themes with background color set to #00, and
>> org-preview-default-process is set to dvisvgm, the LaTeX fragments are
>> displayed incorrectly.
>>
>> To reduplicate:
>>
>> 1. Switch to a theme with background c
Ihor Radchenko writes:
> I am unable to reproduce.
+1 However, there is a bug I where if the theme is changed while preview
is showing, then the preview has the wrong colors until re-previewed.
Rudy
--
"Simplicity is complexity resolved."
--- Constantin Brâncuși, 1876-1957
Rudolf Adamkovič [
Ihor Radchenko writes:
> ...
Apologies for a late reply. I have been sick. :(
> Also, keep in mind that syntax highlighting is experimental and that the
> texinfo manual explicitly says
>
> Warning: Source highlighting is experimental; feedback is
> welcomed. The syntax of HIGHLIGHT_
Rob Davenport writes:
> FYI - so far, I've narrowed down when I get the "cannot be used in non-Org
> buffer" error in my setup to the use of org-agenda-include-diary.
>
> With this set to t:
>
> (use-package org
>...
>:config
> (setq org-agenda-include-diary t)
>
FYI - so far, I've narrowed down when I get the "cannot be used in non-Org
buffer" error in my setup to the use of org-agenda-include-diary.
With this set to t:
(use-package org
...
:config
(setq org-agenda-include-diary t)
...
I see the error when I bring up my a
Leo Butler writes:
> Alternatively, why not fix Karthik's stated problem with some analogue
> to `org-insert-structure-template'? E.g. `org-insert-latex-environment'.
This would be a nice addition in general, IMO.
> It would insert a latex environment, after prompting for the name, or
> update
On 13/04/2025 23:38, Ihor Radchenko wrote:
Max Nikulin writes:
Notice that code of `gui--selection-value-internal' and
`org-get-x-clipboard' uses different set of targets and `window-system'
variants.
[...]
From quick skimming, it does not look like there is any actual
difference.
Absence of
On 15/04/2025 02:47, Leo Butler wrote:
I experience problems typesetting mathematical expressions. I cannot
find anything as good as the unicode-math package for lualatex.
Consider generating a preview of this fragment using pdflatex versus lualatex:
\[ ∫₀¹ 𝐟(σ) dσ \]
Isn't unicode-heavy form
在 2025/4/15 2:02, Ihor Radchenko 写道:
Billy Lei writes:
When using themes with background color set to #00, and
org-preview-default-process is set to dvisvgm, the LaTeX fragments are
displayed incorrectly.
To reduplicate:
1. Switch to a theme with background color set to #00 (like Mod
On Mon, 14 Apr 2025 at 19:23, Ihor Radchenko wrote:
>
> Looks like we are losing the context.
>
Maybe... too many things at once ;-)
> Let me reiterate. I was questioning your ORG-NEWS entry:
>
> > +When exporting to beamer, =#+BEAMER_CLASS_OPTIONS:= should be
> used
> > +inste
34 matches
Mail list logo
