[O] org compact guide texinfo bug ?

y should be coded as @item. Jean-Christophe Helary

Re: [O] org compact guide texinfo bug ?

> 2016/04/09 5:53、Nicolas Goaziou のメール： > >> @itemx @key{TAB} >> >> and >> >> @itemx @key{RET} >> >> are not subsequent entries of @item mouse-3 but entries on their own. >> >> They should be coded as @item. > > Fixed. Thank you. Thank you very much ! Jean-Christophe Helary

[O] different key binding between GUI emacs and emacs -nw

I've just filed a bug report on emacs and was advised to report it here too. It's bug#27140. Basically, when I start GUI emacs (macOS, but also Aquamacs, also reported in Xubuntu and GTK+/Linux), I don't get the default org-mode bindings. Only emacs -nw gets them. Even if I start both with -Q,

Re: [O] different key binding between GUI emacs and emacs -nw

> On May 30, 2017, at 15:51, Nicolas Goaziou wrote: > >> http://lists.gnu.org/archive/html/help-gnu-emacs/2017-05/msg00306.html >> >> Let me know if you need extra information. > > What happens if you replace, e.g., > > (org-defkey org-mode-map [(meta left)] 'org-metaleft) > > with > > (

[O] [org] different key binding between GUI emacs and emacs -nw

cept that I don't *have* most bindings in GUI. There is probably a rational reason what that is happening. I'm fine with helping with the investigation but I fear that's an area where I can't do much more than that. Jean-Christophe > > On Tue, May 30, 2017 at 3:3

Re: [O] [org] different key binding between GUI emacs and emacs -nw

> On May 31, 2017, at 7:28, Tim Cross wrote: > > Just add my confirmation that I have no issues with GUI bindings on either > MacOS Sierra with emacs 25.2 and org 9.0.7 or under Linux with Ubuntu 17.04 > (same emacs and org versions). There were *some* people on help-emacs that could reprodu

Re: [O] [org] different key binding between GUI emacs and emacs -nw

> On May 31, 2017, at 11:38, Tim Cross wrote: > > It is certainly a weird issue. I couldn't agree more :) > If there was a problem at the OS, window manager or interface library (i.e. > gtk) level, it should affect all bindings. That's correct. Basically, what happens in that in GUI mode,

Re: [O] [org] different key binding between GUI emacs and emacs -nw

Apologies, > On May 31, 2017, at 12:51, Jean-Christophe Helary > wrote: > This morning I have installed emacs from macport (emacs-app-devel) and I've > also built it from the repository (./configure with-ns). > > In the locally build version Esc-Left promotes a hea

Re: [O] emacs vs emacs -nw

> On May 31, 2017, at 18:41, Yuri Khan wrote: > > On Wed, May 31, 2017 at 3:58 PM, Jean-Christophe Helary > wrote: > >>> Could you provide an example and/or a recipe to demonstrate the issue? >> >> • Open an org file with a few headers and different head

Re: [O] [org] different key binding between GUI emacs and emacs -nw

> On May 31, 2017, at 19:01, Eric S Fraga wrote: > > On Wednesday, 31 May 2017 at 02:38, Tim Cross wrote: >> I'm sure this has been checked, but make sure it isn't the window >> manager/OS 'stealing' the keys. When I install emacs on any system, > > My own experience over the years is that this

Re: [O] emacs vs emacs -nw

> On May 31, 2017, at 19:04, Jean-Christophe Helary > wrote: >> On X11/GNU/Linux, I get header promotion with Alt+Left but word >> navigation on Esc Left. > > Now that I think about it, I just tried this: > > (setq ns-right-command-modifier 'meta) > &g

Re: [O] emacs vs emacs -nw

> On May 31, 2017, at 20:30, Eli Zaretskii wrote: > >> From: Jean-Christophe Helary >> Date: Wed, 31 May 2017 19:41:00 +0900 >> Cc: Org-mode >> >> Ok, I just tried something else: >> >> (setq ns-function-modifier 'meta) and what I g

[O] keybindings again...

I'm using emacs built from master, emacs -nw, after moving .emacs.el and .emacs.d away, on OSX 10.12. I'm trying to assign M-S-RET to org-insert-todo-heading because for some reason it is not assigned by default: every time I hit ESC S-RET I get ESC RET only. So, I tried things from http://erg

Re: [O] keybindings again...

> On Jun 30, 2017, at 11:51, Kaushal Modi wrote: > > On Thu, Jun 29, 2017 at 10:43 PM Jean-Christophe Helary > mailto:jean.christophe.hel...@gmail.com>> > wrote: > I'm using emacs built from master, emacs -nw, after moving .emacs.el and > .emacs.d away, on

Re: [O] keybindings again...

> On Jun 30, 2017, at 14:27, Nicolas Goaziou wrote: >> It would be nice if the org manual mentioned that too, and give >> alternative keybindings for use in the terminal because that's >> extremely confusing. > > It does: (info "(org) TTY keys"). Thank you for the pointer. Although I don't thi

Re: [O] keybindings again...

:17, Eli Zaretskii wrote: > >> From: Jean-Christophe Helary >> Do you mean that Shift is not recognized as a modified key by the terminal ? > > No, that's not it.

Re: [O] keybindings again...

> On Jun 30, 2017, at 14:27, Nicolas Goaziou wrote: > >> It would be nice if the org manual mentioned that too, and give >> alternative keybindings for use in the terminal because that's >> extremely confusing. > > It does: (info "(org) TTY keys"). The alternative to M-S-RET is C-c C-x M = C-c

Re: [O] keybindings again...

> On Jun 30, 2017, at 17:14, Nicolas Goaziou wrote: >> So, I have a few suggestions to improve that part of the documentation: >> 1) add a list of preset keys in the manual >> 2) add a line about speed keys in the compact guide >> >> That's something I could do if the idea is accepted. > > Sur

[O] capture templates and ^{prompt}

I'm looking for a way to use the string acquired by prompt in a second location in the template, like: * TODO %^{prompt} [/] :sometag:\n** TODO (value of ^{prompt} comes here) :someothertag:\n What's the best way to get that "value of ^{prompt}" ? Jean-Christophe

Re: [O] capture templates and ^{prompt}

Ooops, yes, that was totally under my nose :) Thank you very much. Jean-Christophe > On Jun 30, 2017, at 18:18, numbch...@gmail.com wrote: > > Check out the docstring of variable `org-capture-templates`. > There is a doc like this: > ``` > %\1 ... %\N Insert the text entered at the nth %^{promp

Re: [O] capture templates and ^{prompt}

> On Jun 30, 2017, at 18:21, Jean-Christophe Helary > wrote: > > Ooops, yes, that was totally under my nose :) > Thank you very much. > > Jean-Christophe > >> On Jun 30, 2017, at 18:18, numbch...@gmail.com wrote: >> >> Check

Re: [O] capture templates and ^{prompt}

> On Jun 30, 2017, at 18:47, Nicolas Goaziou wrote: > > Jean-Christophe Helary writes: > >> * TODO %^{prompt} [/]\n** TODO %\1 %^{prompt} %^t\n >> >> gives >> >> * TODO stuff [/] >>

[O] capture template and writeroom mode ?

What would be the best way to have writeroom mode called in one given capture template and not the others ? Jean-Christophe

Re: [O] capture template and writeroom mode ?

Thank you Bsstien. > On Jul 3, 2017, at 12:46, Bastien wrote: > >> What would be the best way to have writeroom mode called in one >> given capture template and not the others ? > > I would you a (file+)function to get the location: > >`(file+function "path/to/file" function-finding-locati

Re: [O] capture templates and ^{prompt}

Sorry to send this question again: > Are there cases where %\1 ... %\N would be used *outside* of a string in a > template? Jean-Christophe > On Jun 30, 2017, at 20:04, Jean-Christophe Helary > wrote: > >> >> On Jun 30, 2017, at 18:47, Nicolas Goaziou wr

[O] message:// links

I'm pasting a message:// link into an org-mode file but it fails to be recognized as a link that should open in a mail client. What is a simple way to have org-mode recognize such links ? Jean-Christophe Helary --- http://mac4translators.blogspo

Re: [O] message:// links

Thank you Nicolas. Jean-Christophe > On Nov 10, 2018, at 16:28, Nicolas Goaziou wrote: > > Hello, > > Jean-Christophe Helary writes: > >> I'm pasting a message:// link into an org-mode file but it fails to be >> recognized as a link that should open

[O] Changing the face of the capture template ?

Sorry for asking such a beginner question. I'm using a non monospace font for my daily work and I'd like to have the capture template buffer be in monospace. How do I do that ? Jean-Christophe Helary --- http://mac4translators.bl

[O] org-megaup

When I use org-megaup I get a "Invalid function: org-preserve-local-variables" is there a way to fix that ? Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

Re: [O] org-megaup

> On Aug 31, 2019, at 4:42, Nick Dokos wrote: > > Jean-Christophe Helary writes: > >> When I use org-megaup I get a "Invalid function: >> org-preserve-local-variables" is there a way to fix that ? >> > > org-megaup is not defined AFAICT - d

Re: [O] org-megaup

Thank you Nick for the help. It looks like I some kind of interference between the built-in org-mode and the most recent package available in melpa. Everything is fixed now. > On Aug 31, 2019, at 4:42, Nick Dokos wrote: > > Jean-Christophe Helary writes: > >> When I use

[O] Capture template issue ?

fer-display 'current-window org-modules '(org-bbdb org-bibtex org-docview org-habit org-info org-irc org-mhe org-protocol org-rmail) org-support-shift-select t org-todo-keyword-faces '(("IN-PROGRESS" . "orange") ("WAIT" . "magenta") ("CANCELED" . "darkgreen") ("TODO" . "pink") ("DONE" . "green"))) Where should I investigate to fix this ? Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

Re: [O] Capture template issue ?

lly I don't have it when it is visible when I do. Currently, the place where that happens most (?) is when I add captured text in a "file+datetree" structure right over a "file+headline" structure. Jean-Christophe Helary > On Sep 17, 2019, at 8:48, Jean-Christophe

[O] sync a single subtree to a different file

I'm looking for a way to sync a given subtree to a different file, semi-automatically (it at the launch of a command). Is there something like that in org-mode ? Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

org 9.2.6 and org 9.1.9

st way to solve that ? Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

Re: org 9.2.6 and org 9.1.9

Nick, thank you for your reply. > On Nov 27, 2019, at 4:15, Nick Dokos wrote: > > Jean-Christophe Helary writes: > >> org 9.1.9 is a built-in >> >> but org 9.2.6 comes as a dependency to some packages and having both >> installed creates conflicts. &g

Re: org 9.2.6 and org 9.1.9

ge maintainers specifying the latest org > version rather than the version built into Emacs when the bundled version > would be sufficient. > > It took me a while to structure my init.el file such that no org > functionality was loaded until I used something which depends on it. Howeve

Re: org 9.2.6 and org 9.1.9

Thank you Stefan. I'll try to reproduce the issue and then I'll report. Jean-Christophe > On Nov 27, 2019, at 12:24, Stefan Monnier wrote: > >> What should happen is that >> 1) packages.el should see that I'm trying to install a package that requires >> 9.2.6 as a dependency and it should notif

using #+ to define faces

I would like to define faces on a file basis by using #+ but I'm not finding relevant info in the manual. Is it possible ? Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

Re: using #+ to define faces

> On Dec 31, 2019, at 18:57, Nicolas Goaziou wrote: > > Hello, > > Jean-Christophe Helary > writes: > >> I would like to define faces on a file basis by using #+ but I'm not >> finding relevant info in the manual. >> >> Is it possible ?

Re: Format of Effort estimates should be mentioned in its Info node

ow Timestamps are. This does look like a potential contribution to the package. Jean-Christophe Helary > > 2020年1月4日 11:55 差出し人： k...@kyleam.com: > >> Kisaragi Hiu writes: >> >>> Currently, the Info node about effort estimates does not mention what >>> format

Re: Step by step tutorial on Worg on how to create a new export backend

beat me to it, go on. I might do some proofreading > then.) Marcin, Aren't you supposed to write a book about Emacs already ? ;) Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

Re: Step by step tutorial on Worg on how to create a new export backend

> On Feb 16, 2020, at 17:05, Marcin Borkowski wrote: > > > On 2020-02-16, at 01:46, Jean-Christophe Helary > wrote: > >>> On Feb 16, 2020, at 2:55, Marcin Borkowski wrote: >>> >>> >>> On 2020-02-14, at 21:48, Bastien wrote: >>

[O] htmlize

I tried to export to html and org told me to first install htmlize ( https://github.com/hniksic/emacs-htmlize). I tried to find an emacs-htmlize in the package list, and found nothing, so I went to the github page and since saw it was a seemingly normal el package called htmlize I checked agai

Re: [O] htmlize

Thank you Jonas ! Jean-Christophe > On Oct 25, 2017, at 21:51, Jonas Bernoulli wrote: > > This was discussed here: https://github.com/hniksic/emacs-htmlize/issues/7.

Re: [O] Applescript help

it's a block "to" if it's a line: >> (do-applescript "tell application \"Finder\" to set visible of application >> process \"Emacs\" to false") Jean-Christophe Helary --- @brandelune http://mac4translators.blogspot.com

[O] 3 manuals fail to export to PO (gnus, idlwave, org)

nvironment 'vtable' ses.texi:512: (po4a::tex) unmatched end of environment 'ftable' widget.texi:690: (po4a::tex) unmatched end of environment 'deffn' woman.texi:868: (po4a::tex) unmatched end of environment 'vtable' woman.texi:1115: (po4a::tex) unmatched end of environment 'vtable' woman.texi:1158: (po4a::tex) unmatched end of environment 'vtable' woman.texi:1193: (po4a::tex) unmatched end of environment 'vtable' woman.texi:1228: (po4a::tex) unmatched end of environment 'vtable' elisp.texi:167: (po4a::tex) unmatched end of environment 'html' modes.texi:2631: (po4a::tex) unmatched end of environment 'ftable' Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

Re: [O] 3 manuals fail to export to PO (gnus, idlwave, org)

llowing the '@item', and > the text for an item can continue for several paragraphs. > > Looks like po4a doesn't support this feature of the Texinfo language? > >> org.texi >> >> perl just keeps churning dat

Re: [O] Localized org-mode

use in their language. But emacs (the main org user) is so far behind in that respect compared to the rest of the FLOSS ecosystem that even having one mode that implements some sort of l10n would be huge. Although, it would be nice to have that work nicely with already existing l10n processes. Je

Re: [O] Localized org-mode

e: > > Hello, > > Jean-Christophe Helary writes: > >> There are no practical reasons why that should not be possible. > > Yet, I gave some already. Consider the following three documents: Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

Re: [O] Localized org-mode

> On May 10, 2018, at 0:41, Diego Zamboni wrote: > > > On Wed, May 9, 2018 at 3:48 PM, Jean-Christophe Helary <mailto:brandel...@gmail.com>> wrote: > You misquoted me. I was talking about design constraints when C and Lisp were > created, which kept language creat

Re: [O] Localized org-mode

sue. l10n is not as good as code *because* it is not defined with a higher priority and a better consciousness of the linguistic issues, and that is because monolingual activists think one language is sufficient (funny how that does not apply to programming languages, but they don't seem to be conscious of that contradiction...) Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune

Re: [O] Localized org-mode

> On May 12, 2018, at 20:07, Göktuğ Kayaalp wrote: > How do you know that if you first learned the translated version? Because (define eklemek +) If you run Scheme, you either know or can discover that. Jean-Christophe Helary --

Re: [O] Localized org-mode

> On May 13, 2018, at 7:48, Göktuğ Kayaalp wrote: > > People/packages can define their own keywords for in buffer settings, > and again here translations can cause breakage. That's a design problem, not a l10n problem. Jean-

Re: [O] info URL « open at point » patch

index that I written in Texinfo to get an info node with this > index. > Wouldn't it be shorter and easier to understand/maintain to explicitly describe the protocols: + ((setq node (Info-get-token (point) "\\(?:f\\(?:ile\\|tp\\)\\|https?\\)://" ??? Jean-Christophe

[O] bug#27140: Different key bindings between GUI emacs and terminal emacs

Sorry, I missed that. Proceed with closing and if there is an issue I'll send a report again. Jean-Christophe > On Jul 7, 2018, at 20:12, Nicolas Goaziou wrote: > > Nicolas Goaziou writes: > >> I think I fixed it in Org's master branch (aka Org 9.2). >> >> Meanwhile, I think setting `org-u

export dispatch → change the default "Contents" string

What is the parameter to change the default "Contents" ToC string when exporting to PDF ? -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

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

Thank you Juan. It does not seem to work as I expected, but that's OK, I just removed the ToC. Jean-Christophe > On Oct 2, 2021, at 1:35, Juan Manuel Macías wrote: > > Hi, jean-Christophe, > > Jean-Christophe Helary writes: > >> What is the parameter to chan

Elegant way to export org to Markdown ?

I wanted to write my teaching material in org on sr.ht, but... -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

Re: Elegant way to export org to Markdown ?

> On Oct 2, 2021, at 14:57, Protesilaos Stavrou wrote: > > On 2021-10-02, 14:20 +0900, Jean-Christophe Helary > wrote: > >> I'm trying to work with SourceHut (sr.ht) and right now they only >> accept Markdown syntax for their readme/wiki files. >>

Re: Elegant way to export org to Markdown ?

> On Oct 2, 2021, at 15:24, Ihor Radchenko wrote: > > Jean-Christophe Helary writes: > >> My follow-up question is, most of the ox-stuff seem to be installed by >> default, as far as I can tell. Why is ox-md not ? > > Not most. The default export backends are

Re: Elegant way to export org to Markdown ?

> On Oct 2, 2021, at 16:00, Ihor Radchenko wrote: > > Jean-Christophe Helary writes: > >> Next (related) question: >> >> Why that ugly number in front of headers defined with in HTML ? > > I have little knowledge about HTML export... I blind guess

Re: Elegant way to export org to Markdown ?

> On Oct 2, 2021, at 16:44, Tim Cross wrote: > > Jean-Christophe Helary writes: > >> I'm trying to work with SourceHut (sr.ht) and right now they only accept >> Markdown syntax for their readme/wiki files. >> >> Since I work in Emacs/org-mode t

Re: Elegant way to export org to Markdown ?

> On Oct 2, 2021, at 21:18, Morgan Willcock wrote: > > Jean-Christophe Helary writes: > >> I'm trying to work with SourceHut (sr.ht) and right now they only accept >> Markdown syntax for their readme/wiki files. > > Hi Jean-Christophe, > > If

Re: [emacs-humanities] Elegant way to export org to Markdown ?

Better solution found: quit sr.ht and move to a gitea implementation. No hassle, org files are fully recognized. Jean-Christophe > On Oct 2, 2021, at 14:20, Jean-Christophe Helary > wrote: > > I'm trying to work with SourceHut (sr.ht) and right now they only accept >

face for org-capture template

plies the fixed font to the capture target and not to the template buffer... I'm sure the answer is somewhere right under my nose... -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

Re: Problems generating the org-mode documentation

otnoteの中の改行を処理できてないようです。 > > 一方、masterのorg.orgでは@itemが > > http://git.savannah.gnu.org/cgit/emacs.git/tree/doc/misc/org.org#n6650 > > ここで参照されている[fn:78]の同じ箇所に改行があるので、この改行を削除すればpo4aで処理できる形式になるかもしれません。 > > http://git.savannah.gnu.org/cgit/emacs.git/tree/doc/misc/org.org#n21590

Re: A quick LaTeX reference guide in Org

> On Oct 25, 2021, at 0:37, Emmanuel Charpentier > wrote: > > "A quick LaTeX reference guide"... > > Nice oxymoron ! But it looks good in org-mode :-) Thank you Juan ! -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

Re: Problems generating the org-mode documentation

> On Oct 22, 2021, at 15:34, Pedro Andres Aranda Gutierrez > wrote: > > I have checked on a MacBook Pro with 16G running non-virtualised Same here. It is not a resource problem. -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelu

Regular expressions that describe most (?) org syntax ?

around… -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

Re: Regular expressions that describe most (?) org syntax ?

> On Oct 30, 2021, at 14:18, Ihor Radchenko wrote: > > Jean-Christophe Helary writes: > >> I am looking for a set of regular expressions that roughly describe most of >> the important org syntax. > > You need to study org-element.el starting from > `org-elem

epresent font increase ?

t to read. Any solution ? -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

Re: epresent font increase ?

> On Nov 9, 2021, at 21:16, Ihor Radchenko wrote: > > Jean-Christophe Helary writes: > >> I'm trying to increase the overall font for an epresent slide show that I'm >> presenting in 37 minutes and I keep getting this "face-attribute: Invalid

Re: epresent font increase ?

written in org: https://arxiv.org/abs/2106.05096 -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

Re: epresent font increase ?

> On Nov 9, 2021, at 21:11, Marco Wahl wrote: > > Jean-Christophe Helary writes: > >> I'm trying to increase the overall font for an epresent slide show >> that I'm presenting in 37 minutes and I keep getting this >> "face-attribute: Invalid face

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

are vastly superior to whatever markdown does, and we should not forget that markdown’s originator (at least the one who is still alive today) pretty much systematically despises free software and the free software movement on his blog… Jean-Christophe Helary > On Nov 29, 2021, at 4:46, K

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

> On Nov 29, 2021, at 7:57, Tom Gillespie wrote: > > PS Another brainstormed name: Orgsyn? Org Agnostic Syntax Modules → OrgASM -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

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

> On Nov 29, 2021, at 8:24, Jean-Christophe Helary > wrote: > > > >> On Nov 29, 2021, at 7:57, Tom Gillespie wrote: >> >> PS Another brainstormed name: Orgsyn? > > Org Agnostic Syntax Modules → OrgASM I understand that the issue is quite moot no

Re: Translation of the Org mode manual (was: Translation of manuals (was: SES manual French translation))

Ihor, Thank you for chiming in. > On Jan 4, 2024, at 20:34, Ihor Radchenko wrote: > > Jean-Christophe Helary > writes: >> I’m not sure this is the place to discuss translation theory... > > Let me steer this discussion to non-texi manuals - Org mode manual. Su

org-mode export to (latex) PDF

the default settings do not allow for out-of-the-box multilingual support. Is there an easy way to have that as the default behavior? -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

Re: org-mode export to (latex) PDF

> On Jul 10, 2021, at 22:52, Juan Manuel Macías wrote: > > Hi Jean-Christophe, > > Jean-Christophe Helary writes: > >> I guess it is an issue with the Latex backend and could have been solved >> with the proper Latex settings, but it seems weird that the def

Re: org-mode export to (latex) PDF

> On Jul 10, 2021, at 23:38, Juan Manuel Macías wrote: > > Hi Jean-Christophe, > > Jean-Christophe Helary writes: > >> I had given up on Latex because mixing languages sounded like a huge >> pain in the butt but I see that without some org-level infrastru

Re: help with a regexp

There are no reasons to limit the string after : to ascii. in isearch I tried: \[\{2\}cite.*\]\{2\}\|[^\[]cite:[^ \ ]* And it seems to do the job. -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

Re: org-mode export to (latex) PDF

e software, etc. but I'm not talking about that) proper font support for PDF, and well-documented workaround solutions. I don't mind going through the org→ODF→PDF route, but it's a waste of time. Still, it works *well enough* so it's actually the only viable option.

Re: org-mode export to (latex) PDF

discussion here, but it is sadly not the case.) -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/

org.texi and po4a

ssues with the texi itself, it looks like the texi conversion in po4a is a bit weak, but it would be awesome if somebody could check if there is something that could be simplified (org.texi is the *only* manual in the whole emacs distribution that faults at the conversion). -- Jean-Christo