Re: Seemingly inconsistent whitespace ownership

2023-08-11 Thread Tom Alexander
On August 11, 2023 5:20:08 AM EDT, Ihor Radchenko wrote: >"Tom Alexander" writes: > >> The org-mode documentation states: "With the exception of list items, blank >> lines belong to the preceding element with the narrowest possible scope. For >> example, if at the end of a section we have a

Re: Or probably just fix the org-ctags hook functions?

2023-08-11 Thread Jens Schmidt
On 2023-08-11 23:48, Ihor Radchenko wrote: - If you run into this issue, the real pain is to understand what's going on, since org-ctags might get loaded in surprising ways. So probably we should make that easier. The quick fix is unsetting `help-enable-completion-autoload'.

Re: Or probably just fix the org-ctags hook functions?

2023-08-11 Thread Ihor Radchenko
Jens Schmidt writes: > - If you run into this issue, the real pain is to understand what's >going on, since org-ctags might get loaded in surprising ways. So >probably we should make that easier. The quick fix is unsetting `help-enable-completion-autoload'. And I do not think that we

Re: Or probably just fix the org-ctags hook functions?

2023-08-11 Thread Jens Schmidt
On 2023-08-11 19:01, Nick Dokos wrote: Sure, but we should not reject Jens' proposal just because of this argument. We can use the suggestions to improve org-ctags itself, after it is explicitly loaded. Absolutely. My disagreement was only with the part that I quoted, in particular the

Re: [patch] ox-latex.el: fix blank lines behavior in verse block

2023-08-11 Thread Juan Manuel Macías
Ihor Radchenko writes: > Juan Manuel Macías writes: > >> ... In any case, the fact that the verse block can also be used to >> literally export line breaks and horizontal/vertical spaces is >> interesting. Something occurred to me that I don't know if it's a bit >> foolhardy: how about a LaTeX

Re: Or probably just fix the org-ctags hook functions?

2023-08-11 Thread Nick Dokos
Ihor Radchenko writes: > Nick Dokos writes: > >>> ... >>> Probably the problem is not the side-effects done by loading >>> =org-ctags=, but rather that these hook function from =org-ctags= try >>> to do their job when the environment is not really ready for them, >>> i.e. when there is no known

Re: [SUMMARY] [[bbb:OrgMeetup]] on Wed, Aug 9, 19:00 UTC+3 (was: Interest in an Org video meetup?)

2023-08-11 Thread William Denton
On 10 August 2023, Ihor Radchenko wrote: Thanks everyone who participated! We had quite a few people by Emacs meetup standards. Thanks for organizing this! It was a good session, and I picked up a few tips and things to try out. Seeing the Arabic dissertation was a highlight. It was also

Re: [PATCH] org-macs.el: Fix Emacs-26 compatibility

2023-08-11 Thread Ihor Radchenko
Max Nikulin writes: > Current state of the main branch is not compatible with Emacs-26. > > Loading /home/ubuntu/src/org-mode/lisp/org-compat.el (source)... > Eager macro-expansion failure: (wrong-number-of-arguments (2 . 2) 6) > > It is again `setq-local' call with multiple variables. See the

[PATCH] org-macs.el: Fix Emacs-26 compatibility

2023-08-11 Thread Max Nikulin
Current state of the main branch is not compatible with Emacs-26. Loading /home/ubuntu/src/org-mode/lisp/org-compat.el (source)... Eager macro-expansion failure: (wrong-number-of-arguments (2 . 2) 6) It is again `setq-local' call with multiple variables. See the attached patch that splits it

[BUG][SECURITY] ob-sqlite header args allows execution of arbitrary shell commands

2023-08-11 Thread Max Nikulin
Consider the following Org file 8< #+begin_src elisp :results none (require 'ob-sqlite) #+end_src #+begin_src sqlite :db /tmp/ob.sqlite$(date >/tmp/ob-sqlite-vuln.log) select 1 #+end_src >8 Executing of the sqlite code block causes creation of the

Re: Concerning previews of LaTeX snippets

2023-08-11 Thread Ihor Radchenko
Divya writes: > Whenever I try to do `C-x C-c C-l`, I get the following error: > > `org-compile-file: File "/tmp/orgtexEMteNn.svg" wasn't produced Please > adjust 'dvisvgm' part of 'org-preview-latex-process-alist'` > > And following this, I have tried to tweak the value of the variable, but >

Re: [SUMMARY] [[bbb:OrgMeetup]] on Wed, Aug 9, 19:00 UTC+3 (was: Interest in an Org video meetup?)

2023-08-11 Thread Ihor Radchenko
Carlo Tambuatco writes: > Was unable to attend due to a power outage. Is this going to be a > monthly/semi monthly meetup? Is the next one scheduled already? Not scheduled yet. I am tentatively thinking about the second Wednesday of September (Wed, Sep 13). Another idea is to have the meetup

Re: [patch] ox-latex.el: fix blank lines behavior in verse block

2023-08-11 Thread Ihor Radchenko
Juan Manuel Macías writes: > ... In any case, the fact that the verse block can also be used to > literally export line breaks and horizontal/vertical spaces is > interesting. Something occurred to me that I don't know if it's a bit > foolhardy: how about a LaTeX attribute ':literal t'? If used,

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

2023-08-11 Thread Ihor Radchenko
Bastien Guerry writes: >> Finally, we have org-mouse.el discussed here, which modifies key >> bindings and org-inlinetask.el, which modifies how Org treats headlines >> in Org files, modifying syntax. > > org-mouse.el should not modify default Org _editing_ key bindings. > Is it really the case?

Re: [PATCH] Re: what is the purpose of "This link has already been stored"?

2023-08-11 Thread Ihor Radchenko
Bastien Guerry writes: > (1) by always store the latest link on top and remove old dups. > > (2) always store latest link at the top and remove old dups and allow > to keep dups with 3 universal prefix args. > ... > I'm in favor of option (2) as it deals with the above use-case, and >

Re: Feature request: adjust ~org-agenda-format-item~ to let the user choose the first level included in breadcrumbs

2023-08-11 Thread Ihor Radchenko
"M. Pger" writes: > I understand better, thanks. Would be a good opportunity for me to (try to) > contribute; this weekend I will check carefully the link you've sent. I'll > keep you posted, your assistance would be more than welcome :) It has been a month since the last message in this

Re: Seemingly inconsistent whitespace ownership

2023-08-11 Thread Ihor Radchenko
"Tom Alexander" writes: > The org-mode documentation states: "With the exception of list items, blank > lines belong to the preceding element with the narrowest possible scope. For > example, if at the end of a section we have a paragraph and a blank line, > that blank line is considered part

Re: Passing table to Ruby session

2023-08-11 Thread Ihor Radchenko
Mike Gauland writes: > I've reported it to the inf-ruby project: > https://github.com/nonsequitur/inf-ruby/issues/172 > > I wasn't aware that Emacs would insert EOF in a stream, but that doesn't > seem to be the problem (if it is even occurring here). AFAIK, it has nothing to do with Emacs

Re: Or probably just fix the org-ctags hook functions?

2023-08-11 Thread Ihor Radchenko
Nick Dokos writes: >> ... >> Probably the problem is not the side-effects done by loading >> =org-ctags=, but rather that these hook function from =org-ctags= try >> to do their job when the environment is not really ready for them, >> i.e. when there is no known tag file around. >> ... > > I

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

2023-08-11 Thread Ihor Radchenko
Nick Dokos writes: > I would also recommend that the library *not* call its enable function > in general and leave it to the user to do so explicitly, but that may > be more controversial for "backward compatibility" reasons (with which > I disagree in these particular cases: I view them as bugs

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-08-11 Thread Ihor Radchenko
Jonathan Gregory writes: >> Jonathan, do you think that your original patch is still what >> you want to get merged? > > Yes, the one I sent on 20 Jul 2023. I haven't had any issues with > it so far. Ok. Would you mind adding a commit message, as described in