Re: [PATCH] org-agenda: Make sure skipping warning/delay days never increases their number

On Tue, 2024-02-27 at 12:49 +, Ihor Radchenko wrote: > However, your total contributions are now at the limit we can legally > accept without FSF copyright assignment. > Would you consider doing copyright paperwork as described in > ? >

Re: [PATCH] org-agenda: Make sure skipping warning/delay days never increases their number

prewarning (org-get-wdays > > s > > +   (wdays (min max-wdays (org-get-wdays s > > warning-days > > > -   (suppress-delay > > +   (max-ddays > > max-deadline-warning-days > Done. Tim From 145b2526882264985d497ee0940

Re: [PATCH] org-agenda: Make sure skipping warning/delay days never increases their number

00 2001 From: Tim Ruffing Date: Tue, 13 Feb 2024 10:57:29 +0100 Subject: [PATCH] org-agenda: Make sure skipping warning/delay days never increases their number * lisp/org-agenda.el (org-agenda-get-deadlines, org-agenda-get-scheduled): Use minimum of warning/delay days specified in time

[PATCH] org-agenda: Make sure skipping warning/delay days never increases their number

or delay period, but never extend it. Best, Tim From 5db0ac7115b86a12d1a2106eb54b07d339f69ed6 Mon Sep 17 00:00:00 2001 From: Tim Ruffing Date: Tue, 13 Feb 2024 10:57:29 +0100 Subject: [PATCH] org-agenda: Make sure skipping warning/delay days never increases their number * lisp/org-agenda.el (org-agen

Re: [PATCH] Don't reset `org-todo-keywords-for-agenda' when org-agenda-multi

git send-email properly... Tim On Fri, 2023-03-10 at 19:32 +0700, Max Nikulin wrote: > On 10/03/2023 18:48, Ihor Radchenko wrote: > > Tim Ruffing writes: > > > > > * org-agenda.el (org-prepare-agenda): Don't reset > > > `org-todo-keywords-for-agenda' when org-a

Re: [PATCH] Don't reset `org-todo-keywords-for-agenda' when org-agenda-multi

-todo-keywords-for-agenda and (org-done-keywords-for-agenda) are not nil. Best, Tim On Fri, 2023-03-10 at 11:48 +, Ihor Radchenko wrote: > Tim Ruffing writes: > > > * org-agenda.el (org-prepare-agenda): Don't reset > > `org-todo-keywords-for-agenda' when org-agenda-mul

Re: [BUG] Date prompt suggests yesterday when changing timestamp with org-extend-today-until set [9.6]

Sorry for the late reply. The patch solves the problem for me, thanks! Would be great to have this fixed. On Sun, 2023-01-22 at 11:44 +, Ihor Radchenko wrote: > * This is test > SCHEDULED: <2023-01-28 Sat> > > Then, M-: (setq org-extend-today-until 20) > Then, C-c C-s on the heading above >

[PATCH] Don't reset `org-todo-keywords-for-agenda' when org-agenda-multi

* org-agenda.el (org-prepare-agenda): Don't reset `org-todo-keywords-for-agenda' when org-agenda-multi. Fixes a bug with TODO keywords that came to light in org-modern, see https://github.com/minad/org-modern/issues/26. This is very similar to cd2d138883a55cad48394a3f473da8b973a99a5e, which

[BUG] Date prompt suggests yesterday when changing timestamp with org-extend-today-until set [9.6]

Hi, Assume org-extend-today-until is set to an integer greater 0, say 3. When I change a timestamp without date such as <2023-01-20> (e.g, when rescheduling), the prompt defaults to a day earlier, i.e., to "2023-01- 19" in this case. The same happens with <2023-01-20 01:00> which is still before