Re: [O] [ANN] Changes to link syntax

Nicolas Goaziou writes: > Hello, > > I finally pushed changed about escape syntax in bracket links. Here is > the excerpt from ORG-NEWS: > > Org used to percent-encode sensitive characters in the URI part of the > bracket links. > > Now, escaping mechanism uses the usual backslash

Re: [O] [PATCH 2/2] test-ob-emacs-lisp: Test :lexical src block header argument

Sebastian Miele writes: > After some initial tooth-grinding, My intent is not to be negative. I do understand that writing tests takes time. However, from experience, having to fix a regression when your only indication comes from a test you do not fully understand is a pain. To see what I

[O] Timestamps: overnight repeater possible?

Hi subscribers, can multiday timestamp ranges be made repeatable? Case in point: I'd like to create the timestamp(s) for an "after-hour" time span ranging from 18:00 in the evening til the following morning 10:00, repeated every day. I tried these: * Overnighter (listed for 2000-01-03 and -04

Re: [O] [PATCH 2/2] test-ob-emacs-lisp: Test :lexical src block header argument

Nicolas Goaziou writes: > [...] > > > However, your tests are very convoluted. It is better than no test, but > if, unfortunately, one of them fail in some distant future, it may take > more time understanding what happens in the test than actually fixing > the bug. > > Would you mind rewriting

Re: [O] org-clock-rounding-minutes -- non-zero value can cause double clocking

Hello, Raymond Zeitler writes: > There is a problem when org-clock-rounding-minutes is non-zero, say > N.  The problem is that the clockin-time of a task can be N less than > the clockout-time of the previous task at certain times.  Thus, clock > reports can show an extra N minutes total time

Re: [O] org-lint reports non-existent file for html links

Hello, Dominik Schrempf writes: > I have the following in-buffer variable set: > > #+SETUPFILE: https://path/to/some/setupfile.setup > > Org lint reports > > 17 low Non-existent setup file "https://path/to/some/seutpfile.setup > > This is true, but also not very relevant. Fixed. Thank you.

Re: [O] org-sbe: error when passing strings as parameters to/from Python blocks

* Karl Voit wrote: > > * Daniel Herzig wrote: >> Karl Voit writes: >> >> After some trying I found that the variables as set in the source-code >> header need standard values set: >> >> #+NAME: classificationfm >> #+BEGIN_SRC python :var prob="high" :var impact="high" >> if prob == "high" and

Re: [O] [PATCH 2/2] test-ob-emacs-lisp: Test :lexical src block header argument

Hello, Sebastian Miele writes: > * testing/lisp/test-ob-emacs-lisp.el > (test-ob-emacs-lisp-dynamic-lexical-text, > test-ob-emacs-lisp-dynamic-lexical-expr, > ob-emacs-lisp/dynamic-lexical-execute, > ob-emacs-lisp/dynamic-lexical-edit): Add tests that check the > correct handling of

Re: [O] [PATCH 1/2] ob-emacs-lisp: Set `lexical-binding' in edit buffers

Hello, Sebastian Miele writes: > * lisp/ob-emacs-lisp.el (org-babel-execute:emacs-lisp, > org-babel-emacs-lisp-lexical): Factor out the conversion of the > :lexical source block argument to a form that is appropriate for > `lexical-binding' and the LEXICAL argument to `eval'. > > *

Re: [O] [bug] org-sbe: error when passing strings as parameters to/from Python blocks

Hi Daniel, * Daniel Herzig wrote: > Karl Voit writes: > > After some trying I found that the variables as set in the source-code > header need standard values set: > > #+NAME: classificationfm > #+BEGIN_SRC python :var prob="high" :var impact="high" > if prob == "high" and impact == "high": >

Re: [O] org-sbe: error when passing strings as parameters to/from Python blocks

Karl Voit writes: > Hi! Hi! > > I want to test/use Python with org-sbe: > > #+NAME: classificationfm > #+BEGIN_SRC python :exports none :var prob :var impact > > result = "" > if prob == 'high' and impact == 'high': > return 'A' > if prob == 'low' and impact == 'high': > return 'B' > if

[O] [PATCH 1/2] ob-emacs-lisp: Set `lexical-binding' in edit buffers

* lisp/ob-emacs-lisp.el (org-babel-execute:emacs-lisp, org-babel-emacs-lisp-lexical): Factor out the conversion of the :lexical source block argument to a form that is appropriate for `lexical-binding' and the LEXICAL argument to `eval'. * lisp/ob-emacs-lisp.el

[O] [PATCH 2/2] test-ob-emacs-lisp: Test :lexical src block header argument

* testing/lisp/test-ob-emacs-lisp.el (test-ob-emacs-lisp-dynamic-lexical-text, test-ob-emacs-lisp-dynamic-lexical-expr, ob-emacs-lisp/dynamic-lexical-execute, ob-emacs-lisp/dynamic-lexical-edit): Add tests that check the correct handling of the :lexical header argument when executing

[O] org-sbe: error when passing strings as parameters to/from Python blocks

Hi! I want to test/use Python with org-sbe: #+NAME: classificationfm #+BEGIN_SRC python :exports none :var prob :var impact result = "" if prob == 'high' and impact == 'high': return 'A' if prob == 'low' and impact == 'high': return 'B' if prob == 'high' and impact == 'low': return

[O] excluding lines from the export to latex

Hello, I meet a small problem that org-mode or lisp code could probably solve, but again I need help. Here is my question. In my gnus setup, via selecting identity, I get the following sample: #+BEGIN_SRC emacs-lisp From: Joseph Vidal-Rosset To: Subject: Gcc: