[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: org-agenda-move-date-from-past-immediately-to-today could work for n
Re: org-agenda-move-date-from-past-immediately-to-today could work for non-days
Mon, 5 Jul 2021 16:51:41 -0700
i am referring to this code in org-agenda-date-later. i do not
understand why there is (equal arg 1):
(when (and org-agenda-move-date-from-past-immediately-to-today
(equal arg 1)
(or (not what) (eq what 'day))
(not (save-match-data (org-at-date-range-p))))
(setq cdate (org-parse-time-string (match-string 0) 'nodefault)
(list (nth 4 cdate) (nth 3 cdate) (nth 5 cdate)))
(when (> today cdate)
;; immediately shift to today
(setq arg (- today cdate))))
i would want to move to today if needed, then the number of days, such
as 7 here:
(defun alpha-org-agenda-do-date-later--week ()
but perhaps there is a good reason for restricting this variable to
controlling only a single day move?
On 6/20/21, Samuel Wales <firstname.lastname@example.org> wrote:
> org-agenda-move-date-from-past-immediately-to-today moves a ts
> immediately to today in agenda, but only if you do
> org-agenda-do-date-later by one day. if you instead do it by 7 days
> or so, it will check and not do the feature.
> i keep getting surprised by this, so i thought perhaps newcomers would
> be too. do you think it makes sense to drop that check and make the
> variable work consistently for all time periods? imo that would be
> the least surprising and most useful behavior.
> the drawbck of not dong so is that you take past scheduled, for
> example, and move them by weeks into the future, only to find out
> later that you moved them into the past. but perhaps others have
> different sensibilities and there is some reason for the check.
> The Kafka Pandemic
> Please learn what misopathy is.
The Kafka Pandemic
Please learn what misopathy is.
|[Prev in Thread]
||[Next in Thread]|
- Re: org-agenda-move-date-from-past-immediately-to-today could work for non-days,
Samuel Wales <=