emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-agenda for a day different than today
Date: Thu, 18 Feb 2021 00:32:14 -0500	[thread overview]
Message-ID: <87pn0y2b6p.fsf@kyleam.com> (raw)
In-Reply-To: <87eehft7gm.fsf@m4x.org>

Alan Schmitt writes:

> On 2021-02-16 23:01, Kyle Meyer <kyle@kyleam.com> writes:
>
[...]
>> Here are two threads from around that time that may be related, though I
>> haven't reviewed either of them:
>>
>>  https://orgmode.org/list/BLU0-SMTP912FC379760EE431D3D68EBBBC0@phx.gbl/T/#u
>>  https://orgmode.org/list/BLU0-SMTP950E9387B34FA390C4FD9CBBBD0@phx.gbl/T/#u
>>
>> Moving org-read-date back to the interactive form would allow lisp
>> callers to pass in the date, though perhaps it'd bring back some
>> misbehavior discussed in the above threads.
>
> I’ve tried this change here and it works great, thanks a lot.

Thanks for testing.

> Looking at the code, I don’t see how it could cause trouble elsewhere
> (but understanding agenda code is always tricky…)

Yeah, I too think it's safe.  If you have the time, I'd appreciate if
you could skim through the above threads and see if there are any
minimal examples or test cases.  If so, it be good to verify that they
still work with the patch.

> Should I file a bug regarding this?

Just this thread is fine.  I should find time to put together a proper
patch in the next couple of days.


  reply	other threads:[~2021-02-18  5:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 14:12 org-agenda for a day different than today Alan Schmitt
2021-02-17  4:01 ` Kyle Meyer
2021-02-17  8:38   ` Alan Schmitt
2021-02-18  5:32     ` Kyle Meyer [this message]
2021-02-18 16:41       ` Alan Schmitt
2021-02-21  6:23         ` Kyle Meyer
2021-02-21 15:42           ` Alan Schmitt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pn0y2b6p.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).