Re: [ANN] An Org parser for Julia

On Thursday, 2 Dec 2021 at 22:04, Timothy wrote: > It worked all the time, except when I tried to `@benchmark' it, where > strange errors that shouldn’t happen cropped up. automated benchmarking multi-threaded applications is a form of dark magic... -- : Eric S Fraga, with org

Re: Unwanted italics formatting between two URLs

On 29/11/2021 14:03, Rafael Laboissière wrote: [[https://first/-/url/][pre]] text [[https://second-url/?][post]] Fortunately this sample is parsed and exported correctly: https://first/-/url/;>pre text href="https://second-url/?;>post so it is only issue with regexp-based fontification.

Re: Org-syntax: Intra-word markup

Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, December 2nd, 2021 at 4:24 PM, Robert Pluim wrote: >> autofrettage> any kind of rower = Ruder*in > > But with the 'female' suffix? Thatʼs almost as bad as 'écriture > inclusive'. Surely 'Ruder**'?  The

Re: Some commentary on the Org Syntax document

Hi Tom, Thanks for your comments, they've been most helpful. I have some comments on your comments, and have also started drafting some tweaks to the document in light of your initial comments, put as a diff excerpt at the end of this email. For starters, I have come more general comments.

Re: Org-syntax: Intra-word markup

Hi Nicolas and all, Nicolas Goaziou writes: > I find zero-with spaces solution much more elegant. It also doesn't > change current syntax, which is a big advantage. I agree that zero width spaces work fine as a solution, but I think they should not be understood as part of the syntax but as a

Re: Org-syntax: Intra-word markup

a silly question. don't we already use something kinda similar to \emph{what}ever for all backends? could we do so? On 12/2/21, Denis Maier wrote: > Am 02.12.2021 um 19:11 schrieb Tom Gillespie: >> I don't mean to be a wet blanket, but the edge cases for >> the current markup syntax are

Re: Org-syntax: Intra-word markup

Tom Gillespie writes: > I don't mean to be a wet blanket, but the edge cases for > the current markup syntax are already hard enough to > implement correctly, to the point where different parts of > Org mode are inconsistent. Intra-word markup isn't viable > because there simply isn't any sane

Re: Org-syntax: Intra-word markup

Am 02.12.2021 um 19:11 schrieb Tom Gillespie: I don't mean to be a wet blanket, but the edge cases for the current markup syntax are already hard enough to implement correctly, to the point where different parts of Org mode are inconsistent. Intra-word markup isn't viable because there simply

Re: Org-syntax: Intra-word markup

On 02/12/2021 20:07, Ihor Radchenko wrote: As for suggestions: If just using /intra/word creates ambiguities, what about the asciidoc solution? So //intra//word? I do like this idea. - Some //text surprise// - ++another ~i++~ problem++ First wins...

Re: examples for org-manual

Thank you very much for your message and the link. Does Org format produce the .texi format for TexInfo ?  I found the official reply here: https://orgmode.org/manual/Texinfo-export-commands.html Org format seams to be a top layer format to produce others formats. That seams to be a good reason

Re: Some commentary on the Org Syntax document

Hi Timothy, Replies in line. Best! Tom On Thu, Dec 2, 2021 at 1:32 AM Timothy wrote: > > Hi All (& Nicolas in particular again), > > With my recent efforts to write a parser based on > , I’ve developed a few thoughts > on > that document.

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

On 02/12/2021 08:48, Ihor Radchenko wrote: Max Nikulin writes: Well... I added yet another exception on main. Note that this special case is also just in older Emacs versions. Ihor, have you pushed the change? I still can reproduce the issue with Emacs-26.3 Oops. I fixed Emacs 27, but

Re: citeproc-org and org-ref 3

Glad to hear it is working again for you! Best wishes, Joseph Vidal-Rosset writes: > Dear all, > > > I just succeeded in solving my problem. > > l-210-235 of myblogexporter.el, I changed the code for: > > (defun org-export-head-export-headers (directory-name backend) >"Exports each heading

Re: Faces for inline src blocks

Hi Eric, > I am not very picky (yeah, well, okay, maybe a little ). All I really > care about is not having other faces, that have well defined meanings, > being used. I would actually be happy with just the whole block having > a face but maybe others, including yourself, would like to

Re: Faces for inline src blocks

On Thursday, 2 Dec 2021 at 23:56, Timothy wrote: > [...] but something like 6 faces for inline source blocks just feels > excessive to me. Why? It's just a number. I cannot imagine it would have any performance impact? If you think that level of granularity is useful, I suggest you go for

Re: Org-syntax: Intra-word markup

I don't mean to be a wet blanket, but the edge cases for the current markup syntax are already hard enough to implement correctly, to the point where different parts of Org mode are inconsistent. Intra-word markup isn't viable because there simply isn't any sane way to parse something like *hello

Re: Faces for inline src blocks

On Thursday, 2 Dec 2021 at 21:57, Timothy wrote: > Let me know what your thoughts are. I am not very picky (yeah, well, okay, maybe a little ). All I really care about is not having other faces, that have well defined meanings, being used. I would actually be happy with just the whole block

Re: Bibliographies on export with ox-context and ox-epub

There is a ConTeXt-specific citation exporter that's in development: https://github.com/Jason-S-Ross/oc-context On 12/2/21 12:11 AM, juh wrote: Am 01.12.21 um 16:01 schrieb Eric S Fraga: What completion engine are you using?  In selectrum, typing C-j at that point finishes the completion. 

Re: citeproc-org and org-ref 3

Dear all, I just succeeded in solving my problem. l-210-235 of myblogexporter.el, I changed the code for: (defun org-export-head-export-headers (directory-name backend) "Exports each heading to directory-name using backend" (if (equal backend "html")

Re: examples for org-manual

On Thu, Dec 2, 2021, 8:08 AM Vincent Breton wrote: > Hi, > > > Emacs and Emacs Org documentation, and lot of others GNU products use > Texinfo to generate their own documentation to different formats. The Org mode documentation switched to Org format few years back:

Re: Org-syntax: Intra-word markup

> On Thu, 02 Dec 2021 13:36:48 +, autofrettage > said: autofrettage> Someone brought up edge and corner cases, so I simply have to mention the German gender stars ("Gendersternchen"). autofrettage> In an effort to make German gender neutral, some individuals use '*' in the

Re: Org-syntax: Intra-word markup

Hello, Ihor Radchenko writes: > Denis Maier writes: > >> As for suggestions: If just using /intra/word creates ambiguities, what >> about the asciidoc solution? So //intra//word? > > I do like this idea. > > Though I would also like to hear Nicolas' opinion. I sympathize to the idea of

Re: Org-syntax: Intra-word markup

Nicolas Goaziou writes: > I'm suggesting to remove zero-width spaces contiguous to emphasis > markers only. Therefore LaTeX process would npot see them. Other zero > width spaces, e.g., inserted by user, are kept. AFAICT, the two last > points you mention are not relevant with my proposal. > >

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

Timothy writes: > Thanks for your thoughtful deliberation on this. No worries, and thanks for continuing to engage with it. >> The other consideration is if we take the first point as a given (that >> org should use width directives for other backends), should it also >> attempt to interpret

Re: Patch to align baseline of latex fragments and surrounding text

Timothy, looping you in on this. I feel that maybe it would be useful to attach screenshots to show the improvement from this patch? Anyway, I've attached two images: one with the correct baseline alignment to surrounding text and the other with the current, incorrect, baseline alignment. I

Re: Org-syntax: Intra-word markup

Hello, Juan Manuel Macías writes: > I agree that zero width spaces work fine as a solution, but I think they > should not be understood as part of the syntax but as a punctual > (temporal?) remedy to certain scenarios. As mentioned before, in LaTeX > zero width spaces can produce unexpected

Re: ox-extra ignore-headlines mismatching/unexpected behavior

Em sex, 2020-09-04 às 19:40 +0200, Bastien escreveu: > Hi Alexandre, > > Alexandre Jesus writes: > > > I am getting some unexpected and/or mismatching (between pdf and html > > exports) behavior with ox-extra ignore-headlines. The weird behaviors > > I > > am getting are: > > thanks for

Re: [PATCH] Fix behavior of lambda default header arg vars

Matt Huszagh writes: > Hey Timothy, > > Any thoughts on this bug fix? > > Thanks > Matt Apologies, meant to include the org-mode mailing list in this too. Thanks Matt

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

Max Nikulin writes: > Unfortunately currently it fails in Emacs-26.3 event without "#+startup: > indent": > > Warning (org-element-cache): org-element--cache: Unregistered buffer > modifications detected. Resetting. > If this warning appears regularly, please report it to Org mode mailing >

Some commentary on the Org Syntax document

Hi All (& Nicolas in particular again), With my recent efforts to write a parser based on , I’ve developed a few thoughts on that document. Hopefully, they can lead to some improvements and clarifications.

Re: [PATCH] Fix ob-plantuml over TRAMP

Hi Guillaume, Thanks for picking this up and submitting a patch. Have you considered using `tramp-handle-file-exists-p'? I’m not overly familiar with tramp or this sort of issue, but it looks like it could be exactly what we want. > My Emacs Workflow involves connecting to a dev server over

org-element-cache warning even when off

Hello, I have #+begin_src emacs-lisp (setq org-element-use-cache nil) (setq org-element-cache-persistent nil) #+end_src Yet when editing by hand a time string in a today habit I get the warning: --8<---cut here---start->8--- Warning (org-element-cache):

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

Karl, thanks for all of this, and for writing and posting your blog entry (words of caution for many). my thoughts on your project are something like this: - i think non-emacs tools to deal with org mode files is a Good Thing. - for me, the main motivation is to allow *me* to share an org mode

Re: Bibliographies on export with ox-context and ox-epub

Am 01.12.21 um 16:01 schrieb Eric S Fraga: What completion engine are you using? In selectrum, typing C-j at that point finishes the completion. Other engines will differ. You might also try up-arrow and RET. Thanks a lot. I use selectrum and would've never found this door out. juh

[ANN] An Org parser for Julia

Hi Everyone, I’ve gone heavily into Julia over the past year, and I recently thought it would be nice if an Org parser existed for it — so I made one! It’s just over a week since I started, so it’s fairly young, but I’m pretty happy with the way it’s

Re: [PATCH] ob-shell-test, test-ob-shell and introduction

Hi Matt, > > [FSF copyright assignment]. Have you done that yet? > > I just verified with my employer that my contract grants an exception for this > project. Just emailed the request to ass...@gnu.org. Also, got access from > Bastien for worg. I figure it’s probably best to reserve any more

Org-syntax: Intra-word markup

Hi everyone, while we're at discussing org syntax anyway, I thought it's time to bring up another syntax question: Currently, org syntax doesn't officially seem to support intra-word emphasis. Am I missing something? If the assessment is correct: Is there a reason for this? And, shouldn't

Re: Org babel Python and R, table not transformed when :var is called ?

Hi, I found a solution using *Wrapping*, adding a #+NAME to #+RESULTS block resolve the problem. This is not defined / described into the doc, and actually i found this process a little anti-intuitive. #+RESULTS has already a name, resulting/linked from/to the execution of mypythoncode ...

Re: [ANN] An Org parser for Julia

Timothy writes: > I’ve actually had a brief look at my performance using my Emacs config file > (which is ~10k lines). On this, my parser is about ~5x faster than > org-element. > On a smaller file like the project’s readme it’s closer to ~10x faster. I’ve > also noticed that I can multithread

Re: org-element-cache warning even when off

> Ihor Radchenko writes: > Colin Baxter  writes: >> I do not have an org-persist cache present. So I wonder where is >> the cache that I am supposedly corrupting. > That warning is shown when org-element--parse-to throws an error > (the parser fails). Apparently, there

Re: org-element-cache warning even when off

Colin Baxter  writes: > I have done this but now do not see any warning. Further, I now don't > seem to be able to re-produce the issue at all. It could that the > original warning was spurious and reflected some stale state. I did have > multiple emacsen open at the time. Note that I fixed

Re: Org-syntax: Intra-word markup

Hi Denis and Ihor, Ihor Radchenko writes: > Denis Maier writes: > >> Currently, org syntax doesn't officially seem to support intra-word >> emphasis. Am I missing something? > > intra-*word* works just fine for me. > > Best, > Ihor I think what Denis is referring to is a construction of the

Re: Org-syntax: Intra-word markup

Hi! >>> Currently, org syntax doesn't officially seem to support intra-word >>> emphasis. Am I missing something? >> >> intra-*word* works just fine for me. >> >> Best, >> Ihor > > I think what Denis is referring to is a construction of the type > *intra*word, which, if I'm not mistaken, is not

Re: Org-syntax: Intra-word markup

Am 02.12.2021 um 12:42 schrieb Marco Wahl: Hi! Currently, org syntax doesn't officially seem to support intra-word emphasis. Am I missing something? intra-*word* works just fine for me. Best, Ihor I think what Denis is referring to is a construction of the type *intra*word, which, if I'm

Re: [ANN] An Org parser for Julia

Hi Ihor, > Just FYI that I am getting similar results on your config.org: > [snip] Thanks. It’s always nice to see a confirmation of a result. Hopefully in the near future we’ll be able to run your files through without issue . All the best, Timothy

Re: [ANN] An Org parser for Julia

Timothy writes: > I’ve gone heavily into Julia over the past year, and I recently > thought it would be nice if an Org parser existed for it — so I made one! > > > I am wondering how the third-party parsers are going to scale for larger Org files. I did

Re: [ANN] An Org parser for Julia

Hi Ihor, > I am wondering how the third-party parsers are going to scale for larger > Org files. I did some simple testing in the past, and it seems that only > tree-sitter can potentially get sufficiently close to org-element in > terms of performance. I’ve actually had a brief look at my

Re: Org-syntax: Intra-word markup

Denis Maier writes: > Currently, org syntax doesn't officially seem to support intra-word > emphasis. Am I missing something? intra-*word* works just fine for me. Best, Ihor

Re: Org-syntax: Intra-word markup

Juan Manuel Macías writes: >> intra-*word* works just fine for me. >> > I think what Denis is referring to is a construction of the type > *intra*word, which, if I'm not mistaken, is not supported and can only > be achieved by inserting a zero width space. I see. We had a discussion about

Re: Org-syntax: Intra-word markup

Marco Wahl writes: > Is there a recommended way to insert a zero with space? C-x 8

Re: [ANN] An Org parser for Julia

Timothy writes: > │ julia> @benchmark parse(Org, config) > │ BenchmarkTools.Trial: 139 samples with 1 evaluation. > │ Range (min … max): 34.042 ms … 43.269 ms ┊ GC (min … max): 0.00% … 16.10% > │ Time (median): 34.857 ms ┊ GC (median):0.00% > │ Time (mean ± σ):

Re: Org-syntax: Intra-word markup

Denis Maier writes: > > Just a furter remark: while zero-width-spaces can be used as a > workaround, they may create problems in some export formats. E.g., they > will mess up hyphenation in latex. I think if read somewhere that those > can be removed with hooks or filters, but I think that

Re: Formal syntax for org-cite

Hi Nicolas, Tom, I just thought I’d do a little test to see what markup citations accept with org-element, and I’m not quite sure what to make of the results. I’d appreciate hearing your thoughts on the example below. Let’s look at a strange citation. ┌ │ [cite: @key *bold* text @@org:hey@@

Re: [ANN] An Org parser for Julia

Timothy, this is really good to see! I have been using Julia as my main programming language for some years now and all of my codes generate output with org markup. Now I could in principle use it for the input as well which could be quite helpful. As an aside, Julia 1.7 was released two or

Re: org-element-cache warning even when off

Colin Baxter  writes: > I do not have an org-persist cache present. So I wonder where is the > cache that I am supposedly corrupting. That warning is shown when org-element--parse-to throws an error (the parser fails). Apparently, there is some problem with Org parser. > Warning

Re: [ANN] An Org parser for Julia

Hi Ihor, > I am wondering how you did the benchmark. > I just tried the following on my config.org > (): > > The config.org is about 18k lines, but I did not manage to wait enough > for the parser to return. Hmm, I just tried yours and I think something

Re: Org-syntax: Intra-word markup

Yes, Juan Manuel. That's it. See for reference: https://stackoverflow.com/questions/1218238/how-to-make-part-of-a-word-bold-in-org-mode Best, Denis Am 02.12.2021 um 12:30 schrieb Juan Manuel Macías: Hi Denis and Ihor, Ihor Radchenko writes: Denis Maier writes: Currently, org syntax

Re: Org-syntax: Intra-word markup

Denis Maier writes: > Yes, Juan Manuel. That's it. > > See for reference: > https://stackoverflow.com/questions/1218238/how-to-make-part-of-a-word-bold-in-org-mode Please, do not use that stackoverflow answer. It is not officially supported, breaks exporting, and will not work anymore in

Re: Org-syntax: Intra-word markup

Hi Denis, > Currently, org syntax doesn’t officially seem to support intra-word emphasis. > Am > I missing something? I’d describe it as supported via-zero width spaces. You may be interested in . > If the assessment is

Re: Org-syntax: Intra-word markup

Hi Timothy, Am 02.12.2021 um 12:58 schrieb Timothy: Hi Denis, Currently, org syntax doesn’t officially seem to support intra-word emphasis. Am I missing something? I’d describe it as supported via-zero width spaces. You may be interested in

Re: Org-syntax: Intra-word markup

Am 02.12.2021 um 13:10 schrieb Ihor Radchenko: Denis Maier writes: Just a furter remark: while zero-width-spaces can be used as a workaround, they may create problems in some export formats. E.g., they will mess up hyphenation in latex. I think if read somewhere that those can be removed

Re: Formal syntax for org-cite

Hi Ihor, > This is all defined in org-element-object-restrictions together with > other restrictions on what kinds of objects can be placed inside other > elements and objects: > > (minimal-set ’(bold code entity italic latex-fragment strike-through >subscript

Re: Org-syntax: Intra-word markup

Denis Maier writes: > As for suggestions: If just using /intra/word creates ambiguities, what > about the asciidoc solution? So //intra//word? I do like this idea. Though I would also like to hear Nicolas' opinion. Best, Ihor

Re: examples for org-manual

Hi, Emacs and Emacs Org documentation, and lot of others GNU products use Texinfo to generate their own  documentation to different formats. Unlucky, they are just the HTML version on https://www.gnu.org/software/emacs/manual/org.html and It is not for lack of having written the 22 november 2021

Re: Org-syntax: Intra-word markup

Ihor Radchenko writes: > Denis Maier writes: > >>> Can you create an example of such scenario and post it as a bug? >>> Probably, we just need to strip all zero-width spaces at the basic ox.el >>> level. >> To be clear: That's not an org bug. It's just that latex won't be able >> such a word.

Re: citeproc-org and org-ref 3

Dear John (cc. Ivan), First, thanks for your help and for your patience, that's very kind of you. The good news is that indeed, org-ref 3 exports nicely the html bibliography with my CSL file, it works well with your org file and your bibliography. My error was simple: I did not use the

Re: Org-syntax: Intra-word markup

Someone brought up edge and corner cases, so I simply have to mention the German gender stars ("Gendersternchen"). In an effort to make German gender neutral, some individuals use '*' in the midst of some words, e.g. rower. Ordinary German: male rower = Ruderer female rower = Ruderin Gender

Re: Org-syntax: Intra-word markup

Am 02.12.2021 um 13:08 schrieb Eric S Fraga: My solution, in these case, is to fall back to LaTeX using @@latex:...@@ (and equivalent for HTML, if desired). Not pretty but I need this so seldom that I am happy with the org emphasis support generally. Hi Eric, Am 02.12.2021 um 13:08

Re: Org-syntax: Intra-word markup

Am 02.12.2021 um 13:00 schrieb Ihor Radchenko: Juan Manuel Macías writes: intra-*word* works just fine for me. I think what Denis is referring to is a construction of the type *intra*word, which, if I'm not mistaken, is not supported and can only be achieved by inserting a zero width

Re: Org-syntax: Intra-word markup

On 02/12/2021 19:10, Ihor Radchenko wrote: Denis Maier writes: Just a furter remark: while zero-width-spaces can be used as a workaround, they may create problems in some export formats. E.g., they will mess up hyphenation in latex. I think if read somewhere that those can be removed with

Re: Formal syntax for org-cite

Timothy writes: > Let’s look at a strange citation. > > ┌ > │ [cite: @key *bold* text @@org:hey@@ and /italic/ and {{{macro()}}} and > [fn:3] and > │ <> <2021-12-02 Thu> \latex and \alpha and a statscookie [3/7] > src_lang{hi} > │ s^{up} and s_{ub}] > └ > > Examining the interpretation

Re: Org-syntax: Intra-word markup

Denis Maier writes: >> Can you create an example of such scenario and post it as a bug? >> Probably, we just need to strip all zero-width spaces at the basic ox.el >> level. > To be clear: That's not an org bug. It's just that latex won't be able > such a word. If | is a zero width space, the

Re: [PATCH] Fontification for inline src blocks

Timothy, I am happy to see the fontification of inline src blocks in org. Thank you! However, I am finding the result not very pleasing unfortunately. Specifically, I am not happy with the use of other pre-existing faces (shadow and org-meta-line) for this purpose. These other faces have their

Re: Org-syntax: Intra-word markup

Denis Maier writes: >> An alternative may be some kind of "forced" emphasis syntax where Org >> does not have to guess about the emphasis using non-transparent rules. >> But it's what zero width space is for and it is what we recommend in the >> Org manual. > As for the forced syntax. What do

Re: Org-syntax: Intra-word markup

On Thursday, 2 Dec 2021 at 13:27, Denis Maier wrote: > This works if your target is just latex, but not if you have multiple > targets, right? Multiple targets are possible: @@latex:\textbf{html:@@intra@@latex:}html:@@word. Just very ugly! 藍 Of course, if you do this more than once, a

Re: Org-syntax: Intra-word markup

Am 02.12.2021 um 14:14 schrieb Juan Manuel Macías: Ihor Radchenko writes: Denis Maier writes: Can you create an example of such scenario and post it as a bug? Probably, we just need to strip all zero-width spaces at the basic ox.el level. To be clear: That's not an org bug. It's just that

Faces for inline src blocks (was: [PATCH] Fontification for inline src blocks)

Hi Eric, > However, I am finding the result not very pleasing unfortunately. > Specifically, I am not happy with the use of other pre-existing faces > (shadow and org-meta-line) for this purpose. These other faces have > their specific uses and the resulting combination for inline src blocks, >

Re: [ANN] An Org parser for Julia

Hi Eric, > As an aside, Julia 1.7 was released two or three days ago. Works very > well. None of my codes has broken, which is always a good sign. Funny you should mention 1.7, I tried multithreading the parser and achieved a ~10x speedup. It worked all the time, except when I tried to