Ruijie Yu writes:
> "Dr. Arne Babenhauserheide" writes:
>
>> [...]
>> You could try using a ZERO WIDTH SPACE around the expression [...]
>
> Thank you Arne and Steven. I have tried to just insert the zero width
> space, and it seems to work very well (at least on HTML export, which is
> the on
On Tue, 28 Mar 2023 10:04:24 +0200, Christian Moe wrote
Hi,
> I'm trying and failing to export images from TikZ code, apparently
> because the temporary PDF is misplaced. Here is a minimal example just
> exporting the PDF:
> #+LATEX_HEADER: \usepackage{tikz}
>
> #+header: :fit yes
> #+begin_src
Hello,
The Emacs integrated development environments Slime and Sly
communicate by means of similar RPC protocols with different server
programs: Swank in case of Slime and Slynk in case of Sly. However,
the code in org-babel-execute:lisp always expects to talk with Swank
because of the hard-code
On 2023-03-29, at 05:12, Ruijie Yu via General discussions about Org-mode.
wrote:
> Hello,
>
> I am working on a piece of CJK text, which requires italicization.
>
> --8<---cut here---start->8---
> 任何一个章节可以通过增加例如 =TODO= 或者 =HOLD= 等关键词来被设置成 /待办/ 。
> --8<-
Hello,
my Emacs 29 asked me to report this. I don't know why it happend. Not
sure how I can help you here.
It is Debian 11 on a Raspberry Pi 4. Emacs 29 selfbuild ("GMP GNUTLS
JSON LIBSELINUX LIBSYSTEMD LIBXML2 MODULES NATIVE_COMP NOTIFY INOTIFY
PDUMPER SECCOMP SQLITE3 THREADS XIM ZLIB") runni
c.bu...@posteo.jp writes:
> my Emacs 29 asked me to report this. I don't know why it happend. Not
> sure how I can help you here.
> It is Debian 11 on a Raspberry Pi 4. Emacs 29 selfbuild ("GMP GNUTLS
> JSON LIBSELINUX LIBSYSTEMD LIBXML2 MODULES NATIVE_COMP NOTIFY INOTIFY
> PDUMPER SECCOMP SQLI
Matt writes:
> Does anyone know which function is responsible for re-fontifing source
> blocks?
`org-src-font-lock-fontify-block', which is using major-mode's native
fontification. The major mode is determined by `org-src-get-lang-mode',
which can be customized using `org-src-lang-modes'.
Org
alain.coch...@unistra.fr writes:
> | | ---+--- |
> | x | x |
>
> At 1st sight, it does not seem so to me (in particular, LaTeX export
> does not turn '---+---' into an horizontal rule for the 2
> corresponding columns). So then one could imagine that '|' at
> the beginning of a line start
gerard.vermeu...@posteo.net writes:
> The Emacs integrated development environments Slime and Sly
> communicate by means of similar RPC protocols with different server
> programs: Swank in case of Slime and Slynk in case of Sly. However,
> the code in org-babel-execute:lisp always expects to talk
Dear Ihor,
thanks for reply.
Am 29.03.2023 11:31 schrieb Ihor Radchenko:
May you also provide the full text of the warning that asked you to
send
this bug report?
Sorry, I'm not able to do that. I just send what was auto-generated for
that email.
I'm also not able to reproduce.
It is not
c.bu...@posteo.jp writes:
>> May you also provide the full text of the warning that asked you to
>> send
>> this bug report?
>
> Sorry, I'm not able to do that. I just send what was auto-generated for
> that email.
> I'm also not able to reproduce.
>
> It is not in the message buffer.
It should
I am having a problem using Org Cite with Org Publish (Emacs 28.1, Org 9.6.1).
Publication of documents containing an Org Cite citation fails every time.
Here's a minimum (not) working example. I have a file `publish.el` which
contains the following vanilla Elisp.
```
(require 'package)
(setq pa
Bastien writes:
> That said, do you have any idea how to fix the bug people encounter
> when installing Org from ELPA and being bitten by "invalid-function
> org-assert-version"?
Even though we identified that the problem is related to a combination
of old Emacs version and OS-specific Emacs cus
Ihor Radchenko writes:
> It is a bug in `org-fold-show-children'. The reason your example works
> has nothing to do with what the function intends to do.
>
> Fix is attached.
> From a5e8062b258fc7c4e4d4129278101a8d20bb43c4 Mon Sep 17 00:00:00 2001
> Message-Id:
>
> From: Ihor Radchenko
> Date:
"Marvin J." writes:
> Org-agenda provides the possibility to automatically restore the previous
> window configuration after closing the agenda buffer using org-agenda-quit
> (bound to q). This is achieved by setting
> org-agenda-restore-windows-after-quit to t.
>
> However, there is also another
Ihor Radchenko writes:
> One possibility is hash collision in `org-babel-temp-stable-file'.
> Something similar to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56255
>
> I will see if I can implement collision-free hashing to work around the
> limitations of sxhash.
Done, on main.
Fixed.
https:
Pedro Andres Aranda Gutierrez writes:
> Having said that, I was also (just a bit) bugged by the fact that
> bibliography file names are completely expanded when generating LaTeX.
> Couldn't we avoid that for LaTeX export?
It is in `org-cite-list-bibliography-files'.
AFIAU, full path is forced th
Amery Gration writes:
> I am having a problem using Org Cite with Org Publish (Emacs 28.1, Org
> 9.6.1). Publication of documents containing an Org Cite citation fails every
> time. Here's a minimum (not) working example. I have a file `publish.el`
> which contains the following vanilla Elisp.
[Adding Org ML back to CC]
Amery Gration writes:
> Thanks so much for replying. Do you mean the MWE works for you without error,
> or that the MWE doesn't work for you at all?
Your MWE works for me and I do get html exported with citations without errors.
Though the MWE is not 100% precise. If
On 29/03/2023 20:38, Ihor Radchenko wrote:
Even though we identified that the problem is related to a combination
of old Emacs version and OS-specific Emacs customization
Ihor, who should notice improvement due to this patch? Is it related to
Emacs-29.1 release? The issue is weird, but on the
Max Nikulin writes:
> On 29/03/2023 20:38, Ihor Radchenko wrote:
>> Even though we identified that the problem is related to a combination
>> of old Emacs version and OS-specific Emacs customization
>
> Ihor, who should notice improvement due to this patch? Is it related to
> Emacs-29.1 release?
Looks reasonable... we put the .org and .bib file(s) in the same
directory and we can use relative paths... That's what I would do in a
pure LaTeX environment (and in overleaf.com)
Could be expanded to same directory or its leaves... like when I have
the .org file and a bibliography directory in t
Cool, I would be happy to submit a patch!
Thanks,
Derek
On Wed, Mar 29, 2023 at 3:33 AM Ihor Radchenko wrote:
> Matt writes:
>
> > Does anyone know which function is responsible for re-fontifing source
> blocks?
>
> `org-src-font-lock-fontify-block', which is using major-mode's native
> font
On Wednesday, 29 March 2023 10:00:35 CEST Pedro Andres Aranda Gutierrez wrote:
> On Tue, 28 Mar 2023 10:04:24 +0200, Christian Moe
> wrote
> Hi,
>
> > I'm trying and failing to export images from TikZ code, apparently
> > because the temporary PDF is misplaced. Here is a minimal example just
> >
On Wed, 29 Mar 2023 13:04:31 -0400 Derek Chen-Becker wrote ---
> Cool, I would be happy to submit a patch!
Sure, if that's something you'd enjoy. I'm happy to assist, if needed.
> On Wed, Mar 29, 2023 at 3:33 AM Ihor Radchenko yanta...@posteo.net> wrote:
>
> Org provides some de
Hi,
Pardon the noise: It turned out to be a pretty obvious problem with my
setup that has now been resolved.
I had modified org-latex-pdf-process to use xelatex, and for some reason
my setup lacked the =-output-directory %o= switch. I should probably
have thought of that first, but the omission
On 29.03.2023 11:42, Ihor Radchenko wrote:
gerard.vermeu...@posteo.net writes:
The Emacs integrated development environments Slime and Sly
communicate by means of similar RPC protocols with different server
programs: Swank in case of Slime and Slynk in case of Sly. However,
the code in org-
On Wednesday, 29 March 2023 23:15:03 CEST Christian Moe wrote:
>
> Hi,
>
> Pardon the noise: It turned out to be a pretty obvious problem with my
> setup that has now been resolved.
>
> I had modified org-latex-pdf-process to use xelatex, and for some reason
> my setup lacked the =-output-direct
Greetings,
New to the list, and this is my first post. I hope it's ok.
I'm experiencing an issue when trying to use org-publish.
In attempting to convert the divs generated for preamble, content, and
postamble, by specifying, what I believe to be the appropriate setting
within org-publish-pr
29 matches
Mail list logo
