Re: Way to mark contents of an Org special block as verbatim?

Kaushal Modi writes: > Wow, thanks for that complete code. I didn't know about the parse tree > functions. > > I was thinking if below is possible as any user running my exporter > would need to use this feature easily. > > #+begin_katex :verbatim t > E = -J \sum_{i=1}^N s_i s_{i+1} > #+end_katex

Re: Way to mark contents of an Org special block as verbatim?

Hi Kaushal, Kaushal Modi writes: > I would like to treat that block /like/ how Org treats the latex > environment blocks, but it needs to be a special block as > begin_katex/end_katex here is special and it could be a different > equation rendering backend for another user. > > So is that a

Re: A simple Lua filter for Pandoc

Max Nikulin writes: > It seems, lightweight markup is more annoyance than advantage for you. > Tom posted some thoughts on more rigorous syntax in the following message: It's generally the opposite: working in Org is a pleasant journey for me... except when there are dozens of "/" and "*" in a

Re: Tool to compare and choose fonts

Ypo writes: > Was a tool to compare fonts presented in this list some time ago? > > I lost it, I thought I discovered it on Reddit, but now I am thinking > I found it here. > > It was a script that presented on emacs every font in the computer, in > pairs; so the user chose one font each time,

Re: A simple Lua filter for Pandoc

Max Nikulin writes: > Ideally it should be done pandoc and only if it causes incorrect > parsing of org markup. NBSP, probably, should be replaced by some > exporters, I do not think, it is a problem e.g. in HTML files. The reason for this filter is my own comfort. Linguistics texts contains a

Re: A simple Lua filter for Pandoc

Hi Timothy: Timothy writes: > I’m quite interested in this, thanks for sharing. In fact, I’ll probably add > this to . Interesting package. Until now I used a number of homemade functions to convert docx/odt files from Dired, but I think your

A simple Lua filter for Pandoc

Hi, Very often I need to convert docx documents to Org. There are a series of characters that I prefer to be passed to Org as Org entities and not literally, so I have written this little filter in Lua for Pandoc. I share it here in case it could be useful to someone. Of course, the associative

Re: [PATCH] Re: [BUG] Underlined text in parentheses is not exported correctly

Ihor Radchenko writes: > However, thinking about it more, I feel that prioritising underline > should work better. The underline parser recently got changed into a > stricter version. Now, only underlines starting after spaces,-,(,',", > and { are recognised as an underlines. > > So, the attached

Re: [BUG] Underlined text in parentheses is not exported correctly

Ihor Radchenko writes: > I am not sure if it is an actual issue. > > Note that (_u can be interpreted as a subscript. > Org prioritises subscript over underline. > > Looking at the code: > > (?_ (or (and (memq 'subscript restriction) > (org-element-subscript-parser)) > (and (memq

Re: [BUG] Underlined text in parentheses is not exported correctly

Juan Manuel Macías writes: > If I do M-! (occur org-match-substring-regexp) > > I get: > > 10:(_underline_) > 22:(_underline_ text) Well, in my case the temporary workaround was to force super/subscripts with braces: #+begin_src emacs-lisp (defun my-org-element-sub

[BUG] Underlined text in parentheses is not exported correctly

Hi all, I don't know if this is a known issue... Consider the text: (_underline_) When exported to LaTeX we get: (\textsubscript{underline}\_) And to HTML: (underline_) The same result with: (_underline_ text) LaTeX: (\textsubscript{underline}\_ text) But this: (this word is

Re: caption width in LateX export

Sebastian P. Luque writes: > This is great, and very interesting to learn about the BIND keyword. > > Thank you, You're welcome. Of course, if you use the filter very often, it is not necessary to include it in a document or use the bind keyword. It would be enough to add the function to your

Re: caption width in LateX export

Sebastian P. Luque writes: > Thank you, Juan. Unfortunately, there is a price for this solution as > it is now impossible to name and refer to this segment as usual: I see. Have you tried the option with LuaTeX that I put in my other message? You can compile with LuaTeX also using latexmk:

Re: caption width in LateX export

nsectetuer adipiscing elit #+ATTR_LaTeX: :width .3\linewidth [[img]] Best regards, Juan Manuel Juan Manuel Macías writes: > If you use the caption package (https://www.ctan.org/pkg/caption), you > can indicate in each figure the width of the caption. In this case, you > wou

Re: caption width in LateX export

Hi Seb Seb writes: > When exporting to LaTeX, is there a mechanism to make the figure > captions as wide as the figure? In pure LaTeX, this can be easily > accomplished by placing the figure inside a minipage environment. > Using a special block, as in: > > \begin{minipage}{0.7\textwidth} > >

Re: text after sub headings?

Max Nikulin writes: > It is not necessary complex layout. It is a decoration similar to > pictures in fiction books. Unlike figures such additions are not > strictly important to understand material. In printed form it is like > figures however. Insets are appropriate in particular places, but

Re: text after sub headings?

Max Nikulin writes: > Text books and magazines may contain insets (side notes), sometimes > even page-long ones. They present independent material that may be > interesting or useful in particular context or may be just skipped > when a reader is concentrated on main material. Such inset may be

Re: text after sub headings?

Robert Nikander writes: > If you view a "*" item as "book section", it's confusing. But if you > view a "*" item as "collapsible thing", then it makes more sense. I understand your use case. But I think in that context Org headings would still be useful (at least they remind us at what level

Re: text after sub headings?

Hi Robert, Robert Nikander writes: > I see why this is not possible, given the text format of an org file. > But I am curious if people think it would be useful. This is a bit > off-topic maybe, but I’m imagining what I would do if I created > something like org-mode using another underlying

Re: format/fill of text in a cell in tables

Uwe Brauer writes: > I think, one attempt could be to use org-edit-special, to edit a cell, > type the text in a temporary buffer, fill it and then return to the table. > > That seems so obvious that I think there might be technical problems, > because otherwise it would have been implemented

Re: format/fill of text in a cell in tables

to...@tuxteam.de writes: > This reminds me of people advocating "semantic backup" (e.g. use > "emphasis" instead of "italics", until one realises that you just > managed to peel off one layer of the sematic onion. The onion just got > smaller (some literature perhaps might want to play with the

Re: Raw Org AST snippets for "impossible" markup

Juan Manuel Macías writes: > Jumping into the "real world", how about these two examples of nested > emphasis? By the way, what do you think about allowing the use of some kind of aliases, so that the aspect is less verbose? Maybe something like "(i::" instead of &

Re: Raw Org AST snippets for "impossible" markup

Max Nikulin writes: > Looking into your code I have realized that it should be implemented > using filter, not through :export property of links. Maybe without > working proof of concept with link exporters, this session of > monkey-typing would not be successful. Jumping into the "real

Re: Raw Org AST snippets for "impossible" markup

John Kitchin writes: > Have you seen > https://github.com/tj64/org-dp? It seems to do a lot with creating and > manipulating org elements. It might either be handy or lead to some > inspiration. Interesting package. Thanks for sharing. It gave me an idea, also borrowing part of Maxim's code,

Re: Raw Org AST snippets for "impossible" markup

Max Nikulin writes: > As you have guessed, It is not my choice, it is interface of ox.el and > org-element.el. Indeed. Sorry for my haste: it's the consequences of not read the code carefully :-) Of course, your orgia-link-procedure could be extended to more org elements. I can't think of what

Making a dictionary in Org

. Best regards, Juan Manuel -- Juan Manuel Macías https://juanmanuelmacias.com/ dictionary.org Description: Lotus Organizer

Re: Raw Org AST snippets for "impossible" markup

Juan Manuel Macías writes: > I would suggest, however, not to use the term 'italics [...blah blah...]' Sorry for the noise! I think I messed myself up... Naturally, 'italic' (or 'bold') is required: (italic () \"inter\") Best regards, Juan Manuel

Re: Raw Org AST snippets for "impossible" markup

Max Nikulin writes: > John, thank you for the reminding me of Juan Manuel's idea that > everything missed in Org may be polyfilled (ab)using links. > It is enough for proof of concept, special markers may be introduced > later. After some time spent exercising in monkey-typing, > I have got some

Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal

Hi Greg, Greg Minshall writes: > i hope we don't adopt such an "official policy" regarding discussions on > this list. i don't think we've had any problems where non-FSF/GNU > topics have somehow swamped our discussions. Not that I want to put on a censor hat, far from it :-). But this is

Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal

Hi Timohy, Timothy writes: > I don’t think Ihor is suggesting we stop indicating that org-mode is part of > Emacs. Of course, I am convinced that Ihor is not saying that Org is not part of Emacs, and I have to make it clear, that I have never suggested such a thing. What's more, I understand

Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal

Russell Adams writes: > What makes Org dramatically different is the editing experience in > Emacs. Collapsing the outline, filtering on metadata, exports, agenda, > etc. Those are Emacs features, not specific to the actual markup > format. > > My impression is we already have stretched our

Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal

Ihor Radchenko writes: > Ok. Let me explain my thought process. > > First of all, there is no burden on users of Org mode in making edits to > orgmode.org. It is a burden on Org contributors. > > One of the aims of my proposal is reducing this burden by involving > non-emacs users to provide

Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal

Ihor Radchenko writes: > I view "Org Mode" as a "brand name". Something uniquely identifying Org > mode and serving as a search term. Yes, it makes sense. > Is it your principal position about the title specifically? Do you think > that just referring to Emacs in the website description is not

Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal

Ihor Radchenko writes: > The website title is "Org mode for Emacs", repelling users who _do >not want_ to use Org inside Emacs. Maybe we can do better? Something >with less accent on Emacs like "Org mode: your life in plain text" I am not at all in favor of separating the 'Org Mode' name

Re: Org-syntax: Intra-word markup

Hi John, John Kitchin writes: > Along these lines (and combining the s-exp suggestion from Max) , you > can achieve something like this with links. I like this idea of merging the Maxim's proposal with the power of links. In any case, this and other workarounds provided here make it clear

Re: Org-syntax: emphasis and not English punctuation

Max Nikulin writes: > Maybe this issue should be considered independently of itra-word emphasis. Yes I agree. Apologies for mixing up this topic in the discussion about intra-word emphasis... > Second and third examples looks like they should be supported. Ihor > mentioned treating punctuation

Re: On zero width spaces and Org syntax

Tom Gillespie writes: > I don't mean to be dismissive of the suggestion, but a lot of > time is spent on this list walking back ideas that have not > had sufficient time put into understanding what the > unintended consequences would be, so I wouldn't say > that it is irresponsible, I would say

Re: On zero width spaces and Org syntax

Tim Cross writes: > I think I am in agreement regarding most of your points about the use of > the zero-width character. I see it as a type of escape hatch which > provides a solution in some less frequent situations. It is a somewhat > clever kludge to enable markup in some situations not

Re: On zero width spaces and Org syntax

Hi Greg, thank you for your comment, Greg Minshall writes: > in fact, i am always queasy when i enter ZWNBSP in a .org (or any other) > file. some sort of "visible" sequence would be great. backwards > compatibility might be a problem. Yes I agree. I think that in this case, a new mark would

Re: Org-syntax: Intra-word markup

Hi Maxim, Max Nikulin writes: > More explicit markup leaves less room for ambiguities, and I like the > idea due to this reason. On the other hand it diverges from principle > of lightweight markup. The almost only special character in TeX is > "\", HTML has three ones "&<>" with simple escape

On zero width spaces and Org syntax

Hi all, It is usually recommended, as you know, to insert a zero width space character (Unicode U+200B) as a sort of delimiter mark to solve the scenarios of emphasis within a word (for example, =/meta/literature=) and others contexts where emphasis marks are not recognized (for example

Re: Org-syntax: Intra-word markup

Nicolas Goaziou writes: > I'm suggesting to remove zero-width spaces contiguous to emphasis > markers only. Therefore LaTeX process would npot see them. Other zero > width spaces, e.g., inserted by user, are kept. AFAICT, the two last > points you mention are not relevant with my proposal. > >

Re: Org-syntax: Intra-word markup

Hi Nicolas and all, Nicolas Goaziou writes: > I find zero-with spaces solution much more elegant. It also doesn't > change current syntax, which is a big advantage. I agree that zero width spaces work fine as a solution, but I think they should not be understood as part of the syntax but as a

Re: Org-syntax: Intra-word markup

Tom Gillespie writes: > I don't mean to be a wet blanket, but the edge cases for > the current markup syntax are already hard enough to > implement correctly, to the point where different parts of > Org mode are inconsistent. Intra-word markup isn't viable > because there simply isn't any sane

Re: Org-syntax: Intra-word markup

Ihor Radchenko writes: > Denis Maier writes: > >>> Can you create an example of such scenario and post it as a bug? >>> Probably, we just need to strip all zero-width spaces at the basic ox.el >>> level. >> To be clear: That's not an org bug. It's just that latex won't be able >> such a word.

Re: Org-syntax: Intra-word markup

Hi Denis and Ihor, Ihor Radchenko writes: > Denis Maier writes: > >> Currently, org syntax doesn't officially seem to support intra-word >> emphasis. Am I missing something? > > intra-*word* works just fine for me. > > Best, > Ihor I think what Denis is referring to is a construction of the

Re: how to export red colored TeX to latex

Hi Eric, Eric S Fraga writes: > Very nice Juan! I would find this use of links quite useful. Thank you. Yes, org-link-set-parameters is quite productive, and addictive in occasions! :-): I also have link types defined for somewhat extravagant things, such as linking videos and music from the

Re: Orgdown: negative feedback & attempt of a root-cause analysis

Tom Gillespie writes: > Karl, >The exact naming of a thing is nearly always the most contentious > step in trying to promulgate it. In my own field we can easily get all > parties to agree on a definition, but they refuse to budge on a name. > As others have said, I wouldn't worry about

Re: how to export red colored TeX to latex

Uwe Brauer writes: > Thanks, right now, I don't need links but it is good to know that there is a > way to use them. It's just a way of using links to produce different strings, depending on the export format (LaTeX, HTML...). I use them quite a bit for text segments as \foreignlanguage{}{},

Re: how to export red colored TeX to latex

Hi, Uwe Brauer writes: > Hi > > I want to obtain a latex file that contains > > \textcolor{red}{$\delta \phi = \frac{2 m}{R}$} > > > However when I add > \textcolor{red}{$\delta \phi = \frac{2 m}{R}$} > > To an org file and export it as Latex, the construct ends up like this > > >

Re: "Orgdown", the new name for the syntax of Org-mode

Marcin Borkowski writes: > Quite the contrary. The amount of confusion between TeX (engine)/TeX > (language)/TeX (distro)/TeX-aware text editor/LaTeX (whatever) among > novice/casual users has always been terrible. It's natural when those novice/casual users approach something that is new to

Re: "Orgdown", the new name for the syntax of Org-mode

Joost Kremers writes: > Why not just use the term "Org markup"? It's descriptive and should be > understandable to people familiar with the concept of markup languages. This. 'Org markup language' and 'Org Syntax' are obvious and natural terms that can easily be inferred from the Org manual.

Re: "Orgdown", the new name for the syntax of Org-mode

Hi, I believe (IMHO) that it does not make much sense to separately name the Org Mode syntax (as a markup language). That would only generate confusion among users. Furthermore, 'Org Mode', as a whole, is already a sufficiently recognized and popular name, even outside the GNU Emacs community. A

Dired images in an Org buffer

Hi, I don't like image-dired thumbnails, so I wrote this function to preview all images in a directory in an Org buffer. I share it here, in case it is useful to someone: #+begin_src emacs-lisp (defun my-org-img-dired-preview () (interactive) (if (not (derived-mode-p 'dired-mode))

org-critical-edition (new version)

-- -- -- Juan Manuel Macías https://juanmanuelmacias.com/

Re: insert automatically a reference to a section header and a link

Stefan Nobis writes: > #+begin_src emacs-lisp > (defun sn/ox-latex-filter-special-ref-vref (text backend info) > (when (org-export-derived-backend-p backend 'latex) > (replace-regexp-in-string "ref{" "vref{" text))) > > (add-to-list 'org-export-filter-link-functions >

Re: insert automatically a reference to a section header and a link

Stefan Nobis writes: > Hmmm... for me, the default way to link to headings is just fine, I > seldom need more control over the generated labels: > > #+begin_src org > ,* Intro > > Lorem ipsum dolor sit amet... > > ,* Another section > > As seen in [[*Intro]] there is not much to say. >

Re: Should be possible to export list items emphasized by default?

Ypo writes: > /1. Introduction/ > > It doesn't work as a list item > > 1. /Introduction/ > > It works as a list item but, when exporting, it doesn't export the > whole item emphasized. If I have understood correctly, you want to export the label emphasized as well, not just the item content...

Re: whitespace in org source files

Hi, excalamus--- via "General discussions about Org-mode." writes: > I've not used the email contribution style before and have had > whitespace issues in the past with GitHub PRs.  I typically run > whitespace-cleanup with the before-save-hook which changes tabs to > spaces. I agree with Tim

A function to include a PDF with LaTeX commands for specific pages

Hi, Sometimes I need to include a pre-compiled PDF in my main document. Of course, this can be done simply with the `pdfpages' LaTeX package. If we want to insert a complete PDF, it would be enough to add: #+latex:

Re: [patch] ox-latex.el: add `:options' LaTeX attribute to tables

Hi Nicolas, Nicolas Goaziou writes: > Good idea. Thanks. Attached here the updated patch. Best regards, Juan Manuel >From fc9062caf43956ac68b72f16afbd5584ec84e687 Mon Sep 17 00:00:00 2001 From: Juan Manuel Macias Date: Thu, 4 Nov 2021 21:38:26 +0100 Subject: [PATCH] ox-latex.el: add

Re: [patch] ox-latex.el: add `:options' LaTeX attribute to tables

Hi Nicolas, Nicolas Goaziou writes: > Thank you. > > Could you also document it in the manual? Of course, tomorrow I will upload an updated version of the patch with the documentation in the manual. Should I also add an entry in ORG-NEWS, in "Version 9.6" node? Best regards, Juan Manuel

Re: Sub-figures in Org Mode

Hi Jason, sorry for the late reply. Jason Ross writes: > I'm looking at declaring a "figure" block the way you are, but > `org-element-map'ing over the links inside the block and processing them > with the "normal" link-handling machinery. That way, image options work > the same way in a

Re: Introducing Org-transclusion

Hi Noboru, Noboru Ota writes: > I would like to introduce an add-on package I have been developing for > about one year and ask for discussion / advice. > > The package is named "Org-transclusion", and is available on GitHub at > https://github.com/nobiot/org-transclusion. Simply put, it lets

Re: [patch] ox-latex.el: add `:options' LaTeX attribute to tables

Juan Manuel Macías writes: > \begin{longtblr}[options 1 options 2 options 3 options 4]{align} PS: I think the options should be separated by commas. In this case, it's necessary to replace the line: (mapconcat (lambda (x) (mapconcat 'identity x "")) options-list "

Re: [patch] ox-latex.el: add `:options' LaTeX attribute to tables

Vikas Rawal writes: > This still seems to exporting the second "options" value only. Do you still keep this line in your init: (advice-add 'org-latex--org-table :override #'my/org-latex--org-table) ? If so, rename the function from my previous email as `my/org-latex-org-table' and re-evaluate

Re: [patch] ox-latex.el: add `:options' LaTeX attribute to tables

Hi Vikas, Vikas Rawal writes: > This is excellent. There is only one improvement that I would like you to > consider. Is it possible to allow multiple ":options " lines that are > appended when exported to > +latex? Something like this: > > #+ATTR_LATEX: :environment longtblr > #+ATTR_LATEX:

[patch] ox-latex.el: add `:options' LaTeX attribute to tables

Hi, The `:options' attr. allows adding an optional argument with various table options (between brackets in LaTeX export), since certain tabular environments, such as `longtblr' of the `tabularray' LaTeX package, provides this structure (see:

Re: Support for tabularray in LaTeX export

Vikas Rawal writes: >> >> Hi Vikas, >> >> You can define a modified version of `org-latex--org-table', >> adding a new LaTeX attribute `:options'. Something like this: > > Is there a case for incorporating this in orgmode itself? There is some > general utility for this in my view.

Re: A quick LaTeX reference guide in Org

Eric S Fraga writes: > It's in CTAN, the official (?) LaTeX repository. I just saw it now there. CTAN is an infinite bazaar :-) By the way, in CTAN there is also the /TeX for the Impatient/ book (I love that title), which is a very good manual for programming at low level in TeX/plainTeX:

Re: A quick LaTeX reference guide in Org

Tim Cross writes: > There is also a latex2e.info package 'out there'. I have it installed > from my Linux distro and find being able to run (info)Latex very useful > as a basic reference. Thank you very much for this information, I did not know it. I just saw that there is a

A quick LaTeX reference guide in Org

Hi, The TeXstudio editor includes a comprehensive LaTeX reference guide in HTML (https://github.com/texstudio-org/texstudio/blob/master/utilities/latexhelp.html). I have converted it to Org with Pandoc (and then cleaned it up and fixed some broken links). It can be downloaded here:

Re: Sub-figures in Org Mode

Hi Jason, Jason Ross writes: > Are there any workarounds people use to create subfigures in Org Mode > when exporting to LaTeX? Example output: In this thread I explain a procedure to export images as subfigures using org links: https://list.orgmode.org/87mty1an66@posteo.net/ Best

[tip] Export some footnotes as pdf annotations (LaTeX) or comments (odt)

xt)) (replace-regexp-in-string ".+" "" text #+end_src Best regards, Juan Manuel -- -- -- Juan Manuel Macías -- https://juanmanuelmacias.com/

Fancy underlines in Org to LaTeX

in the soulpos documentation. See this screenshot: https://i.imgur.com/UK6W8sl.png Best regards, Juan Manuel -- -- -- Juan Manuel Macías https://juanmanuelmacias.com/ soulpos-test.org Description: Lotus Organizer

Re: Unable to configure emacs 27.2 to use org 9.5

oked in your elpa directory if you see this path: .../elpa/org-9.5/? Have you tried uninstalling Org and reinstalling it? Best regards, Juan Manuel -- -- ------ Juan Manuel Macías https://juanmanuelmacias.com/

[minor tip] "TeXify" strings "TeX" and "LaTeX" when exporting to HTML

Hi all, I wrote this simple filter for my blogs, which formats "TeX" and "LaTeX" strings in the TeX 'typographic' style (or something similar). First, these variables: #+begin_src emacs-lisp (setq my/tex-html-string "TEX") (setq my/latex-html-string "LATEX") #+end_src Of course, the

Re: how to export to odt with 11 or 10 pt fonts? Default font setting

copropriete27ruemo...@gmail.com writes: > Unless you insist on using Computer Modern with a word processing > programm (yes, it can be done, at least with the OTF versions of these > fonts), or Times New Roman/Cambria with LaTeX (again possible thanks to > their OTF incarnation) and slaving to

[tip] Go to the org node from the attached directory

Hi, I often come across the following use case: helm-locate leads me to a file named (for example) document.pdf, which is in an attached folder of an Org node. I open the document and then I would like to jump from there to the Org node. I don't know if anyone has found any solutions for this or

Re: how to export to odt with 11 or 10 pt fonts? Default font setting

Uwe Brauer writes: > Thanks, but it seems 11TeXpt-->10.95 > > So it is not that different. In typography it's a significant difference. It's not dramatic, but it can produce different results in a book using the same body text and the same line spacing, same margins, page dims. etc. Also TeX

Re: how to export to odt with 11 or 10 pt fonts? Default font setting

Uwe Brauer writes: > I searched about google, but it seems that the only way to have a 10 or > 11 pt font size is, again, by using styles. Am I right? Yes, you are right. Word processors handle paragraph and character styles. Anything that is not styled is applied by direct formatting, manually,

[patch] ox-html.el: add html attribute (verse numbers) to verse blocks

Hi all, I believe that an html attribute to display marginal verse numbers in sequence could be useful for certain content, as philological texts (like here: https://en.wikisource.org/wiki/The_Iliad_and_Odyssey_of_Homer_(Cowper)/Volume_2/The_Odyssey/Book_I) The `lines' property must be a digit

[PATCH] org-manual.org: List the languages supported by smart quotes feature

Hi, I think a footnote with a list of (currently) supported languages could be helpful for users who want to apply this feature. Best regards, Juan Manuel >From 26f799a5a53b35f7f3e6e3df10689855832dbebd Mon Sep 17 00:00:00 2001 From: Juan Manuel Macias Date: Sun, 3 Oct 2021 19:11:48 +0200

[PATCH] ox-latex.el: Unify in one single list Babel and Polyglossia languages alists

Hi all, I'm attaching a patch with a proposal to unify in a single constant (named `org-latex-language-alist') `org-latex-polyglossia-language-alist' and `org-latex-babel-language-alist', along with some necessary (minor) modifications in `org-latex-guess-polyglossia-language' and

Re: [Question] A single *-language-alist in ox-latex.el?

uot; "classic") And then it would be necessary to make some minor modifications in org-latex-guess-polyglossia-language and org-latex-guess-babel-language. I will try to write a patch (or at least a proof of concept) in the next days ... Best regards, Juan Manuel -- -- -- Juan Manuel Macías https://juanmanuelmacias.com/

[Question] A single *-language-alist in ox-latex.el?

sense to mantain in ox-latex.el two separate lists today. Maybe, for simplicity, it would be better to unify the two lists in a single db, something like `org-latex-language-alist'. What do you think? Best regards, Juan Manuel -- -- -- Juan Manuel

Re: export dispatch → change the default "Contents" string

Hi, jean-Christophe, Jean-Christophe Helary writes: > What is the parameter to change the default "Contents" ToC string when > exporting to PDF ? If I'm not wrong, I think there is no native Org way to change the default string for LaTeX literals. But if you use babel (the LaTeX package), you

Re: how to export checkboxes to odt?

Hi Uwe, Uwe Brauer writes: > Any idea how to export checkboxes to odt? > > I mean not just simply having [ ] in the odt document but having them > translated as actual boxes. You can try: (defun my/org-odt--checkbox (item) "Return check-box string associated to ITEM." (let ((checkbox

Re: Possible bug? Combine emphasis marker faces?

Hi Protesilaos, Protesilaos Stavrou writes: > Is there a way to get composite styles? Such as bold and italic or > verbatim and underline, etc.? A somewhat dirty solution (without patching the code) could be evaluating highlight-regexp, for example as a local variable: #+begin_src emacs-lisp

Re: LaTeX export: grffile is a stub package

Hi, meedst...@teknik.io writes: > According to https://ctan.org/pkg/grffile, since 2019-11-08, grffile > is a stub that just loads graphicx, part of texlive-latex-graphics, > part of texlive-base. My system (Guix) doesn't have a package for > grffile, so I can't generate a PDF, which is silly

Re: [BUG] Conflict between org-emphasis and org-latex

Hi Léo and Timothy, Léo Ackermann writes: > [...] > I think that this bug has been introduced recently (I > never noticed it before) I don't know if I'm pointing in the right direction, or I am missing something, but I would say that this is a problem (or consequence) of

Re: [BUG] Conflict between org-emphasis and org-latex

Hi Léo, Léo Ackermann writes: > Hi! > I noticed that in org@888aaa97c0ce331097787333d0d712dd6e4d078f, the > following happens: > When writing `Consider $a^{*}$ and $b^{*}$` in an org-mode buffer, the > two stars match together, causing "and" to appear in bold case. > > Any idea to fix this

Re: [PATCH] org.el: prevent partial fontification when a link is full displayed (was org-link-set-parameters: when :display full, etc.)

Hi Bastien, thank you for your message, Bastien writes: > I could not apply the patch in the bugfix or main branch. Is it still > relevant? If the bug is still here, feel free to send an updated patch. I have consulted the log, and the patch was already applied by Nicololas in commit:

Re: [PATCH] ox.el: add smart quotes for Greek

Hi again, I am attaching a new version of the patch, with some typos fixed and a explanatory note in the commit message on the choice of the character U+201C as Greek second-level opening quotes. In case anyone is interested in what Yanis Haralambous answered me in a recent mail, I reproduce

Re: [PATCH] Fix some typos

regards, Juan Manuel Loris Bennett writes: > Max Nikulin writes: > >> On 23/09/2021 03:18, Juan Manuel Macías wrote: >>> Max Nikulin writes: >>> >>>> However there is namely "memory" in the "1609 Quarto", see e.g. >>>&

Re: [PATCH] ox.el: add smart quotes for Greek

Hi Maxim, Max Nikulin writes: > Juan Manuel, I feel some misunderstanding. I am not asking for more > arguments in support of current variant of patch. CLDR entry, EU > recommendations, the mail from Protesilaos, absence of named HTML > entity, complications with pdfTeX are more than enough. I

Re: [PATCH] Fix some typos

Hi all: Max Nikulin writes: > Please, forgive my ignorance of Shakespeare's poetry. > > On 17/09/2021 17:05, Marco Wahl wrote: >>> On 17/09/2021 04:40, Stefan Kangas wrote: >> Please find attached another clean-up patch that fixes a small number of typos. > > Thou shall not change

Re: [PATCH] ox.el: add smart quotes for Greek

Max Nikulin writes: > I believe, the patch is an improvement. It would be nice to have a > comment clarifying the choice of secondary opening quote mark, but it > is not required. It seems there is no recommendations or established > practice for documenting of such decisions. I have not tested

Re: [ANN] org-ql 0.6 released

Hi Adam, Thank you very much for this great package. I could no longer live without org-ql/helm-org-ql :-) Best regards, Juan Manuel Adam Porter writes: > Hi friends, > > FYI, I just released version 0.6 of org-ql. Please see the changelog > here: > > https://github.com/alphapapa/org-ql#06

Re: [PATCH] ox.el: add smart quotes for Greek

Hi Maxim, Max Nikulin writes: > [...] > Possible options: > - Add the note directly to the .el file. I am afraid, as inline > comment it could be considered too long. > - To a file in the "doc" directory dedicated to such decisions (there > is no such file yet however) with a reference from

<    1   2   3   4   5   6   7   8   9   >