Re: [patch] fix ox-latex async export bug

Hi, Rasmus Pank Roulund writes: This is most likely due to native compilation which compiles the unquoted lambda. Once compiled, it (presumably) fails to be passed to the external emacs process. Ah, interesting. Is this a bug or a feature? I think the bug's with org-mode. As I explain

Re: [PATCH] Fix regex for determining image width from attribute

Hi Matt, Thanks for your thoughtful deliberation on this. > I think the essential disagreement is whether org should take an action if not > explicitly told to do so. I think org should only perform some action if given > a clear directive. In this context, I feel that org is guessing what the

Re: how to export red colored TeX to latex

Very nice Juan! I would find this use of links quite useful. -- : Eric S Fraga, with org release_9.5-230-g2bbac4 in Emacs 29.0.50 : Latest paper written in org: https://arxiv.org/abs/2106.05096

Re: [PATCH] Fix org-comment-line-break-function

Kaushal Modi writes: > On Tue, Nov 30, 2021 at 6:29 PM Tim Cross wrote: > > It would be good to get Nicholas' input here as I think he wrote the > original function back in 2012. > > Just to see what happens, I tried this: > > M-: (setq-local comment-line-break-function

Clocktable parameters

Hello, I find the differences between the variables (1) org-clocktable-defaults (2) org-agenda-clockreport-parameter-plist hard to understand. Ok, (1) seems reasonably clear. It's described in `info' (there's no doc-string). The variable (2) confuses me. According to its doc string (there's no

[Bug] incorrect indent of next heading after org-paste-subtree

Another old bug with org-paste-subtree. It make indentation of next heading wrong. Consider the following document and follow described steps: >8 #+STARTUP: indent Enable soft indent mode Put to kill ring some text *without trailing newline* that represents a subtree. In my case it

Re: [BUG] C-c C-* causes "org-element--cache: Unregistered buffer modifications detected."

On 21/11/2021 15:35, Ihor Radchenko wrote: Max Nikulin writes: C-\ russian-computer RET A C-* Latin "A" to type Cyrillic "Ф" Apparently, C-* on Ф Put cursor on this line and hit =C-c C-*= to make it a heading and just Ф are producing different

Re: [BUG] clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

Hello Jeff You clock table works for me, including your missing rate of 150. I attach a screen shot. By the way, you have a ":inherit-props t" which is not on the #+BEGIN: clocktable line. I assume that has been corrupted in the email formatting. Best wishes

Re: [org-cite] autoload oc processors?

Am 29.11.2021 um 23:48 schrieb Nicolas Goaziou: Hello, Timothy writes: A more sophisticated solution probably exists, but my thought was that if a cite export keyword like this is seen: ┌ │ #+cite_export: FORMAT ... └ and there is no known cite backend `FORMAT', then we could just

Re: [patch] fix ox-latex async export bug

Hi, Nicolas Goaziou writes: This is not really the same fix. Indeed, but I tested it and it does work. You're quoting a lambda, which should not be required if the problem disappeared. IOW, the true fix probably belong in the `org-export-async-start' function. What happens is as follows  

Re: [PATCH] Fontification for inline src blocks

Pushed . All the best, Timothy

Re: [BUG] C-c C-* causes "org-element--cache: Unregistered buffer modifications detected."

Max Nikulin writes: > Ihor, thank you for your work related to such issues. I had a hope to > thank you for the fix, but I faced a warning again in a bit modified > scenario. This time it is soft indent mode. > ... > First letter of new heading must be a capital one, though it can be > Latin.

Re: [PATCH] Fontification for inline src blocks

Hi Sebastien, > Sorry for the late reply, but isn’t there a `message' call leftover from > debugging ? Ooops! Time for a clean-up patch to fix the things you and Ihor’s just noticed. Thanks for mentioning this. All the best, Timothy

Re: [ANN] ox-pandoc, revived

On Tue, Nov 30, 2021 at 9:27 AM Alex Fenton wrote: > > On 30/11/2021 15:09, Bruce D'Arcus wrote: > AFAIK pandoc still doesn't support the official Org Mode syntax. > > ox-pandoc relies on the fact that it first exports to an intermediate > org file before handing off to pandoc. SRC blocks and

[ANN] ox-pandoc, revived

Hello, ox-pandoc is an exporter for Org Mode that uses pandoc (https://pandoc.org/) to export to a very wide variety of text markup (e.g. markdown variants), document (ODT, docx) and presentation (e.g. html, .pdf) formats. It is available via MELPA and at:

Re: [ANN] ox-pandoc, revived

Am 30.11.2021 um 09:40 schrieb Alex Fenton: Hello, ox-pandoc is an exporter for Org Mode that uses pandoc (https://pandoc.org/) to export to a very wide variety of text markup (e.g. markdown variants), document (ODT, docx) and presentation (e.g. html, .pdf) formats. It is available via MELPA

Re: [ANN] ox-pandoc, revived

On 30/11/2021 15:09, Bruce D'Arcus wrote: Did pandoc get support for org-cite? There's been basically zero activity on this issue I created awhile back: https://github.com/jgm/pandoc/issues/7329 AFAIK pandoc still doesn't support the official Org Mode syntax. ox-pandoc relies on the fact

Re: Unintended consequences of removing org-speed-commands-user

Thank you for the tip. I didn't realize that `member' could be used in this way to insert an element at a particular point in a list. But this doesn't address the main issue in my post, that the user has two different approaches for adding commands to `org-speed-commands' depending on whether it

Re: [PATCH] Fontification for inline src blocks

Timothy writes: >>> [use org-element] > > Ah right. We now also have the new thread about using org-element. I think > that > sounds like a great change overall, but am still keen for this patch to go > through for the moment — just as a stop gap till org-element exposes all the > necessary

Re: how to export red colored TeX to latex

>>> "JK" == John Kitchin writes: > maybe @@latex:\textcolor{red}{$\delta \phi = \frac{2 m}{R}$}@@ will do. > John Thanks! That worked! smime.p7s Description: S/MIME cryptographic signature

Re: how to export red colored TeX to latex

Hi, Uwe Brauer writes: > Hi > > I want to obtain a latex file that contains > > \textcolor{red}{$\delta \phi = \frac{2 m}{R}$} > > > However when I add > \textcolor{red}{$\delta \phi = \frac{2 m}{R}$} > > To an org file and export it as Latex, the construct ends up like this > > >

[PATCH] Fix org-comment-line-break-function (was: Is M-j broken for you in Org on Emacs 27 and 28?)

Hi Tim and all, Thanks for sticking with me here... Tim Cross writes: > I just checked this when running emacs -Q and get the following > > comment-line-break-function is a variable defined in ‘simple.el’. > > Its value is ‘org-comment-line-break-function’ > > and fill-prefix is > >

Formal syntax for org-cite

Hi All (and Nicolas in particular), There's recently been a little bit of progress on the Pandoc issue for org-cite support (https://github.com/jgm/pandoc/issues/7329#issuecomment-982805313), and the maintainers are now asking if there is any specification for org-cite syntax. Looking at

Re: Merging ox-texinfo+ into ox-texinfo

Sorry for the delay, I got side-tracked with many other things. Nicolas Goaziou writes: >>> It is possible to mix the two styles; >> >> Well... it turned out not to be true, but I should be able to get it >> to work. > > Then I suggest to use "attr_texinfo" keyword, for example: > >

Re: how to export red colored TeX to latex

> Hi, > Uwe Brauer writes: > Not exactly related, but if it helps, I have defined this custom link > for colored text segments: > (NB: I apply two colors for `:face', because normally I use two themes, > one clear for the day and another dark for the night hours: when my dark > theme is

Re: citeproc-org and org-ref 3

See https://www.youtube.com/watch?v=rRR-5NSpKyE for an overview of what to do. basically you need a csl file that provides the style you want, and you specify it like this in the org file or in default settings. You may also need a locale file if you are not blogging in english. #+csl-style:

Re: how to export red colored TeX to latex

Uwe Brauer writes: > Thanks, right now, I don't need links but it is good to know that there is a > way to use them. It's just a way of using links to produce different strings, depending on the export format (LaTeX, HTML...). I use them quite a bit for text segments as \foreignlanguage{}{},

citeproc-org and org-ref 3

Dear John, and dear Andras, Having updated my org-ref to the last version, I see that the html export of bibliography does not work any longer for my blog. Reading Andras's note here https://github.com/andras-simonyi/citeproc-org I confess that I am lost. What have I to do to not waste too

Re: citeproc-org and org-ref 3

Dear Joseph, unfortunately, my note on the `citeproc-org` page has become kind of misleading and has to be updated because org-ref didn't switch to the new org-cite citation syntax after all, although this was the plan for a while. I think if you wish to use org-ref 3 then you should simply

Re: Is M-j broken for you in Org on Emacs 27 and 28?

Tim Cross writes: > Based on your report of having org 9.3, my suspicion is that your org > version is too old for the current Emacs versions (since the change in > 2019 to use default-indent-new-line for C-M-j and M-j. I don't think > this is a bug in current Org or Emacs. Just for reference,

how to export red colored TeX to latex

Hi I want to obtain a latex file that contains \textcolor{red}{$\delta \phi = \frac{2 m}{R}$} However when I add \textcolor{red}{$\delta \phi = \frac{2 m}{R}$} To an org file and export it as Latex, the construct ends up like this \textcolor{red}\{\(\delta \phi = \frac{2 m}{R}\)\}

Re: how to export red colored TeX to latex

maybe @@latex:\textcolor{red}{$\delta \phi = \frac{2 m}{R}$}@@ will do. John --- Professor John Kitchin (he/him/his) Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin

Re: citeproc-org and org-ref 3

Many thanks Andras for this first clarification. There is no hurry and after John's advice, I will take the most convenient decision. Many thanks to both of you for your very helpful works. Best wishes, Jo. Le 30/11/2021 à 18:16, András Simonyi a écrit : > Dear Joseph, > > unfortunately, my

Re: [PATCH] Fontification for inline src blocks

Hi, Timothy writes: Pushed . Sorry for the late reply, but isn't there a =message= call leftover from debugging ? Regards, -- Sébastien Miquel

Question about using `org-add-note' programmatically

I'm trying to write a function that adds a note to the current `org-mode' heading. Naively I write it as (defun my/add-note () (interactive) (org-add-note) (insert "some text") (org-ctrl-c-ctrl-c)) but this does not work. Calling the function (on a recent build of Emacs 29)

Re: [ANN] ox-pandoc, revived

Hi Alex, Great to hear that someone is taking care of ox-pandoc again! Thanks for stepping up, and I wish you all the best . Timothy

Re: [ANN] ox-pandoc, revived

On Tue, Nov 30, 2021 at 7:50 AM Alex Fenton wrote: > The current version includes initial support for org citations in Org 9.5. > This feature is experimental and I welcome feedback and reports on this or > any other aspect of the package. Did pandoc get support for org-cite? There's been

[PATCH] New function org-speed-command-add for adding/modifying speed commands

Over the weekend I thought about this issue of configuring `org-speed-commands' more easily, and I believe I have come up with a simpler solution that I have provided in the attached patch. This patch creates a new function `org-speed-command-add' that can be used to add new speed command

Re: Stable 9.5: invalid function (date date)

Ihor Radchenko writes: > Tim Loderhose writes: > >> Hi, >> >> I am also getting this error. It's fixable only by re-installing org from a >> emacs -q, I assumed because files on the agenda file list are visited >> before org is fully installed? >> Unfortunately, this also occurs with a fresh

Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode)

Hi, * M ‘quintus’ Gülker wrote: > > Am Montag, dem 29. November 2021 schrieb Karl Voit: >> It seems to be the case that the name "Orgdown" is the reason why >> the Org-mode community does not support the idea of an >> implementation-agnostic definition of the syntax. Which is ... kinda >> funny

Re: [BUG] clocktable :inherit-props does not respect global property setting [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210823/)]

Confirmed, after updating org it now works! Thanks for your help. On Tue, Nov 30, 2021 at 1:07 AM Colin Baxter  wrote: > Hello Jeff > > You clock table works for me, including your missing rate of 150. I > attach a screen shot. > > By the way, you have a ":inherit-props t" which is not on the

[PATCH] org.el: Fix the filling of regions containing lists

Hi, The attached patch fixes the following issues with the functions =fill-region= and =fill-paragraph=, when called with an active region containing a list. In the examples, replace 'long line' by long lines to be filled.  + Calling =fill-region= on a region which contains a list with single  

Re: [PATCH] Fix org-comment-line-break-function

On Tue, Nov 30, 2021 at 3:20 PM Marco Wahl wrote: > > > diff --git a/lisp/org.el b/lisp/org.el > index 1a1375461..fdeec0d67 100644 > --- a/lisp/org.el > +++ b/lisp/org.el > @@ -19695,7 +19695,8 @@ non-nil." >(save-excursion (forward-char -1) (delete-horizontal-space))

Re: [PATCH] org.el: Fix the filling of regions containing lists

wow thank you i look forward to this. On 11/30/21, Sébastien Miquel wrote: > Hi, > > The attached patch fixes the following issues with the functions > =fill-region= and =fill-paragraph=, when called with an active region > containing a list. > > In the examples, replace 'long line' by long

Re: Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode)

Karl, The exact naming of a thing is nearly always the most contentious step in trying to promulgate it. In my own field we can easily get all parties to agree on a definition, but they refuse to budge on a name. As others have said, I wouldn't worry about kibitizing over the name. I would

Re: Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode)

Tom Gillespie writes: > Karl, >The exact naming of a thing is nearly always the most contentious > step in trying to promulgate it. In my own field we can easily get all > parties to agree on a definition, but they refuse to budge on a name. > As others have said, I wouldn't worry about

Re: [PATCH] Fix org-comment-line-break-function

On Tue, Nov 30, 2021 at 6:29 PM Tim Cross wrote: > > It would be good to get Nicholas' input here as I think he wrote the > original function back in 2012. > Just to see what happens, I tried this: M-: (setq-local comment-line-break-function #'comment-indent-new-line) .. and then M-j started

Re: citeproc-org and org-ref 3

Many thanks John ! I will try and I will inform all of you. Best wishes, Jo. Le 30/11/2021 à 18:31, John Kitchin a écrit : > See https://www.youtube.com/watch?v=rRR-5NSpKyE > for an overview of what to > do. basically you need a csl file that

Re: smart quotes and languages like en-gb

Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> I have noticed that smart quotes are not picked up for “long” languages, >> like “en-gb”, since smart quotes are defined for “short” languages, like >> “en”, in org-export-smart-quotes-alist. >> >> The attached patch is an attempt at

Re: oc-biblatex too aggressive in replacing styles

Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> However, I think it is currently too aggressive in overwriting styles. > > Ah? > >> Could it perhaps accept any style that is given in >> ‘org-cite-biblatex-options’ / ‘org-latex-packages-alist’ and only >> overwrite it if another style

Re: [patch] fix ox-latex async export bug

Timothy writes: > Hi Tim, > >> I’m wondering if this could be a problem when exporting to latex if the >>underlying latex process encounters errors and is waiting for user >> input before >>it can continue (which happens if there are problems in the tex >> source latex is >>trying to process)?

Re: [PATCH] Fix org-comment-line-break-function

Hi Richard and all, [...] > Just to be extra, super sure, I built Emacs this afternoon from a > checkout of the repo, and the error is *still* there, with the same > cause. In that build, with emacs -Q, I have: > > (org-version) > "9.5" > > (emacs-version) > "GNU Emacs 29.0.50 (build 1,

Re: [patch] fix ox-latex async export bug

Sébastien Miquel writes: > Hi, > > Nicolas Goaziou writes: >>> I don’t really understand why this bug happens to be honest. >> The patch is already an improvement, but the beast is still lurking, >> indeed. > This is most likely due to native compilation which compiles the > unquoted lambda.

Re: [PATCH] Fix org-comment-line-break-function

Marco Wahl writes: > Hi Richard and all, > > [...] > >> Just to be extra, super sure, I built Emacs this afternoon from a >> checkout of the repo, and the error is *still* there, with the same >> cause. In that build, with emacs -Q, I have: >> >> (org-version) >> "9.5" >> >> (emacs-version)

Re: Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode)

On Tue, 30 Nov 2021 at 17:46, Karl Voit wrote: > > I chose an in-between approach: defining only a minimal set (name, > common structure/idea/documentation, Orgdown1, providing a > collaborative home on GitLab) and hope for a project community that > will take over (or at least support) from

Re: Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode)

Karl Voit writes: > * M ‘quintus’ Gülker wrote: >> Am Montag, dem 29. November 2021 schrieb Karl Voit: >>> It seems to be the case that the name "Orgdown" is the reason why >>> the Org-mode community does not support the idea of an >>> implementation-agnostic definition of the syntax. Which is

Re: noweb and shell heredocs

Immanuel Litzroth writes: > You can set the delimiters used for noweb code. > org-babel-noweb-wrap-end and org-babel-noweb-wrap-end. > > I think I set them to @@ in shell code. I almost always use {{{...}}} via a footer in my org-files: # Local Variables: # org-babel-noweb-wrap-start: "{{{" #

Re: noweb and shell heredocs

Hi Łukasz, One workaround that is fairly reliable is to prefix the names of the blocks to be nowebbed with an &. So #+name: block-name becomes #+name: Then you reference it as <<>> and the heredoc syntax is broken. Best, Tom

Re: [PATCH] Fix org-comment-line-break-function

Kaushal Modi writes: > On Tue, Nov 30, 2021 at 3:20 PM Marco Wahl wrote: > > diff --git a/lisp/org.el b/lisp/org.el > index 1a1375461..fdeec0d67 100644 > --- a/lisp/org.el > +++ b/lisp/org.el > @@ -19695,7 +19695,8 @@ non-nil." > (save-excursion (forward-char

Re: [PATCH] Fix org-comment-line-break-function

On Tue, Nov 30, 2021, 6:29 PM Tim Cross wrote: > > Regardless, I think that unless we understand the purpose of > insert-before-markers-and-inherit, we should make the patch such that it > still calls that function. Even if fill-prefix is nil there is > probably a good reason why the markers and

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

um, or just "assuming too much bias"? :] again i don't think you are really doing these things by just proposing a bunch of ideas about markup languages. not everybody knows all languages and you'll get substantive corrective feedback. On 11/30/21, Samuel Wales wrote: > if you will forgive

Re: Formal syntax for org-cite

Hi Timothy, Thanks for putting this together. Comments in line. Best! Tom For reference here is the tokenizer pattern I use in laundry at the moment. There are a number of issues with it ...

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

if you will forgive one more bikeshed answer, what about this? - reduced org - reduced org, version 1 and maybe - .rorg extension [if and only if needed to guarantee reduction] as for why you got bikeshed answers, maybe the subject header of this thread might have been part of it? idk. ===

Re: [PATCH] Fix regex for determining image width from attribute

Timothy writes: > What would be a more sensible interpretation in your mind? The “true” value > depends on the number of columns, and fetching that information seems a bit > unreasonable. Since this isn’t just used if nothing else if given, I see a > 120% > interpretation as fairly reasonable.

Re: Orgdown: negative feedback & attempt of a root-cause analysis

Tom Gillespie writes: > Karl, >The exact naming of a thing is nearly always the most contentious > step in trying to promulgate it. In my own field we can easily get all > parties to agree on a definition, but they refuse to budge on a name. > As others have said, I wouldn't worry about

Re: Timestamps

Jude DaShiell writes: > I think the new standard is better since it allows for work or an agenda > item to cross one or more Midnights. If so, then the Org commands should be updated to follow the standard. -- David Masterson

Re: Timestamps

Not to mention the documentation. On Tue, 30 Nov 2021, David Masterson wrote: > Jude DaShiell writes: > > > I think the new standard is better since it allows for work or an agenda > > item to cross one or more Midnights. > > If so, then the Org commands should be updated to follow the

Re: Timestamps

My mistake -- it is in the (latest?) documentation of "Plain Timestamp" under "Dates and Times". Eyes are getting old. ;-) Jude DaShiell writes: > Not to mention the documentation. > > > On Tue, 30 Nov 2021, David Masterson wrote: > >> Jude DaShiell writes: >> >> > I think the new standard

Re: Timestamps

Nicolas Goaziou writes: > Hello, > > David Masterson writes: > >> Has the format for timestamps covering (say) a few hours changed? The >> following is still possible with "C-c .", but (I think) it is not >> documented in the Org-Mode manual: >> >> <2021-11-27 Sat 10:30-12:30> >> >> This