Re: [PATCH v2] doc/org-manual.org: Document `org-latex-src-block-backend'

On 5/30/23 11:27, Ihor Radchenko wrote: Nick Dokos writes: Please try to read and let me know if anything is confusing. To me, it does not seem necessary to include the various descriptions. Just the first three lines of the patch, perhaps with a prompt to consult the doc string of the

adding rules for flyspell

I use flyspell, and it looks like org-mode sets flyspell-generic-check-word-predicate to be org-mode-flyspell-verify. I have a few places I would like to augment this to avoid flyspell overlays in different places. In the past I have done this with around advice, which was ok for one rule, but

Re: org-ref-helm-insert-ref-link and latex src blocks

I think you can't use an org-link in a latex src block. You should probably use \eqref{eq:test:2} (probably typed manually). org-ref is not currently clever enough to do that automatically when you inserting in a latex src block. On Tue, May 30, 2023 at 5:29 AM Uwe Brauer wrote: > Hi > > Please

Re: How to export to the simplest possible HTML?

On 2023-05-30, at 17:32, Max Nikulin wrote: > On 30/05/2023 10:47, Marcin Borkowski wrote: >> since I'm going to >> call my exporting function in a loop over many elements. I tried >> (org-export-with-backend 'html (org-element-at-point (point))) > > There is `org-export-string-as', but

Re: How to export to the simplest possible HTML?

On 2023-05-30, at 08:21, Ihor Radchenko wrote: > Marcin Borkowski writes: > >> ... I tried this: >> >> (org-html-export-as-html nil nil nil t '(org-export-with-toc nil)) > > You need (org-html-export-as-html nil nil nil t '(:with-toc nil)) > See `org-export-options-alist'. Thanks. So

Re: HTML export meta tag

On 30/05/2023 03:37, Timothy wrote: The things is the ox-html exporter currently tries to (mostly) support XHTML, which as I understand requires the self-closing slash. ox-html has (:html-doctype "HTML_DOCTYPE" nil org-html-doctype) option that may be set to e.g. xhtml-11 or html5.

Re: How to export to the simplest possible HTML?

On 30/05/2023 10:47, Marcin Borkowski wrote: since I'm going to call my exporting function in a loop over many elements. I tried (org-export-with-backend 'html (org-element-at-point (point))) There is `org-export-string-as', but likely it is not suitable for you. My guess is that you are

[PATCH v2] doc/org-manual.org: Document `org-latex-src-block-backend'

Nick Dokos writes: >> Please try to read and let me know if anything is confusing. > > To me, it does not seem necessary to include the various descriptions. Just > the first three lines of the patch, perhaps with a prompt to consult > the doc string of the variable which describes these options

Re: [RFC] Refactoring org-element API

Hi Ihor, thank you for all your great work. I did not dive deep into all the details, but the overview you provided sounds sensible. 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

Re: org-ref-helm-insert-ref-link and latex src blocks

Uwe Brauer writes: > #+begin_src latex :results latex replace :exports results :eval t > \begin{equation} > \label{eq:test:2} > > \end{equation} > eqref:eq:test:2 > #+end_src > > > There is some logic to it, however when I use org-edit-special > to deal with the reference reftex-reference does

Re: [RFC] Refactoring org-element API (was: [DISCUSSION] Refactoring fontification system)

Hi, Heads up to org-ml developers as the discussed change is very likely to break org-ml (https://github.com/ndwarshuis/org-ml). See https://list.orgmode.org/874jnudps5.fsf@localhost/T/#u -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at .

[RFC] Refactoring org-element API (was: [DISCUSSION] Refactoring fontification system)

Ihor Radchenko writes: > Ihor Radchenko writes: > >> Instead of fontifying elements individually via regexps, we can leverage >> org-element-map, org-element-parse-buffer, org-element-cache, and >> jit-lock-mode. Each type of Org element/object can be assigned with a >> fontification function

org-ref-helm-insert-ref-link and latex src blocks

Hi Please look at the following lines eqref:eq:test:1 has been inserted with org-ref-helm-insert-ref-link it is correctly exported to latex. \begin{equation} \label{eq:test:1} \int \end{equation} eqref:eq:test:1 However the same reference in a latex src block is not correctly supported

Re: Unable to install from elpa

Max Nikulin writes: >> The first instance of M-x package-install org comes from >> ELPA itself. Considering that ELPA is targeting various Emacs versions, >> it should probably be corrected there first. > > Generally agree, but I am skeptical concerning changes in ELPA since > only minority

Re: How to export to the simplest possible HTML?

Marcin Borkowski writes: > ... I tried this: > > (org-html-export-as-html nil nil nil t '(org-export-with-toc nil)) You need (org-html-export-as-html nil nil nil t '(:with-toc nil)) See `org-export-options-alist'. > but the ToC still appears in the output. Also, I'd prefer to do it > a bit

Re: HTML export meta tag

Scott Randby writes: > Okay, but when I try to validate my page as XHTML, I get numerous errors that > would be inconvenient to fix especially since I'm only interested in > obtaining valid HTML. What I think I'll do is to edit the > org-html--build-meta-entry function in my ox-html.el file