Re: Org markup and non-ASCII punctuation (was: org parser and priorities of inline elements)

2023-07-17 Thread Tom Gillespie
> We might probably generalize to > PRE = Zs Zl Pc Pd Ps Pi ' " > POST = Zs Zl Pc Pd Pe Pf . ; : ! ? ' " \ [ If this works I think it is reasonable. We might want to specify what to do in cases where an org implementation might not fully support unicode, and might want to do a review of related

Re: org-fontify-emphasized-text

2023-07-17 Thread Colin Baxter
> Henrik Frisk writes: > On Mon, Jul 17, 2023, 1:23 PM Ihor Radchenko wrote: >> Henrik Frisk writes: >> >>> For the first time I tried to enable the fontification of >>> emphasized text but quickly decided I didn't want it. But I >>> can't seem to get rid of it.

Re: Org markup and non-ASCII punctuation (was: org parser and priorities of inline elements)

2023-07-17 Thread Ihor Radchenko
Tom Gillespie writes: > The way I have implemented this is by maintaining an explicit list of > characters that are safe for pre markup and another for post markup. > > It is not possible to use unicode punctuation for this because there > are a variety of punctuation marks that cannot appear in

Re: Org markup and non-ASCII punctuation (was: org parser and priorities of inline elements)

2023-07-17 Thread Tom Gillespie
Hi Ihor, Thank you for looping me in. Best, Tom The way I have implemented this is by maintaining an explicit list of characters that are safe for pre markup and another for post markup. It is not possible to use unicode punctuation for this because there are a variety of punctuation marks

Re: org-fontify-emphasized-text

2023-07-17 Thread Henrik Frisk
On Mon, Jul 17, 2023, 1:23 PM Ihor Radchenko wrote: > Henrik Frisk writes: > > > For the first time I tried to enable the fontification of emphasized text > > but quickly decided I didn't want it. But I can't seem to get rid of it. > > For example, any part of a filename that is after an

[BUG] SPACE jumps to tag in header line after hidden emphasis marker [9.7-pre (release_9.6.7-562-g5b6268 @ /home/jschmidt/work/org-mode/lisp/)]

2023-07-17 Thread Jens Schmidt
[emacs-29]$ ./src/emacs -Q -L ~jschmidt/work/org-mode/lisp/ (org-version nil t) "Org mode version 9.7-pre (release_9.6.7-562-g5b6268 @ /home/jschmidt/work/org-mode/lisp/)" (setq org-hide-emphasis-markers t) t ;; assume test.org being absent in cwd C-x 4 f ;; find-file-other-window t

Re: [BUG] feature request: make org-num-mode not count headings that are COMMENTs or have an :ignore: tag [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

2023-07-17 Thread Ilja Kocken
Ah thanks for the info, I messed up by only looking at C-h f org-num-mode, and not looking at customize-group. Thank you :) On Mon, Jul 17, 2023 at 2:35 AM Ihor Radchenko wrote: > Ilja Kocken writes: > > > If I have a large org-file with many headings, sometimes it's useful to > > refer to the

Re: Doubt about error messages

2023-07-17 Thread Ihor Radchenko
Ypo writes: > Warning (org-element-cache): org-element--cache: Org parser error in > 3-recursos.org::1868222. Resetting. > ... > Should I report it in some way? Or as it didn't happen with emacs-q and > as I don't know how to reproduce it, I shouldn't bother? Thanks for reporting! Yes, the

Doubt about error messages

2023-07-17 Thread Ypo
Hi Frequently I receive this kind of messages: " Warning (org-element-cache): org-element--cache: Org parser error in 3-recursos.org::1868222. Resetting.  The error was: (wrong-type-argument integer-or-marker-p nil)  Backtrace: nil  Please report this to Org mode mailing list (M-x

Re: [BUG] WORG example for ob-lilypond is no longer working as described (was: Moving some lisp/ob-*.el files to org-contrib - your advice?)

2023-07-17 Thread Jonathan Gregory
Hi Ihor, On 14 Jul 2023, Ihor Radchenko wrote: Jonathan Gregory writes: Looks like this on my side as well. Given the feedback, I went ahead and changed the lilypond.org file: https://git.sr.ht/~bzg/worg/commit/6f69d212f41bc372426dc9b4df286638fe8f2a92 Thanks! It would be even nicer

[PATCH] Testing: Add tests for 'org-agenda-check-for-timestamp-as-reason-to-ignore-todo-item'

2023-07-17 Thread Morgan Smith
* testing/lisp/test-org-agenda.el (test-org-agenda/check-for-timestamp-as-reason-to-ignore-todo-item): New test. --- testing/lisp/test-org-agenda.el | 56 + 1 file changed, 56 insertions(+) diff --git a/testing/lisp/test-org-agenda.el

Re: [BUG] [PATCH] Avoid interaction in test ~ob-tangle/detangle-false-positive~

2023-07-17 Thread Ihor Radchenko
Evgenii Klimov writes: > While it's not applied, may I also ask: I noticed that non-default value > 'other-frame of =org-src-window-setup= variable in my init.el leads to > creation of multiple frames during interactive testing. > > I understand that testing should be done on ~emacs -Q~ etc, but

Re: [BUG] feature request: make org-num-mode not count headings that are COMMENTs or have an :ignore: tag [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

2023-07-17 Thread Ihor Radchenko
Ilja Kocken writes: > If I have a large org-file with many headings, sometimes it's useful to > refer to the heading number that people have commented on in the > exported PDF (e.g. for an academic paper). However, when I turn on > org-num-mode, this shows a continuous numbering for all the

Re: [BUG] [PATCH] Avoid interaction in test ~ob-tangle/detangle-false-positive~

2023-07-17 Thread Evgenii Klimov
Ihor Radchenko writes: > Evgenii Klimov writes: > >> Test ~ob-tangle/detangle-false-positive~ asks for confirmation to kill >> the buffer, connected to testing/examples/babel.org file, that is >> modified during the couse of the test. >> >> Way to reproduce the bug (from projects main dir): >

Re: [BUG] WORG example for ob-lilypond is no longer working as described

2023-07-17 Thread Graham King
I'm late to this thread, and I might be missing some crucial aspect of the problem, but if you just want to integrate lilypond scores and fragments into a LaTeX document, and you're able to choose to use Luatex, the lyluatex and lilyglyphs packages work beautifully with the latest Lilypond

[BUG] feature request: make org-num-mode not count headings that are COMMENTs or have an :ignore: tag [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

2023-07-17 Thread Ilja Kocken
Hi! If I have a large org-file with many headings, sometimes it's useful to refer to the heading number that people have commented on in the exported PDF (e.g. for an academic paper). However, when I turn on org-num-mode, this shows a continuous numbering for all the headlines in the file. I have

Re: [BUG] feature request: make org-num-mode not count headings that are COMMENTs or have an :ignore: tag [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

2023-07-17 Thread Ilja Kocken
I think in the above I may have forgotten that at the bottom of [[ https://github.com/japhir/ArchConfigs/blob/master/myinit.org#reset-gc-cons-threshold][my config]] I had not uncommented the line that sets the gconf-threshold :O On Thu, Jul 13, 2023 at 3:43 PM Ilja Kocken wrote: > Hi! > > If I

[PATCH worg] ob-doc-python: Use ":results file link" for returning filenames

2023-07-17 Thread ~jackkamm
From: Jack Kamm The correct usage for returng filenames as paths is to use the link header arg. This updates the ob-doc-python examples to follow this convention now. See also: https://list.orgmode.org/87ttu95xst.fsf@localhost/ --- org-contrib/babel/languages/ob-doc-python.org | 8 1

Re: Can someone dig the reasons behind emphasis regexp limitations?

2023-07-17 Thread Ihor Radchenko
Ihor Radchenko writes: > I keep looking at these rules and remain confused, even though I do > remember that Nicolas stated good reasons for this. Ok. So, it was "whatever works". https://orgmode.org/list/87mtlwt4h8@nicolasgoaziou.fr -- Ihor Radchenko // yantar92, Org mode contributor,

Org markup and non-ASCII punctuation (was: org parser and priorities of inline elements)

2023-07-17 Thread Ihor Radchenko
Max Nikulin writes: > On 21/11/2021 16:28, Ihor Radchenko wrote: >> >> Also, is there any reason why we are not simply using punctuation >> character class instead of listing punctuation chars explicitly (and >> only for English)? What about "_你叫什么名字_?" > > It seems punctuation character class

Re: [ANN] lisp/ob-tangle-sync.el

2023-07-17 Thread Mehmet Tekman
Hello again! > Ihor Radchenko writes: > > Two months have passed since the last message in this thread. > Mehmet, have you had a chance to work on this? May you need any help? General recap of where we are so far with this patch: The tangle-sync mode I wished to implement had some ambiguities

Re: org-fontify-emphasized-text

2023-07-17 Thread Ihor Radchenko
Henrik Frisk writes: > For the first time I tried to enable the fontification of emphasized text > but quickly decided I didn't want it. But I can't seem to get rid of it. > For example, any part of a filename that is after an underscore is still > printed as subtext (expected if fontification

org-fontify-emphasized-text

2023-07-17 Thread Henrik Frisk
Hi, For the first time I tried to enable the fontification of emphasized text but quickly decided I didn't want it. But I can't seem to get rid of it. For example, any part of a filename that is after an underscore is still printed as subtext (expected if fontification is on). Is there anything

Re: [BUG] org-babel-result-to-file failed when buffer is narrowed [9.7 (9.7-??-f7aa8c1 @ c:/Users/yhht/.config/emacs/.local/straight/build-29.0.60/org/)]

2023-07-17 Thread Ihor Radchenko
赵一宇 writes: > Yes you're right. > The problem exists in indirect buffer, not narrowed buffer, in which > base-directory is nil in this case. That's why I wonder if >(base-directory (and buffer-file-name > (file-name-directory base-file-name))) >

Re: [BUG] [PATCH] Avoid interaction in test ~ob-tangle/detangle-false-positive~

2023-07-17 Thread Ihor Radchenko
Evgenii Klimov writes: > Test ~ob-tangle/detangle-false-positive~ asks for confirmation to kill > the buffer, connected to testing/examples/babel.org file, that is > modified during the couse of the test. > > Way to reproduce the bug (from projects main dir): Thanks! Waiting for your copyright

Re: [DRAFT PATCH v5] Decouple LANG= and testing (was: Test failure due to LANG)

2023-07-17 Thread Ihor Radchenko
Ihor Radchenko writes: > Ruijie Yu writes: > >> Ihor Radchenko writes: >> >>> (let ((org-time-stamp-formats '("%Y-%m-%d" . "%Y-%m-%d %H:%M"))) >>> (org-element-timestamp-interpreter timestamp nil)) >> >> Thanks for the pointer. I have made this into a macro and redid my >> changes