Re: strange error exporting to ascii

"Fraga, Eric" writes: > On Friday, 22 Dec 2023 at 13:53, Ihor Radchenko wrote: >> Looks like your #+bibliography does not follow >> >> #+BIBLIOGRAPHY: /home/user/Literature/foo.bib plain option:-d >> >> format. > > It does not but the documentation does not say anything about a format > at all

Re: strange error exporting to ascii

On Friday, 22 Dec 2023 at 15:58, Ihor Radchenko wrote: > This is a problem with Org mode compilation. Try to reinstall. Problem persists. I've done make update restart emacs: fails to export. Then make cleanall make and restart emacs but also fails to export, both times with same error

Re: strange error exporting to ascii

Another data point: if I do a make cleanall and then start emacs without org compiled, exporting (to both targets) works, although there are complaints initially about the autoload file not being present etc. Slow, mind you. ;-) But I can live with this in the short term so I can get my work

Re: [PATCH] ob-C.el compile-only header argument, was Re: How to use mpirun with C or C++ Org-babel?

Leo Butler writes: >> What will happen if we have something like :results value or :results >> output instead of :results file link? > > Originally, I felt that only ":results file" makes sense. I have adopted > your suggestion, though, and added test cases so that the compiler > stderr output

Re: Unable to install from elpa

Ihor Radchenko writes: > Let's first try to report and see what the reply is. > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63800 This is now semi-fixed on ELPA. Not for Org mode, but for other built-in packages. Org mode in particular is not (yet). See

Re: strange error exporting to ascii

Hi Ihor, thank you for the response. On Friday, 22 Dec 2023 at 13:53, Ihor Radchenko wrote: > Looks like your #+bibliography does not follow > > #+BIBLIOGRAPHY: /home/user/Literature/foo.bib plain option:-d > > format. It does not but the documentation does not say anything about a format at

Re: strange error exporting to ascii

"Fraga, Eric" writes: > Ah! Interesting. I had forgotten about requiring ox-bibtex in my > configuration files. I've now removed it but now get a new error > (elided): > > Debugger entered--Lisp error: (invalid-function org-element-with-buffer-copy) > org-element-with-buffer-copy(:to-buffer

Re: [PATCH] Re: [feature request] startup variable for link display

Rudolf Adamkovič writes: >> #+startup: showlinks >> and >> #+startup: compresslinks > > Why not continue with established terminology? > > #+STARTUP: descriptivelinks > #+STARTUP: literallinks I do not have a strong opinion here. I used "show" following showstars/showeverything/etc and because

Re: [BUG] orgmode.org is not up-to-date with the latest orgweb master

Bastien Guerry writes: >> Bastien, may you please check the publish scripts? > > I've launched it, the translation is online now. Thanks! Fixed. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at

Re: strange error exporting to ascii

On Friday, 22 Dec 2023 at 15:14, Ihor Radchenko wrote: [...] > This is also something from ox-bibtex.el. I suspect that you do not need > ox-bibtex.el. It is an old library predating Org's native citation support. > > Also, merely loading ox-bibtex.el changes Org export behaviour. Be careful.

Re: [PATCH] Re: [feature request] startup variable for link display

Ihor Radchenko writes: > #+startup: showlinks > and > #+startup: compresslinks Why not continue with established terminology? #+STARTUP: descriptivelinks #+STARTUP: literallinks Rudy -- "It is no paradox to say that in our most theoretical moods we may be nearest to our most practical

Re: strange error exporting to ascii

"Fraga, Eric" writes: > So there seems to be some compilation bug maybe? I will build Emacs > from git as the version I'm using was built in September (I don't update > during term time as I depend on Emacs and org for my teaching). I'll > report back after doing so. This is most likely a bug

[PATCH] Re: [feature request] startup variable for link display

"Fraga, Eric" writes: > Assuming I have not missed something, is there a variable I can set on > visiting an org buffer/file that ensures that links are displayed fully? > > Once I've loaded an org file, I can > >M-x org-toggle-link-display RET. > > but I would like certain files to start up

Re: strange error exporting to ascii

"Fraga, Eric" writes: > So, long story short, I try to export the original document to ascii and > I get an error related to citations. Having seen some updates to > exporting citations on the list over the past few weeks, I figured I > should upgrade org to the latest version. Now exporting

Re: strange error exporting to ascii

On Friday, 22 Dec 2023 at 16:36, Ihor Radchenko wrote: > > This is most likely a bug with internal dependencies. > I need some time to figure out how to approach it. Okay, thank you. For the record, I've re-built Emacs from git and the problem persists so it's not (necessarily) Emacs itself.

[BUG] ox-beamer uses ox-latex private functions

In three separate places (lines 779, 825 and 874) ox-beamer uses ox-latex private functions namely: line779: `org-latex--wrap-label' line 825: `org-latex--insert-compiler' line 874: `org-latex--format-spec' I appreciate ox-beamer is a backend backend derived from ox-latex but isn't this bad

[QUESTION] Should KEYWORD values in org-export-options-alist be lowercase?

Should the KEYWORD values in `org-export-options-alist' that are uppercase be lowercase to reflect what users see say when using a template and/or for consistency? Similarly, for the KEYWORD values in :options-alist in `org-export-define-backend' for example in ox-latex.el? For example the TITLE

Re: [QUESTION] Should KEYWORD values in org-export-options-alist be lowercase?

Niall Dooley writes: > Should the KEYWORD values in `org-export-options-alist' that are > uppercase be lowercase to reflect what users see say when using a > template and/or for consistency? > > Similarly, for the KEYWORD values in :options-alist in > `org-export-define-backend' for example in