Re: [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property]

Ignore the previous message. I see that this was about matching tags not about specifying them. Best, Tom

Re: [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property]

Without wading too far into this, why do we need escape syntax for this? The only character that might need an escape would be colon :, but my reading of the syntax doc is that colo : will immediately terminate the property, so we would update the doc to make it clear that property names cannot

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3

This is a timely discussion. I have been thinking about how to deal with prefixes defined by the #+link: keyword which is directly related to this question. I think the following might be a solution that also avoids the issue brought up by Arne. The original "bug" cannot be resolved because bare

Re: [BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

On Fri, Sep 01 2023, Lockywolf wrote: > Dear org developers, > > At the moment, ob-maxima has a straightforward way of evaluating > babel blocks, > > #+begin_src shell > maxima --very-quiet -r batchload\(\"/tmp/ob-maximaFOOBAR.mac\"\)\$ > #+end_src > > (line 87 of ob-maxima.el), > > I suggest

Re: [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property]

On 2023-08-27 09:43, Ihor Radchenko wrote: > Samuel Loury writes: > >> IMHO, "-tag&-todo=TODO" is totally ok. I even imagine we could say that >> & and | are forbidden to say anything else than AND and OR and people >> would be ok with that. > > Actually, explicit & or | might be an easier way

[BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

Re: TMiO (was: "Re: Monthy emacs-devel digest, similar to "This month in Org")

Hi Ihor, > This is actually quite an effort. AFAIK, the author had difficulties > allocating time to write more posts for TMiO. > > Also, for reference, we are talking about > Each post took several hours to do, despite how short they

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3

Ihor Radchenko writes: > "Dr. Arne Babenhauserheide" writes: > >>> Any thoughts? >> >> Thinking about the effort I’d have to fix all internal links in all >> org-documents I have (dozens of large ones and hundreds of small ones) I >> don’t like the idea of breaking internal link syntax. > >

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link?

On 2023-09-01, Ihor Radchenko wrote: > In theory, we might change the parser to treat anything like foo:bar or > or [[foo:bar]] as a link with "foo" protocol and "bar" URI. > And introduce [[::fig:something]] to allow explicit internal links. > But, despite simplifying the parser, it will

Re: [ANN] org-jami-bot

Hanno writes: > Thank you for your kind words and for suggesting to add a reference on worg! > Putting a package on ELPA is on my bucket list, so why not? ;) > > I do not have the paperwork in place yet. I recently changed employment and > am under the impression that it should not be a

Re: [PATCH] Unit-test for Please add support for dlangs packagemanager to ob-C.el

Christian Köstlin writes: > Subject: [PATCH 2/2] testing/lisp/test-ob-C.el: Add test for dub support in > ob-C.el Canceled, due to no response. See https://list.orgmode.org/orgmode/CAG741+bUT_Yt3PdLuVpMNH7vo-bb3n1iiynf2Cime1LW=21...@mail.gmail.com/ -- Ihor Radchenko // yantar92, Org mode

Re: [PATCH] Please add support for dlangs packagemanager to ob-C.el - v3

Ihor Radchenko writes: >> After adding unit-tests (following in another patchset) I found a bug in my >> last patch. >> Sorry for the noise. > > Sorry for the very late reply. > > If you are still interested, may you please document the new header > argument in etc/ORG_NEWS and update >

Re: [PATCH v2] org-faq.org: Inline comments

Max Nikulin writes: > On 08/07/2023 16:31, Ihor Radchenko wrote: - it is what we use ourselves in WORG sources. > >> Max Nikulin writes: >>> I have not found it in the worg repository. There are enough @@html:@@ >>> with a handful of @@latex:@@. >> >> Yeah, not in WORG. >>

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3

"Dr. Arne Babenhauserheide" writes: >> Any thoughts? > > Thinking about the effort I’d have to fix all internal links in all > org-documents I have (dozens of large ones and hundreds of small ones) I > don’t like the idea of breaking internal link syntax. May you elaborate about what is going

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3

Ihor Radchenko writes: > In theory, we might change the parser to treat anything like foo:bar or > or [[foo:bar]] as a link with "foo" protocol and "bar" URI. > And introduce [[::fig:something]] to allow explicit internal links. > But, despite simplifying the parser, it will certainly be a

Re: Unclear where ob-spice.el is being maintained

Bastien Guerry writes: >> We may consider tagging a new release. > > Yes, please go ahead as you see fit. I made a minor release, because apparently org-contrib 0.4 supposed to remove ob-spice.el already: https://git.sr.ht/~bzg/org-contrib/commit/c6aef31ccfc7c4418c3b51e98f7c3bd8e255f5e6

Re: Fallback fonts in LaTeX export for non latin scripts

Juan Manuel Macías writes: > ...In any > case, the fonts issue is the most delicate part. What default fonts to > add to the list? Here the user's taste or preferences would influence. Commonly available libre fonts look like a good candidate. > It must also be taken into account that if one

[DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk

Max Nikulin writes: > However I do not mind to have an easy way to delegate URI from :export > function to the link transcoder of active export backend. Just make the :export function return nil. > Current behavior with with treating link paths as fuzzy search targets > is a kind of