[BUG] Parser error: Invalid search bound (wrong side of point) [9.7 (9.7-??-e90a8a69a @ /home/user/.emacs.d/.local/straight/build-29.1/org/)]

2023-10-17 Thread General discussions about Org-mode.
Hello,
I ran `C-c C-x C-l` to create a LaTeX preview of the following inline fragment 
in an Org document: $\text{CaCo}_3$, and this bug happened. This is my first 
bug report so let me know if anything else is necessary.
- Lorenzo



Emacs  : GNU Emacs 29.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, 
cairo version 1.16.0)
 of 2023-08-24
Package: Org mode version 9.7 (9.7-??-e90a8a69a @ 
/home/user/.emacs.d/.local/straight/build-29.1/org/)

current state:
==
(setq
 org-link-elisp-confirm-function nil
 org-cite-insert-processor 'citar
 org-after-refile-insert-hook '(save-buffer)
 org-indirect-buffer-display 'current-window
 org-crypt-key nil
 org-hide-emphasis-markers t
 org-bibtex-headline-format-function 'org-bibtex-headline-format-default
 org-load-hook '(+org-init-org-directory-h +org-init-appearance-h 
+org-init-agenda-h +org-init-attachments-h
                 +org-init-babel-h +org-init-babel-lazy-loader-h 
+org-init-capture-defaults-h +org-init-capture-frame-h
                 +org-init-custom-links-h +org-init-export-h +org-init-habit-h 
+org-init-hacks-h +org-init-keybinds-h
                 +org-init-popup-rules-h +org-init-smartparens-h)
 org-startup-folded t
 org-babel-after-execute-hook '(+org-redisplay-inline-images-in-babel-result-h)
 org-link-abbrev-alist '(("doomdir" . "/home/user/.doom.d/%s") ("emacsdir" . 
"/home/user/.emacs.d/%s")
                         ("doom-repo" . 
"https://github.com/doomemacs/doomemacs/%s;)
                         ("wolfram" . "https://wolframalpha.com/input/?i=%s;)
                         ("wikipedia" . "https://en.wikipedia.org/wiki/%s;) 
("duckduckgo" . "https://duckduckgo.com/?q=%s;)
                         ("gmap" . "https://maps.google.com/maps?q=%s;) 
("gimages" . "https://google.com/images?q=%s;)
                         ("google" . "https://google.com/search?q=;) ("youtube" 
. "https://youtube.com/watch?v=%s;)
                         ("github" . "https://github.com/%s;))
 org-agenda-files '("~/nextcloud-sync/todo.org")
 org-capture-templates '(("t" "Personal todo" entry (file+headline 
+org-capture-todo-file "Inbox") "* [ ] %?\n%i\n%a"
                          :prepend t)
                         ("n" "Personal notes" entry (file+headline 
+org-capture-notes-file "Inbox") "* %u %?\n%i\n%a"
                          :prepend t)
                         ("j" "Journal" entry (file+olp+datetree 
+org-capture-journal-file) "* %U %?\n%i\n%a" :prepend t)
                         ("p" "Templates for projects")
                         ("pt" "Project-local todo" entry (file+headline 
+org-capture-project-todo-file "Inbox")
                          "* TODO %?\n%i\n%a" :prepend t)
                         ("pn" "Project-local notes" entry (file+headline 
+org-capture-project-notes-file "Inbox")
                          "* %U %?\n%i\n%a" :prepend t)
                         ("pc" "Project-local changelog" entry
                          (file+headline +org-capture-project-changelog-file 
"Unreleased") "* %U %?\n%i\n%a" :prepend t)
                         ("o" "Centralized templates for projects")
                         ("ot" "Project todo" entry 
#'+org-capture-central-project-todo-file "* TODO %?\n %i\n %a" :heading
                          "Tasks" :prepend nil)
                         ("on" "Project notes" entry 
#'+org-capture-central-project-notes-file "* %U %?\n %i\n %a" :heading
                          "Notes" :prepend t)
                         ("oc" "Project changelog" entry 
#'+org-capture-central-project-changelog-file "* %U %?\n %i\n %a"
                          :heading "Changelog" :prepend t)
                         )
 org-persist-after-read-hook '(org-element--cache-persist-after-read)
 org-refile-targets '((nil :maxlevel . 3) (org-agenda-files :maxlevel . 3))
 org-export-before-parsing-hook '(org-attach-expand-links)
 org-cycle-tab-first-hook '(+org-yas-expand-maybe-h +org-indent-maybe-h 
org-babel-hide-result-toggle-maybe
                            org-babel-header-arg-expand 
+org-clear-babel-results-h +org-cycle-only-current-subtree-h)
 org-default-notes-file "/home/user/org/notes.org"
 org-auto-tangle-default t
 org-refile-use-outline-path 'file
 org-publish-timestamp-directory 
"/home/user/.emacs.d/.local/cache/org/timestamps/"
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-cite-follow-processor 'citar
 org-file-apps '((remote . emacs) (auto-mode . emacs) (directory . emacs) 
("\\.mm\\'" . default)
                 ("\\.x?html?\\'" . default) ("\\.pdf\\'" . default))
 org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
 org-ascii-format-drawer-function #[771 "\207" [] 4 "\n\n(fn NAME CONTENTS 
WIDTH)"]
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-show-empty-lines
                  org-cycle-optimize-window-after-visibility-change 
org-cycle-display-inline-images)
 

Re: [BUG] CI jobs do not appear to be running

2023-10-17 Thread Bastien Guerry
Hi Ihor,

Ihor Radchenko  writes:

> May you also check if new commits in Org repo still trigger the check?

New commits in Org repo don't trigger the checks directly.

Instead, there is a cron job running every three hours and running the
checks iff there are new commits.

> https://lists.sr.ht/~bzg/org-build-failures ran the tests right after
> ,
> but my recent Org commits did not trigger anything.

Perhaps your email was sent less than three hours after the last
checks (I didn't check).

Can you check again after the next commits?  The cron job on the
machine is configured correctly and should run.  I'll see what's 
wrong if it does not run.

Thanks!

-- 
 Bastien



Re: Consider removing newlines from org-insert-link help message

2023-10-17 Thread Salih Muhammed


> I am not sure. Your variant will be worse  on smaller screens
> or terminals, when the line wrap may look more ugly for longer line.

What about replacing it with shorter description?

"Insert a link. Use TAB for prefixes completion, RET for type-specific 
completion"

This is only 80 characters, should be suitable for small terminals.


--
Regards,
Salih



Re: org-notify: Need to get notifications at the start time of the task (in addition to the deadline)

2023-10-17 Thread Peter Münster
On Sun, Jun 05 2016, Amit Tendulkar wrote:

> I need a way to get notifications at the time of starting a task or at
> the start of the meeting (i.e. the SCHEDULED timestamp).

Hi Amit,

This should work now with the latest version (0.1.1) from ELPA.

Cheers,
-- 
   Peter


signature.asc
Description: PGP signature


Re: [SUMMARY] #3 [[bbb:OrgMeetup]] on Wed, Oct 11, 19:00 UTC+3

2023-10-17 Thread Eshel Yaron
Hello Ihor,

Ihor Radchenko  writes:

> - There was a demo demonstrating how to export texinfo manual to HTML
>   with source code examples fontified as in Org mode
>
>   - The motivation is limited Org support for manual authoring
> - ELPA, when generating manuals from Org sources, does not use the
>   latest Org version, with some features lacking.
> - While Org supports org to texi export, only a limited subset of
>   texinfo markup is supported, as Org is not specialized for
>   manuals and does not have a notion of specialized markup like
>   , , , etc
> - Also, Org does not yet support glossaries and indexes as well as
>   Texinfo does. Though see
>   https://github.com/tecosaur/org-glossary, which is an
>   experimental implementation by one of the Org contributors.
>
>   - One downside of texinfo is that code snippets are not colored
> - To solve this problem, https://github.com/hniksic/emacs-htmlize
>   and Org publishing are utilized
>   - The manual source is written in texi and then exported to html
> during publishing
>   - The generated HTML is further processed (via
> ~org-publish-after-publishing-hook~), taking the code in HTML,
> passing it through ~htmlize~ (just like what Org does in
> ~org-html-fontify-code~), and replacing the HTML code elements
> with property fontified versions.
>
> - Unfortunately, the code was only showed on screen and no link was
>   dropped to the chat. So, I am just leaving what I remember from
>   how the code works (above).

I presented that, sorry for not sharing a link.  You can find the code I
use for adding highlighting to Texinfo examples here:

http://git.eshelyaron.com/gitweb/?p=esy-publish.git;a=blob;f=esy-publish.el;h=cb103b78b7dd2f8d0f5260883b61bf651d0650f5;hb=HEAD#l394

Namely, the function `esy-publish-fontify-examples` takes the name of an
HTML-formatted Texinfo manual, and uses `htmlize` to markup the contents
of "example" blocks in that HTML file.

The result is very similar to the markup of source blocks in Org
documents.  For instance you can see some highlighted "examples" here:

https://eshelyaron.com/man/sweep/Numbered-Variables.html


Thank you for organizing this nice meetup!


Best,

Eshel



Re: Consider removing newlines from org-insert-link help message

2023-10-17 Thread Ihor Radchenko
Salih Muhammed  writes:

> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/lisp/ol.el#n1856
>
>   (insert "Insert a link.
> Use TAB to complete link prefixes, then RET for type-specific completion 
> support\n")
>
> This causes a stretch in the message buffer, which sometimes is being a
> little bit annoying, I'm advising org-link-insert personally because of
> it.
>
> Maybe merging it into one line:
>
>   (insert "Insert a link. Use TAB to complete link prefixes, then RET for 
> type-specific completion support\n")
>
> Will make it better.

I am not sure. Your variant will be worse  on smaller screens
or terminals, when the line wrap may look more ugly for longer line.

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



Re: Case insensitivity of simple [[links]]

2023-10-17 Thread Ihor Radchenko
Rudolf Adamkovič  writes:

> Ihor Radchenko  writes:
>
>> Note that there is generally no guarantee that [[name]] link will be
>> exported as "name" by any particular backend. Your workaround with
>> num:nil is just a workaround that may or may not work in future.
>
> I did not know this is considered a workaround!  I have always thought
> this is how Org is specified to work (as in tests).

Tests only cover (some) built-in backends. And they do not always test
documented features. AFAIK, text used when exporting fuzzy links without
description is not something we document. Individual backends are not
constrained to follow any specific convention in such scenario, although
built-in backends generally handle certain things similarly (often,
because they are used as a template for each other).

> One more question before I declare a full victory: I want my notebook to
> show literal links by default, but the following does not seem to work:
>
> # -*- fill-column: 79; org-link-descriptive: nil -*-
>
> The line seems to confuse Org in that not only it shows descriptive
> links but the first call to 'org-toggle-link-display' does nothing.

It does nothing because it is one of the options that must be set before
Org mode is loaded. Resolving buffer-local variables happens after the
major mode is loaded.

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



Re: Escape :end: inside #+begin_example

2023-10-17 Thread Ihor Radchenko
Max Nikulin  writes:

> is there a way to quote a drawer inside a literal example that resides 
> in another drawer? Leading comma ",:end:", unlike for ",* Heading" or 
> ",#+end_src", is not stripped on export or C-c ' (`org-edit-special')
>
> :drawer:
> #+begin_src elisp
>":src:
>%s
>:end:
>"
> #+end_src
> :end:

AFAIK, no. We should fix this.

>From a quick glance, we need to update
`org-element--unescape-substring', `org-escape-code-in-region',
`org-escape-code-in-string', `org-unescape-code-in-region', and
`org-unescape-code-in-string'.
Also, the manual, and org-syntax document.

I see no obvious downside in additional escaping, except lesser blocks
with ,:... lines.

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



Re: [BUG] CI jobs do not appear to be running

2023-10-17 Thread Ihor Radchenko
Bastien Guerry  writes:

> There was a problem with the oauth token not being able to interact
> with the (legacy) builds.sr.ht API.  I've updated the script so that
> it now uses the hut utility (see https://git.sr.ht/~emersion/hut) 
> and tests are running again.

Thanks!
May you also check if new commits in Org repo still trigger the check?
https://lists.sr.ht/~bzg/org-build-failures ran the tests right after
,
but my recent Org commits did not trigger anything.

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



Consider removing newlines from org-insert-link help message

2023-10-17 Thread Salih Muhammed


https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/lisp/ol.el#n1856

(insert "Insert a link.
Use TAB to complete link prefixes, then RET for type-specific completion 
support\n")

This causes a stretch in the message buffer, which sometimes is being a
little bit annoying, I'm advising org-link-insert personally because of
it.

Maybe merging it into one line:

(insert "Insert a link. Use TAB to complete link prefixes, then RET for 
type-specific completion support\n")

Will make it better.

--
Regards,
Salih