Re: How to detect current in logbook drawer?

[Ihor Radchenko]

> I want to get around this problem. So need to know how to detect currently
> in logbook drawer or something else which used to record clocking note,
> `org-add-note`, etc.

You may try to use `org-logbook-drawer-re'.

> When I toggle org-log-mode and related options in org-agenda buffer. I
> found my org-link-beautify will caused long time suspend and no stop. After
> debug, I found org-link-beautify text-property caused this problem.

Could you provide more details how your text property is causing the
problem in org-agenda? Which function in agenda is slow?

Best,
Ihor


"numbch...@gmail.com"  writes:

> I have a org-mode extension:
> https://github.com/stardiviner/org-link-beautify/blob/master/org-link-beautify.el#L71
>
> It will beautify links with text-properties.
>
> When I toggle org-log-mode and related options in org-agenda buffer. I
> found my org-link-beautify will caused long time suspend and no stop. After
> debug, I found org-link-beautify text-property caused this problem.
>
> I want to get around this problem. So need to know how to detect currently
> in logbook drawer or something else which used to record clocking note,
> `org-add-note`, etc.
>
> Or maybe org-agenda upstream can do something to work around this
> text-properties issue?
>
> [stardiviner] GPG key ID: 47C32433
> IRC(freeenode): stardiviner Twitter:  @numbchild
> Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
> Blog: http://stardiviner.github.io/

Re: Bug: eldoc error: (void-function nil) [9.3.7 (release_9.3.7-708-g5417e3 @ /home/n/.emacs.d/straight/build/org/)]

[Kyle Meyer]

No Wayman writes:

> The patch to org-eldoc applied in b2b587387 still throws an error:
>
> eldoc error: (void-function nil)
>
> I was unable to step through this because (I think) eldoc causes 
> the debugger to close as soon as input is received. The error 
> occurs when `eldoc--invoke-strategy` attempts to funcall 
> eldoc-documentation-default.
>
> The attached patch works for me, but I do not know if it is the 
> correct solution.

Yeah, b2b587387 dealt with the compiler warnings, but indeed it looks
like there is at least [*] this remaining issue.  Thanks for catching it
and for the patch.

I'm short on time tonight, but I'll take a closer look tomorrow.


[*] Perhaps org-eldoc-get-mode-local-documentation-function's use of
eldoc-documentation-function is also problematic?

How to detect current in logbook drawer?

[numbch...@gmail.com]

I have a org-mode extension:
https://github.com/stardiviner/org-link-beautify/blob/master/org-link-beautify.el#L71

It will beautify links with text-properties.

When I toggle org-log-mode and related options in org-agenda buffer. I
found my org-link-beautify will caused long time suspend and no stop. After
debug, I found org-link-beautify text-property caused this problem.

I want to get around this problem. So need to know how to detect currently
in logbook drawer or something else which used to record clocking note,
`org-add-note`, etc.

Or maybe org-agenda upstream can do something to work around this
text-properties issue?

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

[PATCH] improve ol-man.el with occur searching

[numbch...@gmail.com]

With this patch, ol-man.el link type can be a link like this:
```org
[[man:grep::--extended-regexp][grep --extended-regexp]]
```
Occur will auto search "--extended-regexp" string in man page buffer.

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
From dcb9246ce948ce5d409c4f1e6d3e0ab53ed2ff4d Mon Sep 17 00:00:00 2001
From: stardiviner 
Date: Fri, 14 Aug 2020 12:33:51 +0800
Subject: [PATCH] ol-man.el: Add occur searching in man page buffer

* contrib/lisp/ol-man.el (org-man-open): Support auto searching man page
buffer with occur.
---
 contrib/lisp/ol-man.el | 11 +--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/contrib/lisp/ol-man.el b/contrib/lisp/ol-man.el
index 5cb7e0155..8ad1fabb2 100644
--- a/contrib/lisp/ol-man.el
+++ b/contrib/lisp/ol-man.el
@@ -37,8 +37,15 @@ (defcustom org-man-command 'man
 
 (defun org-man-open (path _)
   "Visit the manpage on PATH.
-PATH should be a topic that can be thrown at the man command."
-  (funcall org-man-command path))
+PATH should be a topic that can be thrown at the man command.
+If PATH contains extra ::STRING which will use `occur' to search
+matched strings in man buffer."
+  (string-match "\\(.*?\\)\\(?:::\\(.*\\)\\)?$" path)
+  (let* ((command (match-string 1 path))
+	 (search (match-string 2 path)))
+(funcall org-man-command command)
+(with-current-buffer (concat "*Man " command "*")
+  (occur search
 
 (defun org-man-store-link ()
   "Store a link to a README file."
-- 
2.27.0

Re: Bug: org agenda leader text "on-the-date" doesn't show for items with both SCHEDULED and DEADLINE properties [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]

[Kyle Meyer]

Russell Adams writes:

> On Thu, Aug 13, 2020 at 06:13:09PM +0100, Dinnyés Dániel wrote:
>> Any response regarding this? Was this registered? If so, Is there a link to
>> track the bug status?
>
> Dinnyés,
>
> There is only the mailing list, there is no web based bug
> tracker. These reports get attention as time permits. Developers
> typically respond on the thread as that occurs. I'm just a helpful
> guy. ;]

In this case, though, it doesn't look like the message hit the list (or
it is very delayed at least).  Based on the In-Reply-To chain, the
original message was

CAFfHKJ59KSyiS5UVRVEJ4KJEm5CSH2zZsdcj2s7K=hrwzcm...@mail.gmail.com

I don't have that message locally, and it doesn't show up at
 or
.

Bug: eldoc error: (void-function nil) [9.3.7 (release_9.3.7-708-g5417e3 @ /home/n/.emacs.d/straight/build/org/)]

[No Wayman]

The patch to org-eldoc applied in b2b587387 still throws an error:

eldoc error: (void-function nil)

I was unable to step through this because (I think) eldoc causes 
the debugger to close as soon as input is received. The error 
occurs when `eldoc--invoke-strategy` attempts to funcall 
eldoc-documentation-default.


The attached patch works for me, but I do not know if it is the 
correct solution.


Emacs  : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, X 
toolkit, cairo version 1.17.3, Xaw3d scroll bars)

of 2020-08-12
Package: Org mode version 9.3.7 (release_9.3.7-708-g5417e3 @ 
/home/n/.emacs.d/straight/build/org/)


>From 45dfdedbce47aa72c9f7f9f146b422236e9b9e23 Mon Sep 17 00:00:00 2001
From: Nicholas Vollmer 
Date: Thu, 13 Aug 2020 14:20:05 -0400
Subject: [PATCH] org-eldoc: (org-eldoc-documentation-function): set
 `eldoc-documentation-functions'

* contrib/lisp/org-eldoc.el (org-eldoc-documentation-function):

b2b587387 did not set eldoc-documentation-functions, resulting in
`eldoc--invoke-strategy' throwing a void-fucntion error.
---
 contrib/lisp/org-eldoc.el | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/contrib/lisp/org-eldoc.el b/contrib/lisp/org-eldoc.el
index aa1dcb41b..ce0b7ddc2 100644
--- a/contrib/lisp/org-eldoc.el
+++ b/contrib/lisp/org-eldoc.el
@@ -138,7 +138,8 @@
  (string= lang "emacs-lisp")
  (string= lang "elisp")) (if (fboundp 'elisp-eldoc-documentation-function)
  (elisp-eldoc-documentation-function)
-   (let (eldoc-documentation-function)
+   (let ((eldoc-documentation-functions
+	  '(elisp-eldoc-var-docstring elisp-eldoc-funcall)))
  (eldoc-print-current-symbol-info
((or
  (string= lang "c") ;; http://github.com/nflath/c-eldoc
-- 
2.28.0

Re: Bug: org agenda leader text "on-the-date" doesn't show for items with both SCHEDULED and DEADLINE properties [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]

[Russell Adams]

On Thu, Aug 13, 2020 at 06:13:09PM +0100, Dinnyés Dániel wrote:
> Any response regarding this? Was this registered? If so, Is there a link to
> track the bug status?

Dinnyés,

There is only the mailing list, there is no web based bug
tracker. These reports get attention as time permits. Developers
typically respond on the thread as that occurs. I'm just a helpful
guy. ;]

More below regarding your issue.

> > As stated earlier, the expected behaviour is that both leader/warning
> > texts are displayed on their appropriate line entry.

I can reproduce your issue on Emacs 27.1 and Org 9.3.7, however it's
the documented behavior. The SCHEDULED and DEADLINE keywords must be
on the first line after the TODO item. They are not like a PROPERTY
block with dynamic placement within the block.

Referring to the manual,
https://orgmode.org/manual/Deadlines-and-Scheduling.html

#+begin_quote
 A timestamp may be preceded by special keywords to facilitate
 planning. Both the timestamp and the keyword have to be positioned
 immediately after the task they refer to.
#+end_quote

Using C-c C-s (insert scheduled), and C-c C-d (insert deadline), Org
consistently appends them to the first line.

How did your org file have them on separate lines?

I agree that it may be slightly counter-intuitive to type manually,
but the tools provided add them correctly.

If the behavior bothers you, I'm certain everyone would welcome a
patch.

Finally, I've often wondered why Org hasn't migrated to using PROPERTY
drawers for all headline metadata. I suppose it's for legacy
compatibility. Perhaps you have an opinion there. I may start a thread
regarding that separately.

My sample file:

#+begin_src org
  ,* TODO EXAMPLE sched first
SCHEDULED: <2020-08-13 Thu>
DEADLINE: <2020-08-13 Thu>

  ,* TODO EXAMPLE1 dead first
DEADLINE: <2020-08-13 Thu>
SCHEDULED: <2020-08-13 Thu>

  ,* TODO EXAMPLE2 dead first, 1 line
  DEADLINE: <2020-08-13 Thu> SCHEDULED: <2020-08-13 Thu>

  ,* TODO EXAMPLE3 sched first, 1 line
  SCHEDULED: <2020-08-13 Thu> DEADLINE: <2020-08-13 Thu>

  ,* TODO EXAMPLE w/ props, 1 line
  SCHEDULED: <2020-08-13 Thu> DEADLINE: <2020-08-13 Thu>
  :PROPERTIES:
  :WUBBA:DUB DUB
  :END:
#+end_src

My sample agenda:

#+begin_example
  Week-agenda (W33):
  Monday 10 August 2020 W33
  Tuesday11 August 2020
  Wednesday  12 August 2020
  Thursday   13 August 2020
test:   Scheduled:  TODO EXAMPLE sched first
test:   Scheduled:  TODO EXAMPLE2 dead first, 1 line
test:   Scheduled:  TODO EXAMPLE3 sched first, 1 line
test:   Scheduled:  TODO EXAMPLE w/ props, 1 line
test:   Deadline:   TODO EXAMPLE1 dead first
test:   Deadline:   TODO EXAMPLE2 dead first, 1 line
test:   Deadline:   TODO EXAMPLE3 sched first, 1 line
test:   Deadline:   TODO EXAMPLE w/ props, 1 line
test:   TODO EXAMPLE sched first
test:   TODO EXAMPLE1 dead first
  Friday 14 August 2020
  Saturday   15 August 2020
  Sunday 16 August 2020
#+end_example

--
Russell Adamsrlad...@adamsinfoserv.com

PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/

Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

Re: Bug: org agenda leader text "on-the-date" doesn't show for items with both SCHEDULED and DEADLINE properties [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]

[Dinnyés Dániel]

Hi all,

Any response regarding this? Was this registered? If so, Is there a link to
track the bug status?

Cheers,
D.

On Mon, 10 Aug 2020 at 10:48, Dinnyés Dániel  wrote:

> --text follows this line--
>
> I am using factory default Emacs and Org-mode settings.
>
> I am using the following org todo item:
>
> #+BEGIN_SRC org
> * TODO EXAMPLE
>   SCHEDULED: <2020-08-09 Sun>
>   DEADLINE: <2020-08-09 Sun>
> #+END_SRC
>
> It is expected that on the date 2020-08-09 I will see 2 lines in my Org
> agenda: one with "Scheduled:" leader text, while the other with
> "Deadline:" leader text.
>
> What happens instead is that one of the lines show "Scheduled:" leader
> text, and the other line shows no leader text at all.
>
> Also, consider changing the order of the SCHEDULED and DEADLINE properties:
>
> #+BEGIN_SRC org
> * TODO EXAMPLE
>   DEADLINE: <2020-08-09 Sun>
>   SCHEDULED: <2020-08-09 Sun>
> #+END_SRC
>
> In this case it will be only the "Deadline:" leader text shown on one of
> the lines, while the other line shows no leader text at all.
>
> Therefore my assumption, is that somehow only the first of the
> properties is taken into account, while the property which comes second
> is ignored.
>
> As stated earlier, the expected behaviour is that both leader/warning
> texts are displayed on their appropriate line entry.
>
> Emacs  : GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.5)
>  of 2019-09-23, modified by Debian
> Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
> /usr/share/emacs/26.1/lisp/org/)
>

Re: window setup that works with org-agenda

[Eric S Fraga]

On Thursday, 13 Aug 2020 at 13:33, Xianwen Chen (陈贤文) wrote:
> I would like to receive tips regarding how to permanently set up the
> window layout that I have on my mind. The layout has three windows.

Have a look at this variable which may provide what you want:

,[ C-h v org-agenda-window-setup RET ]
| org-agenda-window-setup is a variable defined in ‘org-agenda.el’.
| Its value is ‘other-frame’
| Original value was ‘reorganize-frame’
| 
|   You can customize this variable.
| 
| Documentation:
| How the agenda buffer should be displayed.
| Possible values for this option are:
| 
| current-windowShow agenda in the current window, keeping all other 
windows.
| other-window  Use ‘switch-to-buffer-other-window’ to display agenda.
| only-window   Show agenda, deleting all other windows.
| reorganize-frame  Show only two windows on the current frame, the current
|   window and the agenda.
| other-frame   Use ‘switch-to-buffer-other-frame’ to display agenda.
|   Also, when exiting the agenda, kill that frame.
| See also the variable ‘org-agenda-restore-windows-after-quit’.
`

I have a new frame popup when I ask for an agenda view, leaving the
window setup for the original frame untouched.
-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-705-gea9463

Ical import in Emacs 27.1 core packages

[Russell Adams]

Hello Org-ers!

I've just upgraded to Emacs 27.1 and the latest Org
(9.3.7-18-g093b47-elpa). While reviewing my init.el I found I was
still depending on org-import-icalendar.el to import ics files.

The link on Worg for this file is broken, and I could not find a good
source. It's not in ELPA or MELPA, so I felt it was a dead end.

Instead I discovered that Emacs Gnus already has an icalendar importer
which includes some Org functions! I'm not sure when they were
introduced, but I wanted to share because it's a built-in.

In my init.el:

#+begin_src lisp
  
  ;; Ical

  ;; Import ical files
  (require 'gnus-icalendar)
  (add-to-list 'org-capture-templates
   '("#" "Ical capture target" plain
 (file "~/doc/OrgFiles/Agenda.org")
 "%i"
 :immediate-finish t :empty-lines 1))
  (setq gnus-icalendar-org-template-key "#")

  (defun rla-import-ical-to-org-capture (filename)
(with-temp-buffer
  (insert-file-contents filename)
  (gnus-icalendar:org-event-save
   (gnus-icalendar-event-from-buffer (current-buffer))
   nil)))
#+end_src

The key is to have a predefined org-capture template created for
Gnus. There is a function to create one for you, but I preferred to
make one by hand which is just a plain Org file with each new event
appended to the end of the file. The Agenda.org file is also in my
agenda list.

Then I added a simple wrapper function to import an external file into
a buffer for Gnus to save to Org. I think Gnus called it with a buffer
which already contained the ical attachment from the mail message it
was currently viewing.

Now in Mutt if I receive a calendar invite, I can use mailcap to
import it into Org.

#+begin_src text
  text/calendar; emacsclient -e '(rla-import-ical-to-org-capture "%s")' ; 
copiousoutput
  application/ics; emacsclient -e '(rla-import-ical-to-org-capture "%s")' ; 
copiousoutput
#+end_src

Please let me know if this works for anyone else. It may be worth
documenting on Worg.

--
Russell Adamsrlad...@adamsinfoserv.com

PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/

Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

window setup that works with org-agenda

[陈贤文]

Hi! 

I use both org mode and org-roam. 

org-roam opens a right-hand side window that displays backlinks. 

When I run org-agenda, the right window is closed automatically. 


I would like to receive tips regarding how to permanently set up the
window layout that I have on my mind. The layout has three windows. 


The right window, *c*, displays the backlinks from org-roam. The rest of
the space is divided in half, which I call them as the window *a* and
the window *b*. 

|-| 

|  a |   | 

|--|   c  | 

|  b |   | 

|-| 


When org-agenda displays agendas, it will not close *c* and it will not
resize *b*. It will display the agendas in the window *b*. 

Cheers, 


Xianwen

Re: Bug: org-table-sort-lines returns error [9.3.7 (release_9.3.7-705-gea9463 @ /home/oub/emacs/site-lisp/packages/org/)]

[Charles Millar]

On 8/13/20 8:03 AM, Uwe Brauer wrote:

"NG" == Nicolas Goaziou  writes:



Hello,
Uwe Brauer  writes:



I am running emacs 28 master 84ec57fe06e187f41a3546131d5dae3b185c3511

Steps to reproduce

#+TBLNAME: original
| Day   | Color | Level | Quantity |

|---+---+---+--|
| Monday| Red   |30 |   11 |
| Monday| Blue  |25 |3 |
| Tuesday   | Red   |51 |   12 |
| Tuesday   | Red   |45 |   15 |
| Tuesday   | Blue  |33 |   18 |
| Wednesday | Red   |27 |   23 |
| Wednesday | Blue  |12 |   16 |
| Wednesday | Blue  |15 |   15 |
| Thursday  | Red   |39 |   24 |
| Thursday  | Red   |41 |   29 |
| Thursday  | Red   |49 |   30 |
| Friday| Blue  | 7 |5 |
| Friday| Blue  | 6 |8 |
| Friday| Blue  |11 |9 |

Put curso on number 30 in the third column call the function and select
numercial sorting, a bug trace occurs which I attach.



I cannot reproduce it. I'm using neither Emacs 28 nor Org Ref, tho.



I run undo, widen and repeat the operation and then it works

   ^
???



You didn't say you were narrowing something.



Anyway, for the time being the error may come from Org Ref 
(org-ref-delete-labels).



I run more tests.
I upgraded org-ref

Still the following table gives me problems


#+TBLNAME: original
| Day   | Color | Level | Quantity |
|---+---+---+--|
| Tuesday   | Red   |51 |   12 |
| Thursday  | Red   |49 |   30 |
| Tuesday   | Red   |45 |   15 |
| Thursday  | Red   |41 |   29 |
| Thursday  | Red   |39 |   24 |
| Tuesday   | Blue  |33 |   18 |
| Monday| Red   |30 |   11 |
| Wednesday | Red   |27 |   23 |
| Monday| Blue  |25 |3 |
| Wednesday | Blue  |15 |   15 |
| Wednesday | Blue  |12 |   16 |
| Friday| Blue  |11 |9 |
| Friday| Blue  | 7 |5 |
| Friday| Blue  | 6 |8 |


While  this table



| Day   | Color | Level | Quantity |
|---+---+---+--|
| Tuesday   | Red   |51 |   12 |
| Thursday  | Red   |49 |   30 |
| Tuesday   | Red   |45 |   15 |
| Thursday  | Red   |41 |   29 |
| Thursday  | Red   |39 |   24 |
| Tuesday   | Blue  |33 |   18 |
| Monday| Red   |30 |   11 |
| Wednesday | Red   |27 |   23 |
| Monday| Blue  |25 |3 |
| Wednesday | Blue  |15 |   15 |
| Wednesday | Blue  |12 |   16 |
| Friday| Blue  |11 |9 |
| Friday| Blue  | 7 |5 |
| Friday| Blue  | 6 |8 |


Works fine. When I said it worked in the past I should also add, that I
usually did not use tablenames (labels)

@John I think this is your call?

Uwe

Two or three days ago when I started emacs it did not load correctly. ,I 
commented out my org-ref setup and no problem loading emacs.


Current set up
GNU Emacs 28.0.50 (build 214, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, 
cairo version 1.16.0) of 2020-08-13
Org mode version 9.3.7 (release_9.3.7-708-g5417e3 @ 
/usr/local/share/org-mode/lisp/)


I uncommented my org-ref setup in my init file and upon restarting the 
following error was generated:


Debugger entered--Lisp error: (void-variable browse-url-mosaic-program)

byte-code("\306\300!\203\n\0\10\206\13\0\307\310B\11\311B\n\312B\13\313B\f\314B\15\315B\16\26\316B\16\27\317B\16\30\320B\16\31\321B\16\32\322B\16\33..." 
[w3m-command browse-url-firefox-program helm-browse-url-chromium-program 
helm-browse-url-conkeror-program helm-browse-url-opera-program 
helm-browse-url-uzbl-program boundp "/usr/bin/w3m" w3m-browse-url 
browse-url-firefox helm-browse-url-chromium helm-browse-url-conkeror 
helm-browse-url-opera helm-browse-url-uzbl browse-url-kde 
browse-url-gnome-moz browse-url-mozilla browse-url-galeon 
browse-url-netscape browse-url-mosaic browse-url-text-xterm (("emacs" . 
eww-browse-url)) browse-url-kde-program browse-url-gnome-moz-program 
browse-url-mozilla-program browse-url-galeon-program 
browse-url-netscape-program browse-url-mosaic-program 
browse-url-xterm-program] 14)
  (defvar helm-browse-url-default-browser-alist (byte-code 
"\306\300!\203\n\0\10\206\13\0\307\310B\11\311B\n\312B\13\313B\f\314B\15\315B\16\26\316B\16\27\317B\16\30\320B\16\31\321B\16\32\322B\16\33..." 
[w3m-command browse-url-firefox-program helm-browse-url-chromium-program 
helm-browse-url-conkeror-program helm-browse-url-opera-program 
helm-browse-url-uzbl-program boundp "/usr/bin/w3m" w3m-browse-url 
browse-url-firefox helm-browse-url-chromium helm-browse-url-conkeror 
helm-browse-url-opera helm-browse-url-uzbl browse-url-kde 
browse-url-gnome-moz browse-url-mozilla browse-url-galeon 
browse-url-netscape browse-url-mosaic browse-url-text-xterm (("emacs" . 
eww-browse-url)) browse-url-kde-program browse-url-gnome-moz-p

Re: Bug: org-table-sort-lines returns error [9.3.7 (release_9.3.7-705-gea9463 @ /home/oub/emacs/site-lisp/packages/org/)]

[Uwe Brauer]

>>> "NG" == Nicolas Goaziou  writes:

> Hello,
> Uwe Brauer  writes:

>> I am running emacs 28 master 84ec57fe06e187f41a3546131d5dae3b185c3511
>> 
>> Steps to reproduce 
>> 
>> #+TBLNAME: original
>> | Day   | Color | Level | Quantity |
>> 
>> |---+---+---+--|
>> | Monday| Red   |30 |   11 |
>> | Monday| Blue  |25 |3 |
>> | Tuesday   | Red   |51 |   12 |
>> | Tuesday   | Red   |45 |   15 |
>> | Tuesday   | Blue  |33 |   18 |
>> | Wednesday | Red   |27 |   23 |
>> | Wednesday | Blue  |12 |   16 |
>> | Wednesday | Blue  |15 |   15 |
>> | Thursday  | Red   |39 |   24 |
>> | Thursday  | Red   |41 |   29 |
>> | Thursday  | Red   |49 |   30 |
>> | Friday| Blue  | 7 |5 |
>> | Friday| Blue  | 6 |8 |
>> | Friday| Blue  |11 |9 |
>> 
>> Put curso on number 30 in the third column call the function and select
>> numercial sorting, a bug trace occurs which I attach. 

> I cannot reproduce it. I'm using neither Emacs 28 nor Org Ref, tho.

>> I run undo, widen and repeat the operation and then it works 
>   ^
>???

> You didn't say you were narrowing something.

> Anyway, for the time being the error may come from Org Ref 
> (org-ref-delete-labels).


I run more tests.
I upgraded org-ref

Still the following table gives me problems


#+TBLNAME: original
| Day   | Color | Level | Quantity |
|---+---+---+--|
| Tuesday   | Red   |51 |   12 |
| Thursday  | Red   |49 |   30 |
| Tuesday   | Red   |45 |   15 |
| Thursday  | Red   |41 |   29 |
| Thursday  | Red   |39 |   24 |
| Tuesday   | Blue  |33 |   18 |
| Monday| Red   |30 |   11 |
| Wednesday | Red   |27 |   23 |
| Monday| Blue  |25 |3 |
| Wednesday | Blue  |15 |   15 |
| Wednesday | Blue  |12 |   16 |
| Friday| Blue  |11 |9 |
| Friday| Blue  | 7 |5 |
| Friday| Blue  | 6 |8 |


While  this table 



| Day   | Color | Level | Quantity |
|---+---+---+--|
| Tuesday   | Red   |51 |   12 |
| Thursday  | Red   |49 |   30 |
| Tuesday   | Red   |45 |   15 |
| Thursday  | Red   |41 |   29 |
| Thursday  | Red   |39 |   24 |
| Tuesday   | Blue  |33 |   18 |
| Monday| Red   |30 |   11 |
| Wednesday | Red   |27 |   23 |
| Monday| Blue  |25 |3 |
| Wednesday | Blue  |15 |   15 |
| Wednesday | Blue  |12 |   16 |
| Friday| Blue  |11 |9 |
| Friday| Blue  | 7 |5 |
| Friday| Blue  | 6 |8 |


Works fine. When I said it worked in the past I should also add, that I
usually did not use tablenames (labels)

@John I think this is your call?

Uwe 


smime.p7s
Description: S/MIME cryptographic signature

Re: Bug: org-table-sort-lines returns error [9.3.7 (release_9.3.7-705-gea9463 @ /home/oub/emacs/site-lisp/packages/org/)]

[Uwe Brauer]

>>> "NG" == Nicolas Goaziou  writes:

> Hello,
> Uwe Brauer  writes:

>> I am running emacs 28 master 84ec57fe06e187f41a3546131d5dae3b185c3511
>> 
>> Steps to reproduce 
>> 
>> #+TBLNAME: original
>> | Day   | Color | Level | Quantity |
>> 
>> |---+---+---+--|
>> | Monday| Red   |30 |   11 |
>> | Monday| Blue  |25 |3 |
>> | Tuesday   | Red   |51 |   12 |
>> | Tuesday   | Red   |45 |   15 |
>> | Tuesday   | Blue  |33 |   18 |
>> | Wednesday | Red   |27 |   23 |
>> | Wednesday | Blue  |12 |   16 |
>> | Wednesday | Blue  |15 |   15 |
>> | Thursday  | Red   |39 |   24 |
>> | Thursday  | Red   |41 |   29 |
>> | Thursday  | Red   |49 |   30 |
>> | Friday| Blue  | 7 |5 |
>> | Friday| Blue  | 6 |8 |
>> | Friday| Blue  |11 |9 |
>> 
>> Put curso on number 30 in the third column call the function and select
>> numercial sorting, a bug trace occurs which I attach. 

> I cannot reproduce it. I'm using neither Emacs 28 nor Org Ref, tho.

I tried it with emacs27 and obtained the same error

>> I run undo, widen and repeat the operation and then it works 
>   ^
>???

> You didn't say you were narrowing something.

I did not! The buffer got widen when I executed the command.


> Anyway, for the time being the error may come from Org Ref 
> (org-ref-delete-labels).

Very odd, but in earlier org version this problem did not occur.

@John, do you have any comments?

I will try to upgrade org-ref and if that does not help I will try to
bisect the problem compiling older org versions


smime.p7s
Description: S/MIME cryptographic signature

Re: org-caldav-sync hangs

[Eric S Fraga]

In your debug backtrace, the ID of the entry causing difficulties was
given.  Could you check out this entry to see if it is strange in some
way?  Maybe remove it (temporarily) from your org file and see if the
sync operation works?

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-705-gea9463

Re: Bug: Link descriptions include checkbox counter [9.3.7 (9.3.7-16-g521d7f-elpaplus @ /home/tarjei/.emacs.d/elpa/org-plus-contrib-20200803/)]

[Nicolas Goaziou]

Hello,

tarjei writes:

> Is it intended behavior for =org-store-link= to include checkboxcounters
> in the description? I would expect the example below to be
> =[[id:..][Link to this]]=, similarly to how TODO keywords are treated.
>
> #+begin_src org
> ,*** [1/2] Link to this
> :PROPERTIES:
> :ID:   129ed2c7-1ef2-4207-bb79-bfcec5fe6907
> :END:
> - [X] Done
> - [ ] Not done
>
> ,*** Other text
> And now the link, [[id:129ed2c7-1ef2-4207-bb79-bfcec5fe6907][[1/2] Link to 
> this]].
> #+end_src

I cannot reproduce it. You may want to try master branch.

Regards,
-- 
Nicolas Goaziou

Re: Bug: org-table-sort-lines returns error [9.3.7 (release_9.3.7-705-gea9463 @ /home/oub/emacs/site-lisp/packages/org/)]

[Nicolas Goaziou]

Hello,

Uwe Brauer  writes:

> I am running emacs 28 master 84ec57fe06e187f41a3546131d5dae3b185c3511
>
> Steps to reproduce 
>
>  #+TBLNAME: original
>  | Day   | Color | Level | Quantity |
>
>  |---+---+---+--|
>  | Monday| Red   |30 |   11 |
>  | Monday| Blue  |25 |3 |
>  | Tuesday   | Red   |51 |   12 |
>  | Tuesday   | Red   |45 |   15 |
>  | Tuesday   | Blue  |33 |   18 |
>  | Wednesday | Red   |27 |   23 |
>  | Wednesday | Blue  |12 |   16 |
>  | Wednesday | Blue  |15 |   15 |
>  | Thursday  | Red   |39 |   24 |
>  | Thursday  | Red   |41 |   29 |
>  | Thursday  | Red   |49 |   30 |
>  | Friday| Blue  | 7 |5 |
>  | Friday| Blue  | 6 |8 |
>  | Friday| Blue  |11 |9 |
>
> Put curso on number 30 in the third column call the function and select
> numercial sorting, a bug trace occurs which I attach. 

I cannot reproduce it. I'm using neither Emacs 28 nor Org Ref, tho.

> I run undo, widen and repeat the operation and then it works 
  ^
   ???

You didn't say you were narrowing something.

Anyway, for the time being the error may come from Org Ref 
(org-ref-delete-labels).

Regards,
-- 
Nicolas Goaziou

Re: org-caldav-sync hangs

[Robert Pluim]

> On Thu, 13 Aug 2020 11:00:34 +0200, "Loris Bennett" 
>  said:

Loris> Thanks for the suggestions.  Unfortunately all the relevant Org file
Loris> pass linting and regenerating .org-id-locations didn't help.

Loris> What I do occasionally see is this error:

Loris>   up-list: Scan error: "Unbalanced parentheses", 388, 126

Loris> However I don't even know whether this is coming from Org or not, so 
I
Loris> can't tell whether it is relevant.

(setq debug-on-message "Unbalanced parentheses")

Robert

Re: Markup border outdated in spec?

[Nicolas Goaziou]

Hello,

kim.lindber...@gmail.com writes:

> There seems to be an inconsistency between the Org syntax spec and the
> actual behavior regarding text markup: the spec forbids `,`, `'` and
> `"` in the border, yet it seems to work just fine to use them there in
> the current version of Org.

I updated the spec. Thank you.

Regards,
-- 
Nicolas Goaziou

Re: org-caldav-sync hangs

[Loris Bennett]

Hi Eric,

Eric S Fraga  writes:

> On Monday, 10 Aug 2020 at 14:47, Loris Bennett wrote:
>> The following used to work ca. 6-8 weeks ago to work and allow me to
>> synchronise events in an Org file with a calendar provided by a
>> Nextcloud instance:
>
> I had this problem in the past, or something similar.  I found that I
> had to run org-lint on all my relevant files.  Some of my files had the
> properties drawer in the wrong place (things have changed along the way
> with respect to where org expects these to be).  Once I fixed them,
> everything has worked smoothly.  I also use org-caldav-sync with a
> nextcloud instance.
>
> Just in case, and grasping at straws, another possibility may be that
> the file which keeps track of org IDs (~/.emacs.d/.org-id-locations on
> my system) has ended up inconsistent with your actual org files.  You
> may be able to delete that file (make a copy in case I'm wrong) and it
> should be re-generated.

Thanks for the suggestions.  Unfortunately all the relevant Org file
pass linting and regenerating .org-id-locations didn't help.

What I do occasionally see is this error:

  up-list: Scan error: "Unbalanced parentheses", 388, 126

However I don't even know whether this is coming from Org or not, so I
can't tell whether it is relevant.

Cheers,

Loris

-- 
This signature is currently under construction.