Re: Org mode version 9.7-pre (9.7-pre-n/a-g093879

I think you're right. This request was prompted by an issue encounted in org-journal, and it probably exists in org-roam and other similar packages. Ignoring blank lines sounds like a reasonable approach. For more significant syntax violations such as your example, perhaps org-entry-get and

Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

Ihor Radchenko writes: >> I agree that it would be good to redesign it, but am not sure where to >> start. > > For example, > > 1. Change `org-babel-comint-async-register' to return UUID and to store >PARAMS as passed by the backend (current approach with PARAMS being >derived from src

Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

Bruno Barbier writes: > FWIW, I've been trying to use asynchronous blocks for everything, not > only the source blocks that are based on the comint mode. I think it > would be good if ob-core itself could provide an asynchronous API. I've > modified my Org so that it does have such an API.

Re: Async Python src block behavior with :dir header property

Ihor Radchenko writes: > +(defun org-babel-session-buffer ( info) > + "Return buffer name for session associated with current code block. > +Return nil when no such live buffer with process exists. > +When INFO is non-nil, it should be a list returned by > +`org-babel-get-src-block-info'. >

Re: help with gnus-icalendar.el and orgmode agenda

> <2024-02-22 18:30-20:00> is a valid timestamp. Agenda not handling it is > an oversight that should be fixed. Thanks for checking this. If the agenda could parse these, great. However, with a workaround (C-c C-c on the timestamp), I can handle this for now. Incidentally, org-lint says the

Re: Translation of the Org mode manual (was: Translation of manuals (was: SES manual French translation))

Richard Stallman writes: > Using Org format for the source of a document, and converting it to > texi for processing (for instance, through TeX) would be a fine method > to use, if it worked. But it doesn't actually work. > > The problem is that it cannot work, given Org format as it exists

Re: help with gnus-icalendar.el and orgmode agenda

"Stephen J. Eglen" writes: > When I use this package on icalendar attachments, it creates entries > that look like this: > > ... ><2024-02-22 18:30-20:00> > > Note that the timestamp DOES NOT include a day of the week. With the > default settings of org-time-stamp-formats, i.e. > >

help with gnus-icalendar.el and orgmode agenda

hi, I have the following snippet set up so that mu4e will parse icalendar attachments and add them to an org file ... this seems to be the standard prescription: (when (fboundp 'gnus-icalendar-org-setup) (setq gnus-icalendar-org-capture-file "~/todo.org") (setq

Question regarding org-capture-bookmark and org-bookmark-names-plist

Hi all, during last OrgMeetup, I proposed a new user option `org-refile-bookmark', similar to the already existing option `org-capture-bookmark'. Setting this new option to nil, `org-refile’ would not create a bookmark when refiling. (Use case: I am using alphapapa's org-bookmark-heading

Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

Ihor Radchenko writes: > Bruno Barbier writes: > >> While the execution is pending, I'm using the same technique that Org is >> using when a source block is being edited: the result is left untouched, >> but below an overlay. The overlay is used to know where to insert the >> result and to

Re: Bug: org-no-popups disregards display-buffer-fallback-action [9.4.6 (9.4.6-13-g4be129-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20210920/)]

+1! Ihor Radchenko writes: > I conclude that `org-no-popups' and `org-switch-to-buffer-other-window' > should not be used in Org mode. > > Fixed, on main. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=78dc58508 > > Other issues raised in this thread need more thought. --

Re: [BUG] Org may fetch remote content without asking user consent

Max Nikulin writes: > On 07/02/2024 23:12, Ihor Radchenko wrote: >> Max Nikulin writes: >> >>> #+setupfile: /dav:localhost#8000:/msg-123456.org > [...] >> I think we can enable checking for anything where `file-remote-p' >> returns non-nil. > ... In addition, TRAMP locations should be >

Re: Org mode version 9.7-pre (9.7-pre-n/a-g093879

Jason May writes: > Extraneous content (e.g. blank lines) in the PROPERTIES drawer > cause =org-entry-get= to return nil without indication of any problem. > > Desired behavior: =org-entry-get= should be forgiving. > It should ignore blank PROPERTIES lines, or any line with invalid > syntax. > A

Re: [BUG] Org element cache had to reset [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

Thanks, Ihor! I have upgraded Org and will send another bug report if I have further trouble. Thanks, Neil On Wed, Feb 7, 2024 at 11:28 AM Ihor Radchenko wrote: > Neil MacLaren writes: > > > What exactly did I do? > > > > I was trying to fix deadlines for repeating tasks in an org buffer by

Re: [BUG] Org may fetch remote content without asking user consent

On 07/02/2024 23:12, Ihor Radchenko wrote: Max Nikulin writes: #+setupfile: /dav:localhost#8000:/msg-123456.org [...] I think we can enable checking for anything where `file-remote-p' returns non-nil. It is a bit more tricky. Current file may be remote as well. Browsers have concept of

Re: [BUG] Org element cache had to reset [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

Neil MacLaren writes: > What exactly did I do? > > I was trying to fix deadlines for repeating tasks in an org buffer by hand. > I then tried to reload my Org Agenda and it wouldn't load. I tried pkill > -SIGUSR2 emacs but didn't understand the error messages. I narrowed the > problem down to a

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

Bastien Guerry writes: > Ihor Radchenko writes: > >> No response from Bastien. > > Yes, sorry for that. In general, don't wait for my answer unless you > really needed it: you've got pre-approval as co-maintainer, I don't > want my current lack of availability to be a blocker. No blocker here.

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

Hi Ihor, Ihor Radchenko writes: > No response from Bastien. Yes, sorry for that. In general, don't wait for my answer unless you really needed it: you've got pre-approval as co-maintainer, I don't want my current lack of availability to be a blocker. Thanks, -- Bastien Guerry

Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

Bruno Barbier writes: > FWIW, I've been trying to use asynchronous blocks for everything, not > only the source blocks that are based on the comint mode. I think it > would be good if ob-core itself could provide an asynchronous API. I've > modified my Org so that it does have such an API.

Re: [BUG] Org may fetch remote content without asking user consent

Max Nikulin writes: > Consider the following .org file: > > --- 8< --- > #+setupfile: /dav:localhost#8000:/msg-123456.org > --- >8 --- > > When Emacs opens it, HTTP server (plain HTTP, not WebDAV is used for > test) logs contain > ... > Emacs *Messages* buffer: > > Tramp: Opening connection for

Re: [BUG] Invalid capture datetree capture templates (newly introduced) [9.7-pre (release_9.6.18-1145-g10d286 @ /home/jds6696/.emacs.d/straight/build/org/)]

Justin Silverman writes: > I have been using the same capture templates for years now without problem. > Recently updated org and noticed a new bug. > > Example: the following capture template now produces an error: > let: Invalid capture target specification: (file+olp+datetree >

[BUG] Invalid capture datetree capture templates (newly introduced) [9.7-pre (release_9.6.18-1145-g10d286 @ /home/jds6696/.emacs.d/straight/build/org/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See Your bug report will be posted to the Org mailing list.

Re: [BUG] repeated warnings about org-element-at-point "cannot be used in non-Org buffer" [9.7 (9.7-??-57b94f3 @ /Users/cstevens/.emacs.d/.local/straight/build-29.2/org/)]

Thanks, I replaced org-cycle/org-global-cycle with outline-cycle/outline-cycle-buffer, and then the outlining works. On Tue, 6 Feb 2024 at 18:56, Ihor Radchenko wrote: > Daniel Clemente writes: > > > I also see the warnings. In my case it's because I'm using outline-minor > > mode in an elisp

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

Ihor Radchenko writes: > Right. This is because after 72c3f5e8e refactoring, > `org-agenda-skip-scheduled-if-deadline-is-shown' is only respected when > the deadline is actually shown. > > However, judging from the discussion of the original feature request >

[BUG] Org may fetch remote content without asking user consent

Consider the following .org file: --- 8< --- #+setupfile: /dav:localhost#8000:/msg-123456.org --- >8 --- When Emacs opens it, HTTP server (plain HTTP, not WebDAV is used for test) logs contain python3 -m http.server 8000 Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... 127.0.0.1