[ANN] We are now regularily testing Org main branch against Emacs 26, 27, 28

[Bastien]

Hi all,

thanks to joint efforts by Christian Köstlin and Ihor, we are running
the Org test suite from the Org main branch against Emacs 26, 27, 28.

Every three hours, a script from the orgmode.org server checks if the
Org main branch changed.

If yes, we run the Org test suite against Emacs 26, 27 and 28.

If a test fails, a failure report is sent to a new mailing list:
https://lists.sr.ht/~bzg/org-build-failures and we can inspect what
did go wrong.

If a test fails again (i.e. there was a failure, then the repo was
updated, then there is a failure again for the same test), reports are
sent to Ihor, Christian and me, not to the dedicated list.

Tests are performed by running builds on sr.ht.  You can read the
builds in this new repository: https://git.sr.ht/~bzg/org-mode-tests

We are now testing this setup: if it useful enough, we will redirect
failure reports to the Org mailing list, while using the new one for
repeated failures, so as to not spam the list.

In the future, resources at https://git.sr.ht/~bzg/org-mode-tests
will also perhaps help contributors defining new ways on how to run
tests, beyond the current way ("make test").

Patch submitters are required to run the tests themselves before
submitting a patch: we don't rely on this new setup to test patches,
only to catch errors that may inadvertently slip through the cracks.

Thanks again to Christian and Ihor for setting this up!

-- 
 Bastien

Re: [PATCH] org-manual: Remove mention of print edition

[Bastien]

Hi Gregor,

Gregor Zattler  writes:

> Dear org-mode developers, the manual still links to
> network-theory.co.uk for the printed version of the manual.

Thanks for reporting this.

Canceled and replaced by this change, which mentions that the
publisher closed in 2009:

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?h=bugfix&id=58a46fab

I think it is good to remember that Network Theory Ltd. was the
original publisher of the printed manual, as people may find others
options online now.

-- 
 Bastien

Re: Best android app

[Max Nikulin]

On 16/10/2022 01:31, ypuntot wrote:

Could these be added there?

https://github.com/DanielDe/org-web
https://easyorgmode.com/
https://github.com/amake/orgro
https://logseq.com/


At least some brief description of real advantages from actual users is 
necessary. Copy-paste from the project site sometimes is not the best 
option.


Awesome lists is an interesting initiative trying to emphasize strong 
sides of various projects, but particular lists varies in quality. 
Example: https://github.com/emacs-tw/awesome-emacs#readme


I do not have strong opinion concerning proprietary application. 
Requirements for worg section as driven by user content are not so 
strict as for the main part of the Org site that must adhere to FSF 
rules. Perhaps it is possible to separate non-free software by some 
discouraging disclaimer.

Re: [PATCH] Fix for bug that makes the user have to answer the prompt more than once for resolving running clock after being idle

[Ihor Radchenko]

Ignacio Casso  writes:

> I have fixed the bug reported in
> https://lists.gnu.org/archive/html/emacs-orgmode/2010-08/msg00188.html,
> https://lists.gnu.org/archive/html/emacs-orgmode/2019-02/msg00333.html,
> and
> https://lists.gnu.org/archive/html/emacs-orgmode/2022-03/msg00127.html.
>
> In the last of those threads (two emails) I explained in detail the bug and 
> the
> reason it happens. Here is the patch:
>
> From bb4c9e0836b039a496a033a002d97d7062bd8dc8 Mon Sep 17 00:00:00 2001
> From: Ignacio 
> Date: Thu, 17 Mar 2022 11:50:44 +0100
> Subject: [PATCH] org-clock.el: resolve running clock after being idle only
>  once

Thanks!
Applied onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=31f2510995c938d96947086ecd807d9b148ec7f8

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

Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

[Ihor Radchenko]

Ignacio Casso  writes:

>> So the problem is in (org-user-idle-seconds), which in my window system
>> boils down to a call to (current-idle-time). It should return 0 after
>> answering the prompt, but in my system it keeps counting up. At this
>> point I stopped investigating since that function is defined in C.
>>
>
> I have investigated this a little bit further and it seems that reading
> a character with read-char only resets the idle timer if the SECONDS
> argument is nil (which is not the case here) . I reported it as a bug to
> bug-gnu-em...@gnu.org, but it seems there is a reason for that. See
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54371

Fixed on main by merging your other patch.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=31f2510995c938d96947086ecd807d9b148ec7f8

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

Re: [O] Manual errata suggestions

[Ihor Radchenko]

TonyMc  writes:

> I have read through the org mode manual (something I have meant to redo
> for ages) and found some typos, or sentences that might be worded more
> felicitously. I updated my org-mode from 9.1.1 to 9.1.2 part way
> through this reading, so some of the items may already have been fixed.

For record, most of these suggestions have been incorporated into the
manual.

A few were missing though. Now fixed on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3fc782e9b8cbbccc9bab11bd1be541cca79a97f0

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

Re: [bug] `org-latex-line-break-safe' breaks the export of verse blocks to LaTeX

[Ihor Radchenko]

Juan Manuel Macías  writes:

> The recent addition of the `org-latex-line-break-safe' constant makes it
> impossible to compile verse blocks. The reason is that now a \\ is
> inserted between each stanza (aka each paragraph), instead of the
> `\vspace{1em}' as before. That's wrong, as this compile error message
> says:

Thanks for reporting!
Fixed on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5fa66c7ffc4efbea11357fe0d05bc570855cfa91

This was an omission when replacing "\\" instances with safer version in
ox-latex.el.

> On the other hand, I have a few reservations about the usefulness of
> org-latex-line-break-safe. To begin with, it is a particular solution
> applied in a general way. This can have unexpected consequences, as has
> happened in verse blocks. It's like putting your whole body in a
> cast because of a broken finger.

The idea is to use "\\\someescapeLaTeXcommand" rather than "\\". The
latter can take arguments unexpectedly. See
https://orgmode.org/list/8735c0kpb9.fsf@localhost

> I think if the reason for this addition is to prevent problems with
> square brackets, in certain contexts, why not just apply a point
> solution? For example, putting {[}, which is a common LaTeX way to
> protect a square bracket.

Because people export tables not only to LaTeX, but also to other
formats. {[} makes no sense then.

> Use a macro, for example, or even
> define a new entity, something like:
>
> (setq org-entities-user
>   '(("lbrack" "{[}" nil "[" "[" "[" "[")
>   ("rbrack" "{]}" nil "]" "]" "]" "]")))

It will be unclear when to use such entity. Note that it is not obvious
at all that LaTeX export specifically will stumble on

| [1, 2] |
| [3, 4] |

without knowing LaTeX internals and checking the exported LaTeX
intermediate source closely.

We already ask users to deal with Org parser oddities. If we also demand
knowing LaTeX oddities, it will be too much. Better modify parser to
export valid Org syntax into valid LaTeX.

> And finally, I think that applying a general solution to this problem is
> something that should be done(IMHO) in LaTeX and not in Org, for
> example, with some new package that would protect certain signs or
> through ad hoc LaTeX/Lua code.

Either way, we will need to use the new package in ox-latex.el. And our
current approach is somewhat better because users can still use direct
LaTeX @@latex:\\@@ if they want to get "\\" exactly.

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

Re: Best android app

[Ypo]

And I am reading that it is not for Android; just Linux, Windows and Mac.

Definitively, shouldn't go there.

El 16/10/2022 a las 1:01, Juan Manuel Macías escribió:

ypuntot writes:

https://easyorgmode.com/  

Proprietary license. This should not be recommended here
(https://easyorgmode.com/terms).

Re: Best android app

[Juan Manuel Macías]

ypuntot writes:

> https://easyorgmode.com/ 

Proprietary license. This should not be recommended here
(https://easyorgmode.com/terms).

[bug] `org-latex-line-break-safe' breaks the export of verse blocks to LaTeX

[Juan Manuel Macías]

The recent addition of the `org-latex-line-break-safe' constant makes it
impossible to compile verse blocks. The reason is that now a \\ is
inserted between each stanza (aka each paragraph), instead of the
`\vspace{1em}' as before. That's wrong, as this compile error message
says:

-
A \newline or \\ command appears between paragraphs, where it makes no
sense. If you're trying to ``leave a blank line'', use a \vspace
command.
-

You can test yourself with this example:

#+begin_verse
lorem ipsum dolor
lorem ipsum dolor

lorem ipsum dolor
lorem ipsum dolor

lorem ipsum dolor
lorem ipsum dolor
#+end_verse

On the other hand, I have a few reservations about the usefulness of
org-latex-line-break-safe. To begin with, it is a particular solution
applied in a general way. This can have unexpected consequences, as has
happened in verse blocks. It's like putting your whole body in a
cast because of a broken finger.

I think if the reason for this addition is to prevent problems with
square brackets, in certain contexts, why not just apply a point
solution? For example, putting {[}, which is a common LaTeX way to
protect a square bracket. Use a macro, for example, or even
define a new entity, something like:

(setq org-entities-user
  '(("lbrack" "{[}" nil "[" "[" "[" "[")
("rbrack" "{]}" nil "]" "]" "]" "]")))

And finally, I think that applying a general solution to this problem is
something that should be done(IMHO) in LaTeX and not in Org, for
example, with some new package that would protect certain signs or
through ad hoc LaTeX/Lua code.

Best regards,

Juan Manuel 

-- 
--
--
Juan Manuel Macías 

https://juanmanuelmacias.com

https://lunotipia.juanmanuelmacias.com

https://gnutas.juanmanuelmacias.com

Re: Org 9.6-pre and Bash sessions

[Rudolf Adamkovič]

Ihor Radchenko  writes:

> Is it what you actually saw in the past? I just tried with older Org
> versions on my system and the output is
>
>: [00m > > > hello

No.  By "expected", I mean what I expect as a user (and what I would
assert on in a regression test as a developer).

For the record, with Org in Emacs 29, I get:

:
: > > > hello

on the first run and then

:
: > > hello

on the subsequent runs.

Better than the new version but still wrong. :)

Rudy
-- 
"Genius is 1% inspiration and 99% perspiration."
-- Thomas Alva Edison, 1932

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

Re: Best android app

[ypuntot]

Could these be added there?

https://github.com/DanielDe/org-web
https://easyorgmode.com/
https://github.com/amake/orgro
https://logseq.com/



> Re: Best android app
> From: Ihor Radchenko
> Subject: Re: Best android app
> Date: Sat, 15 Oct 2022 09:16:13 +0800
> Renato Pontefice  writes:
> 
>> Sorry…I just realize that I’ve not tell for what I’m looking for the best
>> application…. :-(
>>
>> It’s for open .org file!
>> I would see my org-mode file I’ve created on my emacs on my Mac and check
>> every things…
> 
> https://orgmode.org/worg/org-faq.html#org0a6fc30

Org-mode: how to change field

[Renato Pontefice]

Hi,
I’m trying to change the field value, but I cannot edit this file. If I try to 
erase some character (with backspace), it’s not possible:or it does not start 
to erase or (if I press for log time) it erase all the field.

How can I edit it?

Thank you

Renato 

Re: links to orgcard.pdf and orgcard.txt are broken

[Bastien Guerry]

Ihor Radchenko  writes:

> Bastien, could you take a look?

Now https://orgmode.org/orgcard.txt is back too.

-- 
 Bastien

Doubts about a function for my org-capture template

[Juan Manuel Macías]

Hi all,

I have written this function to be able to choose the type of block in
which to enclose the marked content (by default, quote). So in
my org-capture template I put %(my-capture-block) instead of %i:

┌
│ (defun my-capture-block ()
│   (let ((initial (org-capture-get :initial)))
│ (when initial
│   (let ((block-name
│(read-string
│ "Block type for marked content (default quote): "
│ nil nil "quote")))
│   (format
│"#+begin_%s\n%s\n#+end_%s"
│block-name
│initial
│(if (string-match "\\(src\\)\\(.+\\)" block-name)
│(match-string 1 block-name)
│  block-name))
└

The function works fine from eww, but it doesn't work with org-protocol
+ qutebrowser, as the value of :initial in org-capture-plist seems to be
nil. I've solved it by enclosing %i between two sexp %(...), one to
format the #+begin_xxx and the other to guess the #+end_xxx, but it's
more verbose. Does anyone have a clue how to get the value of %i for
org-protocol with a function inside the template?

Best regards and happy weekend,

Juan Manuel 

-- 
--
--
Juan Manuel Macías 

https://juanmanuelmacias.com

https://lunotipia.juanmanuelmacias.com

https://gnutas.juanmanuelmacias.com

Re: <%%(diary-float t 5 1)>

[Ihor Radchenko]

[I am adding Org mailing list back to the email loop. Please use "Reply
All" when communicating publicly in the mailing lists]

Renato Pontefice  writes:

> Of course!
> This is one statement of my .org file
>
> ** things to do each first Friday of each month 21:00-22:00
>  <%%(diary-float t 5 1)>
>
>  That is a recurrent event that occur every firs Friday of each month.
> How can I the exact day on my agenda?

1. Using "/" in agenda does not really show agenda buffer. It shows the
   built-in "occur" buffer searching matching lines across agenda files.

2. When you need time information, you need to tell Org agenda which
   time period to search for. This is what agenda for day/week ("a" in
   the menu) is doing. In agenda for day/week you can select the date
   and time range where to match Org headings. You can change the
   selected time period by pressing "v" in agenda and selecting the
   desired menu option. You can jump between periods using "j" (jump to
   day) or f/b to move to the adjacent periods

3. Once in day/week agenda, you can limit the displayed entries to
   arbitrary search term matches using "=" (M-x
   org-agenda-filter-by-regexp). There are also similar functions M-x
   org-agenda-filter-by-... to limit the displayed entries by
   tag/property, effort, category, etc.

4. If you log time spent doing certain task or enable org-log-done, you
   may also use inactive timestamp mode "v [" to display when the test
   changes its todo state or is clocked in.

Hope it helps.

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

[PATCH] org-manual: Remove mention of print edition

[Gregor Zattler]

Dear org-mode developers, the manual still links to
network-theory.co.uk for the printed version of the manual.

But there is no service under this address any more (or
ATM).  Even if this was only a temporary hiccup version 7.3
of the manual is quite outdated now.  Therefore I propose to
remove the respective paragraph, see attached patch.

Ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-
>From cdbe7bfd26aaff292156caf6391cd0acfba6d446 Mon Sep 17 00:00:00 2001
From: Gregor Zattler 
Date: Sat, 15 Oct 2022 13:15:51 +0200
Subject: [PATCH] org-manual: Remove mention of print edition

* doc/org-manual.org (Summary): Remove mention of print edition since
network-theory.co.uk is no more.
---
 doc/org-manual.org | 4 
 1 file changed, 4 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index a278eb222..d95a9ef6e 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -73,10 +73,6 @@ of Org, as well as additional information, frequently asked questions
 (FAQ), links to tutorials, etc.  This page is located at
 [[https://orgmode.org]].

-#+cindex: print edition
-An earlier version (7.3) of this manual is available as a [[http://www.network-theory.co.uk/org/manual/][paperback
-book from Network Theory Ltd.]].
-
 ** Installation
 :PROPERTIES:
 :DESCRIPTION: Installing Org.
--
2.38.0.15.gbbe21b64a0

Re: <%%(diary-float t 5 1)>

[Ihor Radchenko]

Renato Pontefice  writes:

> Hi, I’ve used this function (that you suggested me) to enter a schedule 
> activity, and it run very well. But when I try to view this scheduled event 
> on my Agenda, I made so:
> C - C-a
> From the menu that appear in another buffer, I select / (that ask me the word 
> that I’m looking for) but I obtain a line (or more lines) without the date of 
> the occurrence, just with the time that I’ve written on the occur.
> Is there a way to obtain the entire data + time in every occurs?

It would help if you provided more details. Ideally, with a small
example Org file.

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

<%%(diary-float t 5 1)>

[Renato Pontefice]

Hi, I’ve used this function (that you suggested me) to enter a schedule 
activity, and it run very well. But when I try to view this scheduled event on 
my Agenda, I made so:
C - C-a
From the menu that appear in another buffer, I select / (that ask me the word 
that I’m looking for) but I obtain a line (or more lines) without the date of 
the occurrence, just with the time that I’ve written on the occur.
Is there a way to obtain the entire data + time in every occurs?

Thank you

Renato

Re: links to orgcard.pdf and orgcard.txt are broken

[Bastien Guerry]

Ihor Radchenko  writes:

>> both the link to the English reference card as .pdf as well as the
>> plain ASCII version mentioned on https://orgmode.org/worg/ are
>> inaccessible.
>
> Confirmed.

Fixed, thanks!

Not for the ASCII version, as I need to find orgcard2ref.pl back in
the repo history before recreating the ASCII card.

-- 
 Bastien