Re: Is this proper time format?

Ihor Radchenko writes: > David Masterson writes: > >>> AFAIK, closed date intervals with time are currently not supported by >>> org-agenda. You can instead use diary sexp timestamps, a bunch of active >>> timestamps in the body, or M-x org-clone-subtree-with-time-shift >> >> "a bunch of active

Re: Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data

Thanks for the clarification. On 2023-06-08 13:17, Ihor Radchenko wrote: Note that we had some bugs in this area in older Org versions. I happen to have master from git://git.savannah.gnu.org/emacs.git checked out here. How recent is that w.r.t. "bleeding edge Org" from git://git.savannah.g

Re: mailto link issue in 9.5.5 and 9.6.6

On 6/8/23 11:47, Max Nikulin wrote: I decided that it is consistent with    nil("mailto:sran...@gmail.com"; (nil))    browse-url--mailto("mailto:sran...@gmail.com"; nil) when `browse-url-mailto-function' is set to nil. However docstring to this variable allows nil (perhaps there is really an

Re: mailto link issue in 9.5.5 and 9.6.6

On 07/06/2023 19:56, Ihor Radchenko wrote: Max Nikulin writes: It seems https://orgmode.org/worg/org-faq.html#mailto-links requires an update for Emacs-28 (besides a typo with "~" instead of "-"). May you elaborate? (Or, better, send a patch) The typo in https://orgmode.org/worg/org-faq.ht

Re: problem with org-map-entries and the doc for export hooks

"Victor A. Stoichita" writes: > I still see the problem with org version 9.6.6 and your latest example > code. > > I also checked with emacs -Q which has org version 9.6.1. > > I’m testing this on the attached file. Thanks for providing an example! You encountered a bug. Fixed, on bugfix. https

Re: org-latex-preview seems no to work for the \includegraphicscomm

>>> "T" == Timothy writes: Hi Timothy > Hi Uwe, Do you think you could see if the issue is gone with my > revamped-LaTeX-preview-WIP branch? (see > ) thanks for the quick reply, I am quite interested, since lately I had to write a lot o

Re: org-latex-preview seems no to work for the \includegraphicscomm

Hi Uwe, Do you think you could see if the issue is gone with my revamped-LaTeX-preview-WIP branch? (see ) > I am in a directory where the following line > \includegraphics[height=0.8\textheight,width=0.8\textwidth]{images/220px-Enigma_Ver

org-latex-preview seems no to work for the \includegraphicscomm

Hi I am in a directory where the following line \includegraphics[height=0.8\textheight,width=0.8\textwidth]{images/220px-Enigma_Verkehrshaus_Luzern_cropped.jpg} Can be successfully compiled. However in an org file org-latex-preview does not work for \includegraphics[height=0.8\texthe

Re: Org-Agenda view customization

Dieter Faulbaum writes: > I'm a little bit lost in the customize-group of org-agenda. > I'm looking for a variable to "blank" float entries like this: > <%%(diary-float t 4 2)> which is shown in the agenda view > (with org-agenda-remove-timeranges-from-blocks set to t), > because it's not really

Re: Marking task creation date or re-scheduling.

Vladimir Nikishkin writes: > Until recently, I used to just Schedule a task once, and it would stay > in the agenda until it is done. > > This has a nice property of having "Schedules x234 days" displayed near > the task in Agenda, so I know for how long this task has been hanging. > > However, o

Re: Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data

Farblos writes: > I like the idea of org-adapt-indentation being ´headline-data: > >When this variable is set to ‘headline-data’, Org only adapts the >indentation of the data lines right below the headline, such as >planning/clock lines and property/logbook drawers. > > However, I fin

Re: Org-Agenda view customization

Ihor Radchenko writes: Dieter Faulbaum writes: Is there a way to get rid of the part '<2023-06-06>--<2023-06-10>' in the agenda view (with the date entry in the same line in the org-file)? org-agenda-remove-timeranges-from-blocks Oh thanks Ihor, that does it! But I didn't find that var

Re: Parsing nested markup objects

Laith Bahodi writes: > Hi! I'm working on a parser for org and I noticed something about > nested markup in the syntax spec: markup starting at the limit of > another object seems like it shouldn't be interpreted as markup. The > spec says that the precondition characters are: > > PRE MARKER ...

Re: Parsing nested markup objects

Laith Bahodi writes: > Hi! I'm working on a parser for org and I noticed something about > nested markup in the syntax spec: markup starting at the limit of > another object seems like it shouldn't be interpreted as markup. The > spec says that the precondition characters are: > > PRE MARKER ...

Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data

I like the idea of org-adapt-indentation being ´headline-data: When this variable is set to ‘headline-data’, Org only adapts the indentation of the data lines right below the headline, such as planning/clock lines and property/logbook drawers. However, I find the resulting indentation beha

Re: Is this proper time format?

David Masterson writes: >> AFAIK, closed date intervals with time are currently not supported by >> org-agenda. You can instead use diary sexp timestamps, a bunch of active >> timestamps in the body, or M-x org-clone-subtree-with-time-shift > > "a bunch of active timestamps"?!? Ooh! I hadn't go

Parsing nested markup objects

Hi! I'm working on a parser for org and I noticed something about nested markup in the syntax spec: markup starting at the limit of another object seems like it shouldn't be interpreted as markup. The spec says that the precondition characters are: PRE MARKER ... PRE Either a whitespace characte