Re: [PATCH 0/2] Don't print arguments of post-process arguments to stdout

[Ihor Radchenko]

Jonas Bernoulli  writes:

> I run org-babel-execute-buffer from a Makefile and the output is quite
> noisy, forcing me to filter out some output using grep -v so that I am
> still able to spot any unexpected output that indicates some issue.
>
> Now that I have started using post-processing code blocks, the output
> has gotten even more noisy and unfortunately filtering out the unwanted
> additions is not possible.
>
> Currently all arguments to post-processing blocks are printed to
> stdout.  I am not able to filter them out using grep because this
> output seems to be split across multiple lines, so a regexp like
> "^(" only matches parts of the noise.
>
> It is unclear whether the arguments were printed on purpose.  It might
> be useful to do so at times for debugging purposes, but generally they
> make things harder, by obscuring output one would want to notice.

I suspect that it is remnants of previous code re-factoring in
5e0db0798. The old code used `print' for pretty-printing :results pp.

> The second commit addresses a cosmetic, but somewhat related,
> annoyance.
>
> Jonas Bernoulli (2):
>   Don't print arguments of post-process arguments to stdout
>   Begin messages about executing code blocks with a capital letter
>
>  lisp/ob-awk.el| 2 +-
>  lisp/ob-core.el   | 2 +-
>  lisp/ob-emacs-lisp.el | 2 +-
>  lisp/ob-groovy.el | 2 +-
>  lisp/ob-maxima.el | 2 +-
>  lisp/ob-sed.el| 2 +-
>  6 files changed, 6 insertions(+), 6 deletions(-)

Applied onto main with amendments to commit messages.
Please refer to
https://orgmode.org/worg/org-contribute.html#commit-messages in future.

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2f4de60980b6b10770696c4ee0b610d0e96ab575
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=fc8e375b9bd2685690e6ec9f0cc6ed078a6e938f

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] DOCT integration: template specific hooks [9.5.5 (9.5.5-g003cc7 @ /home/n/.emacs.d/elpaca/builds/org/)]

[Ihor Radchenko]

No Wayman  writes:

> I've addressed your comments in the attached patch.
> I based it off the most recent patch in the thread.
> The main difference is that the hook properties accept a single 
> nullary function or list of nullary functions.

Applied onto main with minor amendments (filling and missing ":" in the
commit message).

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=7f3a6cf6e72fe9968c6ef32211c754b7fe0172b6

Thanks for your contribution!

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: The Org mode in the Org Git does not export

[Ihor Radchenko]

After further off-list discussion and online debugging, we have managed
to find out the culprit.

Thanks, Rudolf, for the kind assistance with debugging!

The slowdown mostly came from the new version of `org-html-format-latex'
that copies the parent Org buffer environment when generating LaTeX
images. There were a couple of bottlenecks.

In addition, we have found a critical bug caused by `buffer-file-name'
being non-nil in the buffer copies during export. The bug existed
forever but was previously much harder to be triggered.

Now, everything should be fixed on main via
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5a167f6ef20e337c9b1063097ebe64624ad932a6
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=aa90e5b59cc0fe41072cd6f78968e0b8d5ac6939
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4cb1b8ebd006e0659a34c942ab5594f177d6bf49
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=0551eba40ca1cdeac8645c8614747566025a7e94
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=b45911d41e9d81bc23b93d7e75d0a7611ae18f38
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=09fd5f886a81af686ac0b69af19eb7a8d2007284
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=514e3a9cd26e150f6ee7251433e14701b62f7e98
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=dcdf98a564d17f918afbb947dfc6c96244b94abb
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=0be36ac13eee17b3bf26ea55ba596bf61b71602d

Export copy buffer now can never be saved to disk and will never corrupt
the source Org file.

Rudolf, please kindly confirm that the export performance is back to
satisfactory on the latest main.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

[BUG] Re: 98e168b48 Add compatibility wrapper for string-clean-whitespace (Emacs 26 compatibility) [9.6-pre (release_9.5.5-920-g057193 @ /home/yantar92/.emacs.d/straight/build/org/)]

[Ihor Radchenko]

Kyle,

The following commit adds `string-trim', which is not yet available in
Emacs 26.

98e168b489e4350430d1600f7ece57215de1027c
Author: Kyle Meyer 
AuthorDate: Tue Oct 4 17:42:27 2022 -0400
Commit: Kyle Meyer 
CommitDate: Tue Oct 4 18:38:25 2022 -0400
compat: Add compatibility wrapper for string-clean-whitespace
* lisp/org-compat.el (org-string-clean-whitespace): New compatibility
function.
* lisp/ox.el (org-export-resolve-radio-link): Use
org-string-clean-whitespace.

This is a follow-up to the port of Emacs's 70341cab3.

Best,
Ihor

Re: Interest in an Org video meetup?

[Marcin Borkowski]

On 2022-10-06, at 19:24, Russell Adams  wrote:

> On Thu, Oct 06, 2022 at 05:28:12PM +0200, Marcin Borkowski wrote:
>> Me too, though it depends on the schedule.  What time of day do you plan
>> for that?
>
> From my original post:
>
>>> I'm offering to schedule and moderate the first few events. I'd
>>> propose a Saturday meeting in the afternoon European time to cover EU
>>> and NA.

Thanks.  Stupid me.

-- 
Marcin Borkowski
http://mbork.pl

Re: Fix 'ob-sed-test' on BSD/macOS

[Ihor Radchenko]

Rudolf Adamkovič  writes:

> Please see the attached two patches:
>
> (1) fixes 'ob-sed-test' on BSD/macOS, and
> (2) fixes a typo in 'ob-sed'.

Applied onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=48ac65bea08d385065c4b57f64a276f2b0d86a07
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=a220492064c674ef09589b43799e8868489783a4

Thanks for your contribution!

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH v1] Allow returning empty list from post-processing block

[Ihor Radchenko]

Jonas Bernoulli  writes:

> * lisp/ob-ref.el (org-babel-ref-resolve): When the result an empty
> list, then treat it as a list, not as the symbol nil.
> * testing/lisp/test-ob.el (test-ob/post-header-arguments): Add new
> test.
> * etc/ORG-NEWS (Post-processing code blocks can return an empty list):
> Document change in behavior.

Applied onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9b690462a319e4268f15949bba0fe024dca77182

Thanks!

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: What is a "date tree"? (find manual unclear) [was: Re: Dates in headlines]

[Ihor Radchenko]

alain.coch...@unistra.fr writes:

> Samuel Wales writes on Tue 28 Jun 2022 16:23:
>
>  > [inactive timestamps] much better than date trees for my case.
>
> Reading this, I tried to find out what a date tree is.
>
> The manual says (in 10.1.3.1):
>
>A date tree is an outline structure with years on the highest
>level, months or ISO weeks as sublevels and then dates on the
>lowest level.
>
> which I don't understand.  Could I be provided with a simple example
> of a date tree?

Indeed. Thanks for the heads-up!
Added on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=eece396db88e5793c994825fcb1f75d13091ee5c

> Also, in the manual, the 'Main index' has the entry:
>
>* date tree: Using capture.  
>
> but, if I follow the link, I end up in 10.1.2, in a paragraph about
> 'M-x org-capture' and I don't see the relevance with date trees.

Fixed. Now the index entry points to Capture template elements section.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9ef449224bc532f5cb2d0bc95cce0bb4a43c73bf

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] Three documentation patches

[Ihor Radchenko]

Stefan Kangas  writes:

> Ihor Radchenko  writes:
>
>> The patches look good, but I am unable to apply them onto current main:
>
> Hmm, strange.  I've rebased on top of current main, and I'm resending
> the resulting patches here.  I hope they work better.

This time everything applies like a charm.
Thanks!

Applied onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=101280aa66baec74e36deaeac403cbcbb3c72be8
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e28e3aaabba696444cf4f8243034602bc5824dc1
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=0b67b9f64f4fdba52398a729a76e18b6051401b4


-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] lisp/org-agenda.el: Fix filter preset problem for sticky agenda

[Ihor Radchenko]

Liu Hui  writes:

> When writing the test, I find the original patch only addresses the
> case where an entry contains multiple commands. Now the udpated patch
> can address the case containing one command by changing another global
> symbol property to per-buffer text property.
>
> From 718cb5258a407d8a51eb4a5bac3d0c8025a3f198 Mon Sep 17 00:00:00 2001
> From: Liu Hui 
> Date: Tue, 4 Oct 2022 11:12:41 +0800
> Subject: [PATCH] Fix filter preset problem for sticky agenda

Applied onto main with minor amendments (mostly added double space " "
between sentences in docstrings and the commit message).
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=edf5afc1d833a814cf97e814194b83b82f26a294

Thanks for your contribution!

Also, while we are at it, may you take a look at
https://list.orgmode.org/paxpr06mb7760f3a02d140e7de2baaec6c6...@paxpr06mb7760.eurprd06.prod.outlook.com/?
AFAIR, it is caused by a similar symbol property approach employed in
different place in org-agenda.el.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Interest in an Org video meetup?

[Russell Adams]

On Fri, Oct 07, 2022 at 09:43:23AM +0800, Ihor Radchenko wrote:
> Juan Manuel Macías  writes:
>
> > Great idea. I would like to participate, even if it was just to listen
> > :-) But I'm afraid that these months I'm going to have horrible
> > schedules. Is it planned to record these meetings?
>
> Even if there is a recording, where can we publish the recorded videos?

Exactly.

Recording brings with it extra logistics, which is why I deferred the
issue. ;]

--
Russell Adamsrlad...@adamsinfoserv.com
https://www.adamsinfoserv.com/

Re: Interest in an Org video meetup?

[Ihor Radchenko]

Juan Manuel Macías  writes:

> Great idea. I would like to participate, even if it was just to listen
> :-) But I'm afraid that these months I'm going to have horrible
> schedules. Is it planned to record these meetings?

Even if there is a recording, where can we publish the recorded videos?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Interest in an Org video meetup?

[Russell Adams]

On Thu, Oct 06, 2022 at 08:09:44PM +, Juan Manuel Macías wrote:
> Russell Adams writes:
>
> > Would there be any interest in a monthly 1-2 hour long ad-hoc screen
> > sharing and video discussion for Org-mode?
>
> Great idea. I would like to participate, even if it was just to listen
> :-) But I'm afraid that these months I'm going to have horrible
> schedules. Is it planned to record these meetings?

I can't commit to recording initially. I can't run them forever
either, but I'm happy to start the ball rolling.

Perhaps recording in the future?

--
Russell Adamsrlad...@adamsinfoserv.com
https://www.adamsinfoserv.com/

Re: Interest in an Org video meetup?

[Juan Manuel Macías]

Russell Adams writes:

> Would there be any interest in a monthly 1-2 hour long ad-hoc screen
> sharing and video discussion for Org-mode?
>
> I'm offering to schedule and moderate the first few events. I'd
> propose a Saturday meeting in the afternoon European time to cover EU
> and NA.
>
> I'm considering using Jitsi, or maybe GNU Jami.
>
> Topics could include Q, demonstrations of features, interactive
> troubleshooting, etc. I hadn't considered presentations, but
> that could be an option too.
>
> Comments?

Great idea. I would like to participate, even if it was just to listen
:-) But I'm afraid that these months I'm going to have horrible
schedules. Is it planned to record these meetings?

Best regards,

Juan Manuel

Re: Interest in an Org video meetup?

[Rudolf Adamkovič]

I, too, would like to join.

Rudy
-- 
"Programming reliably -- must be an activity of an undeniably
mathematical nature […] You see, mathematics is about thinking, and
doing mathematics is always trying to think as well as possible."
-- Edsger W. Dijkstra, 1981

Rudolf Adamkovič  [he/him]
Studenohorská 25
84103 Bratislava
Slovakia

test-org-table/sort-lines: Failing test on macOS

[Rudolf Adamkovič]

Howdy, howdy!

I see the test failure below on macOS.

Test test-org-table/sort-lines condition:

  (ert-test-failed
   ((should
 (equal "| a | x |\n| B | 4 |\n| c | 3 |\n"
(org-test-with-temp-text "| a | x |\n| c | 3 |\n| B | 4 |\n"
... ...)))
:form
(equal "| a | x |\n| B | 4 |\n| c | 3 |\n"
   #("| B | 4 |\n| a | x |\n| c | 3 |\n" 0 9
 (face org-table)
 10 19
 (face org-table)
 20 29
 (face org-table)))
:value nil :explanation
(array-elt 2
   (different-atoms
(97 "#x61" "?a")
(66 "#x42" "?B")
 FAILED  796/952  test-org-table/sort-lines (0.003410 sec)
   at ../lisp/test-org-table.el:1880

The isolated part of the test file that fails:

(let ((original-string-collate-lessp (symbol-function 'string-collate-lessp)))
  (cl-letf (((symbol-function 'string-collate-lessp)
 (lambda (s1 s2  _locale ignore-case)
   (funcall original-string-collate-lessp
s1 s2 "C" nil
(should
 (equal "| a | x |\n| B | 4 |\n| c | 3 |\n"
(org-test-with-temp-text "| a | x |\n| c | 3 |\n| B | 4 |\n"
 (org-table-sort-lines nil ?a)
 (buffer-string))

If I understand, "a" should be less than "B" when under "C" locale when
ignoring case (nil) , right?  Yet, I get the following:

(string-collate-lessp "a" "B" "C" nil)  ; => nil

[FYI: If I replace nil with t, the procedure returns nil too.]

Tested on Emacs 29 (adaa2fc90e) and Org 9.5.5 (580f28614).

Rudy
-- 
"It is no paradox to say that in our most theoretical moods we may be
nearest to our most practical applications."
-- Alfred North Whitehead, 1861-1947

Rudolf Adamkovič  [he/him]
Studenohorská 25
84103 Bratislava
Slovakia

Fix 'ob-sed-test' on BSD/macOS

[Rudolf Adamkovič]

Please see the attached two patches:

(1) fixes 'ob-sed-test' on BSD/macOS, and
(2) fixes a typo in 'ob-sed'.

Rudy
>From 868f878cb50c5234a16b2675688256892467f5f6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rudolf=20Adamkovi=C4=8D?= 
Date: Thu, 6 Oct 2022 21:14:17 +0200
Subject: [PATCH 1/2] ob-sed-test: Make the tests pass on BSD systems, such as
 macOS

* testing/examples/ob-sed-test.org: Fix BSD sed incompatibility
---
 testing/examples/ob-sed-test.org | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/testing/examples/ob-sed-test.org b/testing/examples/ob-sed-test.org
index aae1323ca..2f8bcb089 100644
--- a/testing/examples/ob-sed-test.org
+++ b/testing/examples/ob-sed-test.org
@@ -30,6 +30,9 @@
   :ID:   E3C6A8BA-39FF-4840-BA8E-90D5C4365AB1
   :END:
 
-  #+BEGIN_SRC sed :in-file test2.txt :cmd-line "-i"
+  /Note:/ Use =-i.backup= instead of just =-i= because the BSD =sed=,
+  unlike the GNU =sed=, requires =-i =.
+
+  #+BEGIN_SRC sed :in-file test2.txt :cmd-line "-i.backup"
 s/test/tested again/
   #+END_SRC
-- 
2.37.3

>From 34e352b07a53b070a6ea02f820c8d63d0abecebc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rudolf=20Adamkovi=C4=8D?= 
Date: Thu, 6 Oct 2022 21:18:57 +0200
Subject: [PATCH 2/2] ob-sed: Fix typo

* lisp/ob-sed.el: Fix a typo in a comment
---
 lisp/ob-sed.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/ob-sed.el b/lisp/ob-sed.el
index 9befa7163..ecebef925 100644
--- a/lisp/ob-sed.el
+++ b/lisp/ob-sed.el
@@ -35,7 +35,7 @@
 ;; In addition to the normal header arguments, ob-sed also provides
 ;; :cmd-line and :in-file. :cmd-line allows one to pass other flags to
 ;; the sed command like the "--in-place" flag which makes sed edit the
-;; file pass to it instead of outputting to standard out or to a
+;; file passed to it instead of outputting to standard out or to a
 ;; different file. :in-file is a header arguments that allows one to
 ;; tell Org Babel which file the sed script to act on.
 
-- 
2.37.3

-- 
"It is no paradox to say that in our most theoretical moods we may be
nearest to our most practical applications."
-- Alfred North Whitehead, 1861-1947

Rudolf Adamkovič  [he/him]
Studenohorská 25
84103 Bratislava
Slovakia

Re: Interest in an Org video meetup?

[Tory S. Anderson]

I would enjoy a video meetup on Orgmode, since it is the first and last program 
I interact with during my computing day.

--
Tory S. Anderson
Application & Web Developer
https://toryanderson.com

Re: Interest in an Org video meetup?

[Russell Adams]

On Thu, Oct 06, 2022 at 05:28:12PM +0200, Marcin Borkowski wrote:
> Me too, though it depends on the schedule.  What time of day do you plan
> for that?

>From my original post:

>> I'm offering to schedule and moderate the first few events. I'd
>> propose a Saturday meeting in the afternoon European time to cover EU
>> and NA.



--
Russell Adamsrlad...@adamsinfoserv.com
https://www.adamsinfoserv.com/

Re: Interest in an Org video meetup?

[Payas Relekar]

Marcin Borkowski  writes:

> On 2022-10-06, at 16:40, Leslie Watter  wrote:
>
>> Would be great to see what others are doing in their workflows using org ;-)
>>
>> I'd like to join to!
>
> Great idea!
>
> Me too, though it depends on the schedule.  What time of day do you plan
> for that?

+1 for both interest in joining and time of day.

Thanks,
Payas
--

Re: Interest in an Org video meetup?

[Marcin Borkowski]

On 2022-10-06, at 16:40, Leslie Watter  wrote:

> Would be great to see what others are doing in their workflows using org ;-)
>
> I'd like to join to!

Great idea!

Me too, though it depends on the schedule.  What time of day do you plan
for that?

Best,

-- 
Marcin Borkowski
http://mbork.pl

Re: Interest in an Org video meetup?

[Leslie Watter]

Would be great to see what others are doing in their workflows using org ;-)

I'd like to join to!

Cheers,

Leslie

On Thu, Oct 6, 2022 at 10:43 AM Kaushal Modi  wrote:

> I'd like to join.
>
> --
> Kaushal Modi
>
>
> On Thu, Oct 6, 2022 at 9:24 AM Russell Adams 
> wrote:
>
>>
>> Would there be any interest in a monthly 1-2 hour long ad-hoc screen
>> sharing and video discussion for Org-mode?
>>
>> I'm offering to schedule and moderate the first few events. I'd
>> propose a Saturday meeting in the afternoon European time to cover EU
>> and NA.
>>
>> I'm considering using Jitsi, or maybe GNU Jami.
>>
>> Topics could include Q, demonstrations of features, interactive
>> troubleshooting, etc. I hadn't considered presentations, but
>> that could be an option too.
>>
>> Comments?
>>
>> --
>> Russell Adamsrlad...@adamsinfoserv.com
>> https://www.adamsinfoserv.com/
>>
>>

-- 
Leslie H. Watter

[BUG] babel R src block with :results output hangs [9.5.2 (9.5.2 @ /usr/share/emacs/site-lisp/elpa/org-9.5.2/)]

[JM Nunes]

Source blocks with header arg ':results output' either locally or via
#+PROPERTY: do never return (waited 10 minutes before C-g).
Editing the block in a major mode buffer (C-c') shows the correct
results in the iess R session.

The block:

#+BEGIN_SRC R :results output
  sqrt(-4)  #+END_SRC

should show:

[1] NaN
Warning message:
In sqrt(-4) : NaNs produced


Emacs  : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
3.24.30, cairo version 1.16.0)

 of 2022-01-24, modified by Debian
Package: Org mode version 9.5.2 (9.5.2 @ 
/usr/share/emacs/site-lisp/elpa/org-9.5.2/)

[Solved] was: [BUG] babel R src block with :results output hangs [9.5.2 (9.5.2 @ /usr/share/emacs/site-lisp/elpa/org-9.5.2/)]

[JM Nunes]

Dear you,

I continued looking for information to understand the bug and come 
across another bug that lead me to update my ESS package and that solved 
the problem.



Thank you anywayy.
Kind regards,



On 05/10/2022 23.47, JM Nunes wrote:


Source blocks with header arg ':results output' either locally or via
#+PROPERTY: do never return (waited 10 minutes before C-g).
Editing the block in a major mode buffer (C-c') shows the correct
results in the iess R session.

The block:

#+BEGIN_SRC R :results output
   sqrt(-4)  #+END_SRC

should show:

[1] NaN
Warning message:
In sqrt(-4) : NaNs produced


Emacs  : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
3.24.30, cairo version 1.16.0)

  of 2022-01-24, modified by Debian
Package: Org mode version 9.5.2 (9.5.2 @ 
/usr/share/emacs/site-lisp/elpa/org-9.5.2/)

Re: Interest in an Org video meetup?

[Kaushal Modi]

I'd like to join.

--
Kaushal Modi


On Thu, Oct 6, 2022 at 9:24 AM Russell Adams 
wrote:

>
> Would there be any interest in a monthly 1-2 hour long ad-hoc screen
> sharing and video discussion for Org-mode?
>
> I'm offering to schedule and moderate the first few events. I'd
> propose a Saturday meeting in the afternoon European time to cover EU
> and NA.
>
> I'm considering using Jitsi, or maybe GNU Jami.
>
> Topics could include Q, demonstrations of features, interactive
> troubleshooting, etc. I hadn't considered presentations, but
> that could be an option too.
>
> Comments?
>
> --
> Russell Adamsrlad...@adamsinfoserv.com
> https://www.adamsinfoserv.com/
>
>

Re: [BUG] `org-fill-paragraph' doesn't respect formatting

[Rudolf Adamkovič]

Tor Kringeland  writes:

> The same happens with other formatting like *bold* and _underline_.

+1

I bump into this inconsistency almost every day, e.g.

*Example.* Starting with $n = 12$, ...

Rudy
-- 
"The whole science is nothing more than a refinement of everyday
thinking."
-- Albert Einstein, 1879-1955

Rudolf Adamkovič  [he/him]
Studenohorská 25
84103 Bratislava
Slovakia

Interest in an Org video meetup?

[Russell Adams]

Would there be any interest in a monthly 1-2 hour long ad-hoc screen
sharing and video discussion for Org-mode?

I'm offering to schedule and moderate the first few events. I'd
propose a Saturday meeting in the afternoon European time to cover EU
and NA.

I'm considering using Jitsi, or maybe GNU Jami.

Topics could include Q, demonstrations of features, interactive
troubleshooting, etc. I hadn't considered presentations, but
that could be an option too.

Comments?

--
Russell Adamsrlad...@adamsinfoserv.com
https://www.adamsinfoserv.com/

Re: Some links in online manual do not work

[Tim Landscheidt]

Ihor Radchenko  wrote:

>>> This looks like the nginx case issue again.

>>> I've looked at this and there does not seem to be any 'clean' way to fix
>>> this which also doesn't have significant processing overhead or a
>>> maintenance burden.

>>> I wonder if it would be worthwhile adding an option to HTML export which
>>> would force all link targets and exported filenames to lower case,
>>> thereby avoiding issues on platforms and with web servers which have
>>> different positions wrt case sensitivity?

>> Is the nginx configuration/webserver setup documented some-
>> where?

> AFAIK, our nginx configs are not public, but Bastien may privately share
> them if you are willing to help.

Willingness implies commitment, and I don't have that (nor
deeper nginx experience). :-) (That's one of the advantages
of free software for me: I can look at a bunch of problems,
pick the one I know the solution for and get instant grati-
fication :-).)

Tim

[PATCH 1/2] Don't print arguments of post-process arguments to stdout

[Jonas Bernoulli]

It is unclear whether the arguments were printed on purpose.  It might
be useful to do so at times for debugging purposes, but generally they
drown out other messages when a lot of post-processing is being done;
making it harder to spot messages of interest that would otherwise
allow noticing regressions.  This is particularly troublesome when
running org-babel-execute-buffer from a Makefile or script.

lisp/ob-emacs-lisp.el (org-babel-expand-body:emacs-lisp): Do not
print post-processing argument.
---
 lisp/ob-emacs-lisp.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/ob-emacs-lisp.el b/lisp/ob-emacs-lisp.el
index bb311aa44..b8e6ef298 100644
--- a/lisp/ob-emacs-lisp.el
+++ b/lisp/ob-emacs-lisp.el
@@ -58,7 +58,7 @@ (defun org-babel-expand-body:emacs-lisp (body params)
   (format "(let (%s)\n%s\n)"
  (mapconcat
   (lambda (var)
-(format "%S" (print `(,(car var) ',(cdr var)
+(format "%S" `(,(car var) ',(cdr var
   vars "\n  ")
  body
 
-- 
2.37.3

[PATCH 0/2] Don't print arguments of post-process arguments to stdout

[Jonas Bernoulli]

I run org-babel-execute-buffer from a Makefile and the output is quite
noisy, forcing me to filter out some output using grep -v so that I am
still able to spot any unexpected output that indicates some issue.

Now that I have started using post-processing code blocks, the output
has gotten even more noisy and unfortunately filtering out the unwanted
additions is not possible.

Currently all arguments to post-processing blocks are printed to
stdout.  I am not able to filter them out using grep because this
output seems to be split across multiple lines, so a regexp like
"^(" only matches parts of the noise.

It is unclear whether the arguments were printed on purpose.  It might
be useful to do so at times for debugging purposes, but generally they
make things harder, by obscuring output one would want to notice.

The second commit addresses a cosmetic, but somewhat related,
annoyance.

Jonas Bernoulli (2):
  Don't print arguments of post-process arguments to stdout
  Begin messages about executing code blocks with a capital letter

 lisp/ob-awk.el| 2 +-
 lisp/ob-core.el   | 2 +-
 lisp/ob-emacs-lisp.el | 2 +-
 lisp/ob-groovy.el | 2 +-
 lisp/ob-maxima.el | 2 +-
 lisp/ob-sed.el| 2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

-- 
2.37.3

[PATCH 2/2] Begin messages about executing code blocks with a capital letter

[Jonas Bernoulli]

By Emacs' convention all messages should begin with a capital letter.

lisp/ob-awk.el (org-babel-expand-body:awk):
lisp/ob-core.el (org-babel-execute-src-block):
lisp/ob-groovy.el (org-babel-execute:groovy):
lisp/ob-maxima.el (org-babel-execute:maxima):
lisp/ob-sed.el (org-babel-execute:sed):
Begin message with capital letter.
---
 lisp/ob-awk.el| 2 +-
 lisp/ob-core.el   | 2 +-
 lisp/ob-groovy.el | 2 +-
 lisp/ob-maxima.el | 2 +-
 lisp/ob-sed.el| 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/lisp/ob-awk.el b/lisp/ob-awk.el
index e2dfb0c9b..1db9c6b00 100644
--- a/lisp/ob-awk.el
+++ b/lisp/ob-awk.el
@@ -55,7 +55,7 @@ (defun org-babel-expand-body:awk (body _params)
 (defun org-babel-execute:awk (body params)
   "Execute a block of Awk code with org-babel.
 This function is called by `org-babel-execute-src-block'."
-  (message "executing Awk source code block")
+  (message "Executing Awk source code block")
   (let* ((result-params (cdr (assq :result-params params)))
  (cmd-line (cdr (assq :cmd-line params)))
  (in-file (cdr (assq :in-file params)))
diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index 27947111f..18722d141 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -791,7 +791,7 @@ (defun org-babel-execute-src-block ( arg info 
params executor-type)
 result exec-start-time)
(unless (fboundp cmd)
  (error "No org-babel-execute function for %s!" lang))
-   (message "executing %s %s %s..."
+   (message "Executing %s %s %s..."
 (capitalize lang)
  (pcase executor-type
('src-block "code block")
diff --git a/lisp/ob-groovy.el b/lisp/ob-groovy.el
index 426eaacdc..f1689ef12 100644
--- a/lisp/ob-groovy.el
+++ b/lisp/ob-groovy.el
@@ -52,7 +52,7 @@ (defcustom org-babel-groovy-command "groovy"
 (defun org-babel-execute:groovy (body params)
   "Execute a block of Groovy code with org-babel.
 This function is called by `org-babel-execute-src-block'."
-  (message "executing Groovy source code block")
+  (message "Executing Groovy source code block")
   (let* ((processed-params (org-babel-process-params params))
  (session (org-babel-groovy-initiate-session (nth 0 processed-params)))
  (result-params (nth 2 processed-params))
diff --git a/lisp/ob-maxima.el b/lisp/ob-maxima.el
index 1a944376e..ada98bae8 100644
--- a/lisp/ob-maxima.el
+++ b/lisp/ob-maxima.el
@@ -76,7 +76,7 @@ (defun org-babel-maxima-expand (body params)
 (defun org-babel-execute:maxima (body params)
   "Execute a block of Maxima entries with org-babel.
 This function is called by `org-babel-execute-src-block'."
-  (message "executing Maxima source code block")
+  (message "Executing Maxima source code block")
   (let ((result-params (split-string (or (cdr (assq :results params)) "")))
(result
 (let* ((cmdline (or (cdr (assq :cmdline params)) ""))
diff --git a/lisp/ob-sed.el b/lisp/ob-sed.el
index 9befa7163..6e17501e4 100644
--- a/lisp/ob-sed.el
+++ b/lisp/ob-sed.el
@@ -65,7 +65,7 @@ (defun org-babel-execute:sed (body params)
 BODY is the source inside a sed source block and PARAMS is an
 association list over the source block configurations.  This
 function is called by `org-babel-execute-src-block'."
-  (message "executing sed source code block")
+  (message "Executing sed source code block")
   (let* ((result-params (cdr (assq :result-params params)))
  (cmd-line (cdr (assq :cmd-line params)))
  (in-file (cdr (assq :in-file params)))
-- 
2.37.3

[HELP] Please help checking function definitions in the manual vs. docstrings (was: [BUG] Typo in manual [9.5.2 (9.5.2-gfbff08 @ /home/ignacio/.emacs.d/elpa/org-9.5.2/)])

[Ihor Radchenko]

Marco Wahl  writes:

> Ignacio Casso  writes:
>
>> I would like to report a minor typo in the manual, although I'm not sure
>> if this is the right place (please point me to it if it's not).
>
> Confirmed.

I fixed the exact typo on main for now.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=580f2861402ebd9c4effe0c8db5e6efdc139e79a
Fixed.

> And this is the right place to report this bug.  Thanks!
>
>> In the section Appendix A Hacking -> Using the Mapping API
>> (https://orgmode.org/manual/Using-the-Mapping-API.html), it says that
>> org-map-entries returns an alist, but it actually returns a list (as
>> correctly stated by C-h f org-map-entries).
>
> To me this looks like the documentation in the manual started from the
> documentation of the function.  and with time these two documentations
> diverged.
>
> What about removing the (diverged) duplication of the documentation of
> function org-map-entries from the manual?

I do not think that we should remove the function description from the
manual completely. There should be at least some description. Good
enough to get the users started.

Moreover, this function is not the only place where the outdated
docstring is used directly in the manual. Search for #+begin_defun in
the manual and try comparing manual vs. the actual docstring.

We may need to go through these function definitions and strip them out
of excessive details that might be a subject of change. Just leave the
essence about what the function does.

The above is just my suggestion though. Do note that Elisp manual is
using similar approach to the Org manual - a number of functions pretty
much have their docstrings copied from the code to the manual. And they
also do diverge...

I am not sure which way is better.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

[PATCH v1] Allow returning empty list from post-processing block

[Jonas Bernoulli]

* lisp/ob-ref.el (org-babel-ref-resolve): When the result an empty
list, then treat it as a list, not as the symbol nil.
* testing/lisp/test-ob.el (test-ob/post-header-arguments): Add new
test.
* etc/ORG-NEWS (Post-processing code blocks can return an empty list):
Document change in behavior.
---
 etc/ORG-NEWS|  6 ++
 lisp/ob-ref.el  |  2 +-
 testing/lisp/test-ob.el | 24 
 3 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index 4728528f8..74095d101 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -425,6 +425,12 @@ The new variable name is =org-plantuml-args=.  It now 
applies to both
 jar PlantUML file and executable.
 
 ** Miscellaneous
+*** Post-processing code blocks can return an empty list
+
+When the result of a regular code block is nil, then that was already
+treated as an empty list.  Now that is also the case for code blocks
+that post-process the result of another block.
+
 *** Styles are customizable in ~biblatex~ citation processor
 
 It is now possible to add new styles or modify old ones in ~biblatex~
diff --git a/lisp/ob-ref.el b/lisp/ob-ref.el
index b79e47900..2b4a16aea 100644
--- a/lisp/ob-ref.el
+++ b/lisp/ob-ref.el
@@ -199,7 +199,7 @@ (defun org-babel-ref-resolve (ref)
(org-babel-execute-src-block nil info params
 (error "Reference `%s' not found in this buffer" ref
 (cond
- ((symbolp result) (format "%S" result))
+ ((and result (symbolp result)) (format "%S" result))
  ((and index (listp result))
   (org-babel-ref-index-list index result))
  (t result)
diff --git a/testing/lisp/test-ob.el b/testing/lisp/test-ob.el
index 99912fe63..9051a642d 100644
--- a/testing/lisp/test-ob.el
+++ b/testing/lisp/test-ob.el
@@ -136,6 +136,30 @@ (ert-deftest test-ob/get-src-block-info-tangle ()
 (let ((info (org-babel-get-src-block-info)))
   (should (string= "no" (cdr (assq :tangle (nth 2 info
 
+(ert-deftest test-ob/post-header-arguments ()
+  "When the result of a post-processing source block is an empty
+list, then it should be treated as such; not as the symbol nil."
+  (should
+   (let ((default-directory temporary-file-directory))
+ (org-test-with-temp-text
+ "
+#+name: addheader
+#+header: :var rows=\"\"
+#+begin_src elisp :hlines yes
+  '()
+#+end_src
+#+header: :post addheader(*this*)
+#+begin_src emacs-lisp :results table
+#+end_src
+#+RESULTS:
+: nil"
+   (org-babel-execute-src-block)
+   (goto-char (1- (point-max)))
+   (equal (buffer-substring-no-properties
+   (line-beginning-position)
+   (line-end-position))
+  "#+RESULTS:")
+
 (ert-deftest test-ob/elisp-in-header-arguments ()
   "Test execution of elisp forms in header arguments."
   (org-test-with-temp-text-in-file "
-- 
2.37.3

Re: [PATCH] DOCT integration: template specific hooks [9.5.5 (9.5.5-g003cc7 @ /home/n/.emacs.d/elpaca/builds/org/)]

[No Wayman]

I've addressed your comments in the attached patch.
I based it off the most recent patch in the thread.
The main difference is that the hook properties accept a single 
nullary function or list of nullary functions.


>From 90f0c68e1149512b51230fd44ad728b38e5f088e Mon Sep 17 00:00:00 2001
From: Nicholas Vollmer 
Date: Tue, 27 Sep 2022 05:44:33 -0400
Subject: [PATCH] org-capture: Add template hook properties

* lisp/org-capture.el (org-capture-templates): Document template hook properties.
(org-capture-finalize): Execute :prepare/:before/:after-finalize functions.
(org-capture-place-template): Execute :hook functions.

* doc/org-manual.org Document template hook properties.

* etc/ORG-NEWS: Add news entry for template hook properties.

* testing/lisp/test-org-capture.el: Add tests for template hook properties.
---
 doc/org-manual.org   | 20 +++
 etc/ORG-NEWS |  6 +
 lisp/org-capture.el  | 32 
 testing/lisp/test-org-capture.el | 43 
 4 files changed, 101 insertions(+)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index ab8a295e5..6a857529c 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -7838,6 +7838,26 @@ Now lets look at the elements of a template definition.  Each entry in
   - ~:refile-targets :: Temporarily set ~org-refile-targets~ to the
 value of this property.
 
+  - ~:hook~ ::
+
+A nullary function or list of nullary functions run before ~org-capture-mode-hook~
+when the template is selected.
+
+ - ~:prepare-finalize~ ::
+
+A nullary function or list of nullary functions run before ~org-capture-prepare-finalize-hook~
+when the template is selected.
+
+ - ~:before-finalize~ ::
+
+A nullary function or list of nullary functions run before ~org-capture-before-finalize-hook~
+when the template is selected.
+
+ - ~:after-finalize~ ::
+
+A nullary function or list of nullary functions run before ~org-capture-after-finalize-hook~
+when the template is selected.
+
  Template expansion
 :PROPERTIES:
 :DESCRIPTION: Filling in information about time and context.
diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index cab64317f..1a482c3c7 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -657,6 +657,12 @@ When exiting capture mode via ~org-capture-refile~, the variable
 ~org-refile-targets~ will be temporarily bound to the value of this
 template option.
 
+*** Add Capture template hook properties
+
+Capture templates can now attach template specific hooks via the following properties:
+~:hook~, ~:prepare-finalize~, ~:before-finalize~, ~:after-finalize~.
+These nullary functions run prior to their global counterparts for the selected template.
+
 *** New startup options =#+startup: showlevels=
 
 These startup options complement the existing =overview=, =content=,
diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index 428d0ac0e..4b6b51b39 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -297,6 +297,21 @@ properties are:
 
  :no-saveDo not save the target file after finishing the capture.
 
+ :hook   A nullary function or list of nullary functions run before
+ `org-capture-mode-hook' when the template is selected.
+
+ :prepare-finalize   A nullary function or list of nullary functions run before
+ `org-capture-prepare-finalize-hook'
+ when the template is selected.
+
+ :before-finalizeA nullary function or list of nullary functions run before
+ `org-capture-before-finalize-hook'
+ when the template is selected.
+
+ :after-finalize A nullary function or list of nullary functions run before
+ `org-capture-after-finalize-hook'
+ when the template is selected.
+
 The template defines the text to be inserted.  Often this is an
 Org mode entry (so the first line should start with a star) that
 will be filed as a child of the target headline.  It can also be
@@ -740,6 +755,17 @@ of the day at point (if any) or the current HH:MM time."
 	(format "* Template function %S not found" f)))
  (_ "* Invalid capture template"
 
+(defun org-capture--run-template-functions (keyword  local)
+  "Run funcitons associated with KEYWORD on template's plist.
+For valid values of KEYWORD see `org-capture-templates'.
+If LOCAL is non-nil use the buffer-local value of `org-capture-plist'."
+  ;; Used in place of `run-hooks' because these functions have no associated symbol.
+  ;; They are stored directly on `org-capture-plist'.
+  (let ((value (org-capture-get keyword local)))
+(if (functionp value)
+(funcall value)
+  (mapc #'funcall value
+
 (defun org-capture-finalize ( stay-with-capture)
   "Finalize the capture process.
 With prefix argument STAY-WITH-CAPTURE, jump to the location of the
@@ -751,6 +777,7 @@ captured item after finalizing."
 	   

Re: Bug: org-table-clean-line may not return only | and space [9.4.4 (release_9.4.4 @ /home/tbb/code/emacs/emacs/lisp/org/)] [9.4.4 (release_9.4.4 @ /home/tbb/code/emacs/emacs/lisp/org/)]

[Mauro Aranda]

Ihor Radchenko  writes:

> Ihor Radchenko  writes:
>
>> Mauro Aranda  writes:
>>
>>> 5. I expected to get a clean row:
>>> Here is a table:
>>> |   |   |
>>> | Data1 | Data2 |
>>>
>>> but I got:
>>> Here is a table:
>>> |   | Data2 |
>>> | Data1 | Data2 |
>>
>> Confirmed
>
> Fixed on main.
> 
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f0b7dfb3a018891b2955986b0bdb5bf6fd5beb57


Thanks!

What is a "date tree"? (find manual unclear) [was: Re: Dates in headlines]

[Alain . Cochard]

Samuel Wales writes on Tue 28 Jun 2022 16:23:

 > [inactive timestamps] much better than date trees for my case.

Reading this, I tried to find out what a date tree is.

The manual says (in 10.1.3.1):

   A date tree is an outline structure with years on the highest
   level, months or ISO weeks as sublevels and then dates on the
   lowest level.

which I don't understand.  Could I be provided with a simple example
of a date tree?

Also, in the manual, the 'Main index' has the entry:

   * date tree: Using capture.  

but, if I follow the link, I end up in 10.1.2, in a paragraph about
'M-x org-capture' and I don't see the relevance with date trees.

Regards.


-- 
EOST (École et Observatoire des Sciences de la Terre) 
ITE (Institut Terre & Environnement) | alain.coch...@unistra.fr
5 rue René Descartes   [bureau 106]  | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France | [ slot available for rent ]

Re: Should we make org-fill-element respect the selected region and not expand the selection to the element boundaties?

[Fraga, Eric]

On Thursday,  6 Oct 2022 at 16:38, Ihor Radchenko wrote:
> Should we go for it?

It would mean better alignment with the rest of the text modes in Emacs
so I would be supportive.  But I only tend to use filling for paragraphs
in any case so the breaking change would not affect me much.

-- 
: Eric S Fraga, with org release_9.5.5-853-g7b9d8e in Emacs 29.0.50

Re: Bug report: org-preview-latex fails when using tramp

[Ihor Radchenko]

Timothy  writes:

> Confirmed.
>
> I just tried this by creating an Org file on a Debian server (I run OpenSUSE
> with TexLive 2021). From looking at the `*Org Preview LaTeX Output*' buffer, 
> it
> appears that the temp file is created on my local machine, and then the 
> process
> is called on the remote machine.
>
> ┌
> │ This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
> (preloaded format=latex)
> │  restricted \write18 enabled.
> │ entering extended mode
> │ ! I can't find file `/tmp/orgtexToEnS4.tex'.
> └
>
> Having a look at `org-create-formula-image', I suspect this is due to the
> `make-temp-name' call at
> .
> Perhaps `tramp-make-tramp-temp-name' could be useful?

But will it be efficient? We will need to transfer images between the
remote host and the Emacs host.

Should we instead arrange the LaTeX call to be done on user side all the
time?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Should we make org-fill-element respect the selected region and not expand the selection to the element boundaties? (was: Bug: org-fill-paragraph [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)])

[Ihor Radchenko]

Ihor Radchenko  writes:

> Edrie Ddrie  writes:
>
>> When using `org-fill-paragraph' on a part of a paragraph, e.g. with halve
>> the lines as active region, it still uses the unselected text around when
>> filling.
>> This works different than `fill-paragraph', `fill-region' and
>> `fill-region-as-paragraph' that fill only the selected part of a paragraph
>> WITHOUT effecting the text around.
>> I don't know if this is a real bug but it is confusing, and annoying
>> because org-mode overrides the default `C-q' key binding for
>> `fill-paragraph' so I have to invoke that command via M-x.
>
> Confirmed

While I understand that the current behaviour is unexpected, it is
internally consistent within Org for different kind of Org elements:
paragraphs, source blocks, comments, tables etc. For all the elements,
Org effectively expands the region boundaries to the beginning/end of
the first/last element in the selected region.

If we do decide to change expanding the selection to the element
boundaries, it should be done across all filled element types.

It will also be a breaking change.

Should we go for it?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] `org-fill-paragraph' doesn't respect formatting

[Ihor Radchenko]

Tor Kringeland  writes:

> Applying `org-fill-paragraph' to /e.g./
>
>   /Some text./  Some more text.
>
> when `sentence-end-double-space' is t removes the double space to a
> single space.  The same happens with other formatting like *bold* and
> _underline_.  In other instances it is more context aware.  /E.g./
> applying it to
>
>   (Some text.)  Some more text.
>
> does nothing, which is correct.

This is because Org does not set sentence-end-base to include the markup
markers.

The easiest way to fix this bug will be setting sentence-end-base.
However, in addition to fixing the particular case in this bug report,
such change may have unforeseen consequences in other scenarios.

We may be more selective and only allow the actual parsed emphasis end
markers to be recognized as sentence end.

Or I may be overthinking things because
`org-mode-transpose-word-syntax-table' is already using indiscriminate
approach wrt treating the emphasis barely shielding emphasis additions
to specific commands (like in `org-fill-element').

WDYT?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Bug: org-table-clean-line may not return only | and space [9.4.4 (release_9.4.4 @ /home/tbb/code/emacs/emacs/lisp/org/)] [9.4.4 (release_9.4.4 @ /home/tbb/code/emacs/emacs/lisp/org/)]

[Ihor Radchenko]

Ihor Radchenko  writes:

> Mauro Aranda  writes:
>
>> 5. I expected to get a clean row:
>> Here is a table:
>> |   |   |
>> | Data1 | Data2 |
>>
>> but I got:
>> Here is a table:
>> |   | Data2 |
>> | Data1 | Data2 |
>
> Confirmed

Fixed on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f0b7dfb3a018891b2955986b0bdb5bf6fd5beb57

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [O] BUG: Capture task clocking doesn't stop due to narrowing

[Ihor Radchenko]

Ihor Radchenko  writes:

> Bernt Hansen  writes:
>
>> Hi,
>>
>> I ran into an issue this morning where my capture task continues
>> clocking on save.  This occurs in both master and maint when not
>> clocking into a drawer.
>>
>> ECM follows.
>
> Confirmed

Fixed on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=224708323e0f5682eb3894d58032a593a1a05214

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] org-beamer :BEAMER_ACT: ignored on columns

[Fraga, Eric]

On Thursday,  6 Oct 2022 at 11:06, Ihor Radchenko wrote:
> Is there any reason why you only allow actions for "column" environment
> specifically? What about other environments?

Good question.  But I don't know the answer!  I was mimicking the existing code 
(e.g. the line above).  I am not sure of the logic of limiting to this case.  I 
can try (maybe tomorrow) to see what happens without the condition (and maybe 
try to understand the original logic).

-- 
: Eric S Fraga, with org release_9.5.5-840-g52be6f in Emacs 29.0.50

Re: Bug: Percentage in caption (even escaped) does not work in LaTeX export

[Ihor Radchenko]

Timothy  writes:

> This should be finally fixed in
>  when it’s merged.

The referenced patch has been applied, and the bug should be fully
resolved on main now.
Fixed.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at