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

2024-01-03 Thread Matt
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 didn't say that. When

Re: [PATCH] Fix org-agenda-skip-scheduled-if-deadline-is-shown bug

2024-01-03 Thread Morgan Smith
Ihor Radchenko writes: > Morgan Smith writes: > >>> May you please provide a detailed reproducer demonstrating the bug you >>> are trying to fix? Such reproducer could be a basis of a new test. >> >> See a detailed reproducer attached to this mail. It has a task defined >> as this: >> >> *

Re: org table export to latex, longtable, code does not compile

2024-01-03 Thread Uwe Brauer
>>> "IR" == Ihor Radchenko writes: > Uwe Brauer writes: >> I am running emacs 29 and org mode 9.6.9 >> >> I have set (setq org-latex-line-break-safe "") >> ... >> Will be translated to >> >> #+begin_src >> >> \begin{longtable}{|r|r|l|l|l|l|l|} >> \hline >> Num & Documento &

Re: [PATCH] Re: Suggestion to add hook to be run when org-indent completes a buffer's initialization

2024-01-03 Thread Ihor Radchenko
dark.key8...@151e.ai writes: > Understood. Please find amended patch. Applied, onto main, with minor amendments. I capitalized all the sentences in commit message and added :package-version keyword to the `defcustom' definition.

Re: table of contents + export = Unable to resolve link

2024-01-03 Thread Ihor Radchenko
libreville writes: > if i create an org file with these three lines: > > * contents :TOC: > * a headline > * another > > org helpfully completes the table of contents for me: > > * contents :TOC: > - [[#a-headline][a headline]] > - [[#another][another]] May you please elaborate what you mean by

Re: [PATCH] Fix org-agenda-skip-scheduled-if-deadline-is-shown bug

2024-01-03 Thread Ihor Radchenko
Morgan Smith writes: >> May you please provide a detailed reproducer demonstrating the bug you >> are trying to fix? Such reproducer could be a basis of a new test. > > See a detailed reproducer attached to this mail. It has a task defined > as this: > > * TODO task > SCHEDULED: <2017-03-06 Mon

Re: [PATCH] org-babel-demarcate-block: split using org-element instead of regexp

2024-01-03 Thread Ihor Radchenko
gerard.vermeu...@posteo.net writes: > Attached you'll find a new patch trying to implement your suggestions. > Interactive splitting by demarcation seems to work quite well (see the > before and after splitting snippets in the PS). Thanks! > However, I cannot run the test because

Re: org table export to latex, longtable, code does not compile

2024-01-03 Thread Ihor Radchenko
Uwe Brauer writes: > I am running emacs 29 and org mode 9.6.9 > > I have set (setq org-latex-line-break-safe "") > ... > Will be translated to > > #+begin_src > > \begin{longtable}{|r|r|l|l|l|l|l|} > \hline > Num & Documento & \textit{26.04.2024} & \textit{29.04.2024} & >

Re: [PATCH v2] org-id: allow using parent's existing id in links to headlines

2024-01-03 Thread Ihor Radchenko
"Rick Lupton" writes: > Thanks for the comments. On this point, I'd like to modify > `org-insert-heading' to allow for choosing the level of the newly inserted > heading, but first wanted to check if you have a preference for how to change > it. > > > I think it would be simplest to change

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

2024-01-03 Thread Ihor Radchenko
Matt writes: > Several things in the first paragraph unrelated to your changes stick > out to me. I can't help but make some other remarks. > > "TODO" should probably be "to-do". Every dictionary I looked in has > an entry for "to-do". I think that's the common spelling. Yet, we consistently

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

2024-01-03 Thread Ihor Radchenko
Jean Louis writes: > In my opinion, it's not that Org was intentionally designed to be > "lightweight markup readable for humans"; rather, it was maintained in > a manner that focused on preserving its readability and prevented it > from evolving into something less comprehensible. The point of

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

2024-01-03 Thread Bastien Guerry
Jean Louis writes: > It's primary use was for Emacs users to make notes, TODO tasks, > etc. It is secondary that it became leightweight markup language that > can export to various documents. IMHO it has always been a _lightweight markup language_, used for notes and TODO tasks, then soon

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

2024-01-03 Thread Jean Louis
* Thomas S. Dye [2024-01-02 08:39]: > Aloha Ihor, > > Ihor Radchenko writes: > > > @@ -22,6 +22,10 @@ ** Summary > > It relies on a lightweight plain-text markup language used in files > > with the =.org= extension. > > +Org files can be viewed using any text editor. You can read and > >

table of contents + export = Unable to resolve link

2024-01-03 Thread libreville
hello, if i create an org file with these three lines: * contents :TOC: * a headline * another org helpfully completes the table of contents for me: * contents :TOC: - [[#a-headline][a headline]] - [[#another][another]] * a headline * another clicking on one of the links sends point to the