Re: [BUG] org-element-at-point: Throw an error when not in org-mode [9.7-pre (release_9.6.15-1033-gd8586f @ /home/marie/.emacs.d/straight/build/org/)]

2024-01-05 Thread Marie-Helene Burle
I see. That makes sense. Thank you very much for getting back to me with info. This is much appreciated! Marie Ihor Radchenko writes: > Marie-Helene Burle writes: > >> Prior to org 9.7, I used to use `org-meta-return` everywhere to nicely add >> elements to a list. Whether in mu4e, markdown

Re: [BUG] org-element-at-point: Throw an error when not in org-mode [9.7-pre (release_9.6.15-1033-gd8586f @ /home/marie/.emacs.d/straight/build/org/)]

2024-01-05 Thread Ihor Radchenko
Marie-Helene Burle writes: > Prior to org 9.7, I used to use `org-meta-return` everywhere to nicely add > elements to a list. Whether in mu4e, markdown, or anywhere, typing: > > - item1 > > Would nicely give me: > > - item1 > - > ... > So, indeed, not a bug and probably nothing you want to worr

Re: [BUG] org-element-at-point: Throw an error when not in org-mode [9.7-pre (release_9.6.15-1033-gd8586f @ /home/marie/.emacs.d/straight/build/org/)]

2024-01-05 Thread Marie-Helene Burle
Note: actually, reading that Reddit thread again, it appears that multiple persons were doing this and they regret loosing the use of org functions in non-org buffers so much that they decided to pin org to 9.6... Marie Marie-Helene Burle writes: > Hi Ihor, > > Thank you for your reply and yo

Re: [BUG] org-element-at-point: Throw an error when not in org-mode [9.7-pre (release_9.6.15-1033-gd8586f @ /home/marie/.emacs.d/straight/build/org/)]

2024-01-05 Thread Marie-Helene Burle
Hi Ihor, Thank you for your reply and your explanations: very useful to learn how the system works 🙂 Prior to org 9.7, I used to use `org-meta-return` everywhere to nicely add elements to a list. Whether in mu4e, markdown, or anywhere, typing: - item1 Would nicely give me: - item1 - Not a

[BUG] with scheduled event containing inactive timestamps

2024-01-05 Thread rameiko87
Create an org file named filename.org containing the following text: * TODO Org-agenda Bug Report Timestamp: [2024-01-04 Thu 15:15] SCHEDULED: <2024-01-05 Fri> Expected result: Friday 5 January 2024 filename: Scheduled: TODO Org-agenda Bug Report Timestamp: [2024-01-04 Thu 15:15]

Re: [PATCH] Set Python shell in Org edit buffer

2024-01-05 Thread Ihor Radchenko
Jack Kamm writes: >> python.el is convenient as it allows setting the session buffer name in >> advance via buffer-local variable. Then, all the normal python-mode >> commands, including `run-python' or `python-shell-send-region' will work >> as expected. However, other babel backends like ob-R d

Re: [PATCH] Set Python shell in Org edit buffer

2024-01-05 Thread Ihor Radchenko
Jack Kamm writes: >> Because I am still thinking about the idea with global customization and >> `org-babel--associate-session'. > > It's great that you're thinking about this -- it would be nice to have > better consistency between ob-R, ob-python, etc, and to have better > configurability on th

Re: Comments on Summary section of Org manual (was: [PATCH] doc/org-manual.org (Summary): Clarify the Org markup is human-readable)

2024-01-05 Thread Ihor Radchenko
Matt writes: > On Wed, 03 Jan 2024 14:41:29 +0100 Ihor Radchenko wrote --- > > > I do not see much benefit changing "todo list" to "to-do list". Both are > > clear and both are grammatically correct. > > I said "TODO" to "to-do". I was reacting to it being all caps. I'm sorry I > di

[PATCH v2] doc/org-manual.org (Summary): Clarify the Org markup is human-readable

2024-01-05 Thread Ihor Radchenko
Ihor Radchenko writes: > This is the first section of the manual. Most of the new users will see > it. So, I'd like to hear any objections before installing the patch. Thanks for the comments! I am attaching the next iteration of the patch. "Thomas S. Dye" writes: > How about this, assuming l

Re: [PATCH] ob-C.el compile-only header argument, was Re: How to use mpirun with C or C++ Org-babel?

2024-01-05 Thread Ihor Radchenko
Leo Butler writes: >> #+begin_src C :compile-only t :file foo :includes "stdio.h" >> printf("This is test"); >> #+end_src > > It should be "yes" not "t". I tested with :compile-only yes, but it did not change the observed issue. >> , executing should yield file link, even though it is not expli

Re: [BUG] Styles file and locale environment [9.6.13]

2024-01-05 Thread Ihor Radchenko
Hakan DaÄŸdelen writes: > This is too much work unfortunately, since I come around the problem by > calling terminal commands instead of built-in emacs functions. > > But I can say the problem is still reproducible on my system under Org > 9.6.15. The purpose of my query was to find out whether

Re: [BUG] simple documentation update [9.7-pre (release_9.6.11-923-g6f960f @ /Users/stephen/.emacs.d/straight/build/org/)]

2024-01-05 Thread Ihor Radchenko
"Stephen J. Eglen" writes: > Line 32 and 33 of org-id.el state: > > ;; Identifiers consist of a prefix (default "Org" given by the variable > ;; `org-id-prefix') ... > > I think that should now read: > > ;; Identifiers may consist of a prefix (given by the variable > ;; `org-id-prefix') ... > > a

Re: [BUG] org-element-at-point: Throw an error when not in org-mode [9.7-pre (release_9.6.15-1033-gd8586f @ /home/marie/.emacs.d/straight/build/org/)]

2024-01-05 Thread Ihor Radchenko
Marie-Helene Burle writes: > I suspect that this has already been reported as I saw it here: > https://www.mail-archive.com/emacs-elpa-diffs@gnu.org/msg102743.html. This is just a reference to the commit that introduced the explicit error. Do note that the error got downgraded to a warning in a

Re: Stripping captured journal entries

2024-01-05 Thread Michael Welle
Hi, "Loris Bennett" writes: > Hi, > > I capture journal entries such as > > * 2024-01 January > > ** 2024-01-03 Wednesday > > *** Did this > Added: [2024-01-03 Wed 10:35] > - foo > > *** Did that > Added: [2024-01-03 Wed 12:13] > - bar > > ** 2024-01-04 Thursday > > *