Re: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir

Hi Max, Thanks for your reply. "Max Nikulin" writes: > On 26/02/2023 08:52, gnu...@pm.me wrote: >> (basically similar to what #include >> directive in C preprocessor would do, e.g.). As of now, the >> above >> s.org exports to s.html which has the file: link converted to >> >>

ox-beamer/latex questions

Hello, I have a couple questions about TODO items, cookies and export. I am unable to find anything the manual that seems relevant. Please see the attached. TIA, Leo #+TITLE: ox-beamer/latex questions #+AUTHOR: Leo Butler #+OPTIONS: H:2 toc:t num:t tags:nil todo:nil #+LATEX_CLASS: beamer

Re: [FR] Allow to #+include files verbatim without any processing (was: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir)

Hi Timothy, Thanks for your reply. "Timothy" writes: > Hi Ihor, > >> This sounds like a reasonable request. >> What we may do here is allowing a new parameter :verbatim > > From a read of the original email, it sounds like a `:dir' > parameter could also > solve this use case, and allow for a

Re: How to produce an org-ref citation from ivy-bibtex

You can try something like this #+BEGIN_SRC emacs-lisp (setq bibtex-completion-format-citation-functions '((org-mode . (lambda (keys) (org-ref-insert-cite-keys keys) "")) (latex-mode. bibtex-completion-format-citation-cite) (markdown-mode .

Broken org-persist-storage probably leads to ‘org-open-at-point’ ask for TAGS file

Hello, I have discovered a weird behaviour that I have tracked back to org-persist and org-element-cache, where after some time, when I try to follow a document internal link in org mode, whether to a headline or to a =<>=, it would ask me to load a TAGS file, I think somewhat like how xref might

Re: [FR] Allow to #+include files verbatim without any processing (was: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir)

Hi Ihor, > This sounds like a reasonable request. > What we may do here is allowing a new parameter :verbatim >From a read of the original email, it sounds like a `:dir' parameter could also solve this use case, and allow for a bit more flexibility. All the best, Timothy -- Timothy

Re: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir

On 26/02/2023 08:52, gnu...@pm.me wrote: (basically similar to what #include directive in C preprocessor would do, e.g.). As of now, the above s.org exports to s.html which has the file: link converted to file:///home/user/media/s/media/s01_image.png Doesn't cpp behave in a similar way? grep

Re: [BUG] HTML-export citation suffix rendering with CSL [9.6 (9.6-??-bed47b437 @ /home/romeo/.emacs.d/.local/straight/build-28.2.50/org/)]

Dear All, On Wed, 25 Jan 2023 at 12:53, Ihor Radchenko wrote: > Confirmed, after replacing the .bib key with > abnarQuantifyingAttentionFlow2020a. > > András, may you take a look? First of all, apologies for reacting that late, unfortunately, I've had way less time to work on Org-mode and

Re: ox-rst still working?

Hello, just realized that it is ok if I open the file ox-rst.el and evaluate the hole buffer. I do have (require 'ox-rst) in my .emacs file and I have evaluated that a number of times, but for some reason the rst backend is only registered with the Org dispatch when evaluating the ox-rst.el

Re: [DISCUSS] "same text-property competing" problem in external packages

stardiviner writes: > I got a problem when more than one Emacs package competing on setting > text-property on same target from different packages. > > Here is the original problem and discussion link: > https://github.com/nobiot/org-transclusion/issues/166 > > Does anybody have a good idea to

Re: [PATCH] lisp/ob-screen.el: Support ~:var~ header args for babel blocks

Ken Mankoff writes: >> I noticed that ob-core besides org-babel-default-header-args:LANG uses >> org-babel-header-args:LANG. The latter is not defined in ob-screen, >> however I am unsure concerning its effect (completion?). > > I don't understand this either. It defines the expected values of

Re: inconsistency with :eval yes in orgmode.org and gnu.org manuals for org 9.6, 9.5?

Ihor Radchenko writes: > Subject: [PATCH] org-manual: Clarify that :eval yes obeys > `org-confirm-babel-evaluate' > > * doc/org-manual.org (Limit code block evaluation): Clarify :eval yes > value. Applied, onto bugfix.

[FR] Allow to #+include files verbatim without any processing (was: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir)

gnu...@pm.me writes: > I have a file s.org in ./ (current directory), which includes > another file s0.org living under ./media/s/: > > ./s.org: > > #+TITLE: s > #+INCLUDE: "./media/s/s0.org" > > ./media/s/s0.org: > > * s0 > ** s01 >file:media/s01_image.png > > I want the org export to html

Re: [BUG] Emacs-29.0.60: (setopt org-babel-load-languages ...) may cause warnings

Ihor Radchenko writes: >> 1. I have assigned my copyright for Emacs stuff to the FSF > > Bastien, may you please confirm? I do, sorry for the delay. -- Bastien Guerry

Re: bug#61546: [PATCH] Fix some org functionality breaking upon changing `calendar-buffer'

Ihor Radchenko writes: >> That is a bit of an issue. Do org contributions and emacs contributions >> count towards the same 15 LoC limit? Yes. Copyright-wise, contributions to Org are contributions to Emacs. >> If so, I have already exhausted mine, so TINYCHANGE won't work. > > AFAIK, we

Re: [PATCH] Avoid crash in `org-file-contents' in case of network failure

Ihor Radchenko writes: > Damien Cassou writes: > >> I've signed the FSF copyright agreement in the context of my >> contributions to Emacs. Do I need to do any more paperwork? > > No, you don't. > Bastien, could you please check FSF records? I confirm Damien's FSF record is in order. --