Ihor Radchenko writes:
>> To reproduce this curious behavior, you only need this configuration:
>
> Confirmed.
>
> Something inside `org-todo' call in the hook triggers recursive-edit
> that, in turn, triggers premature call to post-command-hook containing
> note saving function.
I was wrong. Yo
Max Nikulin writes:
>> This can help with escaping syntax and spaces in verbatim.
>
> It should be enough to create nested "code" or "verbatim" inline objects
> with some attribute like :class file, :class var, :class dfn, etc.
> Export backend may interpret this attribute to create proper texi
alain.coch...@unistra.fr writes:
> I can only hope that the "observed inconsistency" related to
> EXPORT_FILE_NAME can be resolved.
Well. I do consider this a bug. However, it is not easy to fix.
`org-export-output-file-name' is used across all ox-*.el backends,
including third-party packages, an
"Christopher M. Miles" writes:
> I replaced step 5 with step 6 by extracting the logic code of
> org-link-beautify, but I found it does not have center-line. That's
> really weird.
> ...
>(put-text-property
> start end
> 'display (create-image "~/Downloads/.thumbnails/3veE
OK, thanks!
Just sent the patch. I realized in my original one
(https://list.orgmode.org/20220228140750.75761-1-dafydd.lu...@gmail.com/),
I'd also gotten rid of the with-temp-buffer in ox.el as long as I was
switching to write-region, because write-region can write a string
directly, but as that's
* lisp/ox-odt.el (org-odt-template, org-odt--export-wrap):
`write-region' instead of `save-buffer'.
`write-file' and `save-buffer' trigger major mode changes, which leads
to various mode-related hooks being run. This is undesirable: running
these on generated files is wasted time and computation,
Hi Max,
Just for reference, I (automatically) embed the `.tex' and `.org' source files
in PDFs I
produce.
Max Nikulin writes:
> It is unrelated to accessibility, but I have heard that OpenOffice may embed
> original document into generated PDF to allow “edit PDF” feature. Instead of
> attempti
Max Nikulin writes:
> From b2a546e239f32c78fb2dfaf92201a0b23eb76059 Mon Sep 17 00:00:00 2001
> From: Max Nikulin
> Date: Fri, 6 May 2022 23:34:52 +0700
> Subject: [PATCH] org-macs.el: Do not compare wall time and file modification
> time
Max, the patch does not currently apply onto main. Can y
David Lukeš writes:
> I'm happy to update the patch for ODT, but just FYI, I still don't
> have the FSF copyright assignment sorted out, which you warned me
> about since my tinychanges are accumulating. I've been in contact with
> both the FSF and my university, and long story short, the easiest
Hi all,
I get different syntax highlighting in code blocks when using async
export: no colors, just bold, italics and underlines. Is this expected,
and if so, is there maybe an easy fix I just don’t know about?
I found a similar problem in [batch export], but the workaround seems
relatively compl
On 01/10/2022 11:36, Ihor Radchenko wrote:
Also, would it help to embed an Org source into the generated PDF?
It is unrelated to accessibility, but I have heard that OpenOffice may
embed original document into generated PDF to allow "edit PDF" feature.
Instead of attempting to map PDF conten
On 02/10/2022 05:05, Christian Köstlin wrote:
Aforementioned unit-test.
+(ert-deftest ob-D/dub-basics ()
+ (if (executable-find "dub") (org-test-at-id
+ "81E17302-BE76-4E2A-93CA-0A7E121CB7C2" (org-babel-next-src-block 1)
+ (should (equal "abc, bac, cab, acb, bca, cb
Aforementioned unit-test.
Kind regards,
Christian
0002-testing-lisp-test-ob-C.el-Add-test-for-dub-support-i.patch
Description: Binary data
After adding unit-tests (following in another patchset) I found a bug in my
last patch.
Sorry for the noise.
Kind regards,
Christian
0001-lisp-ob-C.el-Support-dub-in-ob-D.patch
Description: Binary data
Thanks a lot for you feedbacks!
I rebased my change now, and I hope my changed commit message now conforms
more the the projects standard.
I will send in another patchset including some unittests, if I can get them
to work locally at my machine.
Thanks in advance,
Christian
0001-lisp-ob-C.el-Su
Ihor Radchenko writes:
> Can you execute [...] after loading org and try exporting again?
* EXPERIMENT 1 - TREATMENT *
*** VERSIONS:
- Emacs 29 (adaa2fc90e)
- Org (ebbc2ffaa)
*** CONFIGURATION:
;;; -*- lexical-binding: t; -*-
;;; .ema
On 01/10/2022 11:08, Ihor Radchenko wrote:
Tim Cross writes:
I do not think that we need to add all the variety of Texinfo-specific
constructs to the Org specification. Instead, we should add generic
configurable syntax elements to Org. (The Texinfo-specific part will
come as a separate library,
Ihor Radchenko writes:
No on both counts.
> "T.V Raman" writes:
>
>> 8. Now, connect the dots, newer LaTeX packages like the one mentioned
>>(there may well be others now or in the future) can inprinciple
>>ensure that the required "back pointers to regenerate the original
>>markup"
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> 2. install package =[M-x package-install RET org-link-beautify RET]=
>
> Hmm. Can you also reproduce without org-link-beautify?
I replaced step 5 with step 6 by extracting the logic code of
org-link-beautify, but I found it does no
Fixed
--
Bastien
On 01/10/2022 18:01, Ihor Radchenko wrote:
Max Nikulin writes:
I do not remember if the following idea has been discussed. What about
extending source blocks and inline source snippets to allow :results ast
header argument that caused executing during export only and expects
s-expression with A
Max Nikulin writes:
> I do not remember if the following idea has been discussed. What about
> extending source blocks and inline source snippets to allow :results ast
> header argument that caused executing during export only and expects
> s-expression with AST branch that is included into pa
On 29/09/2022 00:08, Tim Cross wrote:
2. Technically, Org mode cannot be used in any organisation (specifically
government
funded) where ther are policies which require that documents be
accessible. For example, technically, this means we cannot use org mode
in Australian government organisatio
On 01/10/2022 10:30, Ihor Radchenko wrote:
Max Nikulin writes:
Another point is that most of the mentioned commands a close to
verbatim, but Org has much more special characters recognized as markup
and no markup is allowed inside Org verbatim snippets. Escaping (by zero
width spaces?) of code
"Christopher M. Miles" writes:
> 2. install package =[M-x package-install RET org-link-beautify RET]=
Hmm. Can you also reproduce without org-link-beautify?
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapa
Max Nikulin writes:
>> Yes, I have just tried, and everything works fine now. Thanks!
>
> Greet.
>
> I would prefer to keep this issue tracked on https://updates.orgmode.org
> till a couple of places will be fixed in the Org repository to avoid nil
> and use -1 instead where `encode-time' expec
I attached the new patch.
From 67a00b91f53412435a5fd29406cf583a85f2de6d Mon Sep 17 00:00:00 2001
From: stardiviner
Date: Wed, 28 Sep 2022 20:46:52 +0800
Subject: [PATCH] org.el: Support auto display inline images when cycling
* lisp/org.el (org-toggle-inline-images): Support region.
(org-displa
Sébastien Miquel writes:
>> Hi, just following up. This is still an issue.
>
> I can confirm this. I've run into the same issue and fix.
>
> Are you using native compilation ? I think this must be the cause,
> though no one
> else could reproduce. If I byte compile the function instead, things w
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>>> Here is the prototype code which displaying image with text-property:
>>>
>>> #+begin_src emacs-lisp
>>> (put-text-property start end
>>>'display (create-image thumbnail nil nil :ascent 'center
>>> :max-height th
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>>> Here is the prototype code which displaying image with text-property:
>>>
>>> #+begin_src emacs-lisp
>>> (put-text-property start end
>>>'display (create-image thumbnail nil nil :ascent 'center
>>> :max-height th
Ihor Radchenko writes:
> Agree. Let's not go too far yet and focus on extending special blocks
> and the inline special block element I propose. These topics (especially
> for markup element with less edge cases) pop up on the Org ML from time
> to time and worth looking into regardless whether
Léo Ackermann writes:
> I can not reproduce this (ie. my second paragraph is unindented). Here
> comes my bug.org/org.txt files I have using ASCII export.
> I run Emacs 28.2, I just updated the packages.
> I think this is not of importance here, but I use Doom Emacs (up-to-date
> also).
>
> I con
Hi,
I can not reproduce this (ie. my second paragraph is unindented). Here
comes my bug.org/org.txt files I have using ASCII export.
I run Emacs 28.2, I just updated the packages.
I think this is not of importance here, but I use Doom Emacs (up-to-date
also).
I confirm that my goal is to have the
33 matches
Mail list logo
