From: Boruch Baum <boruch_baum@gmx.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"Edward M. Reingold" <reingold@cs.uiuc.edu>,
32105@debbugs.gnu.org
Subject: bug#32105: 25.2; calendar-read-date should default to today [PATCH INCLUDED]
Date: Mon, 20 Jan 2020 23:19:40 -0500 [thread overview]
Message-ID: <20200121041940.d2nk5kojso5zgmdg@E15-2016.optimum.net> (raw)
In-Reply-To: <87zhehrjpd.fsf@marxist.se>
On 2020-01-20 20:50, Stefan Kangas wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
> > On 2019-06-24 22:42, Lars Ingebrigtsen wrote:
> >> I think just putting the current year in M-n is fine -- we don't have to
> >> mess with the history at all.
> >>
> >> That is, something conceptually like:
> >>
> >> (read-from-minibuffer "Year: " nil nil t nil "2019")
> >>
> >> Then 2019 is in M-n and can be edited, and just hitting RET will also
> >> return 2019.
> >
> > Reasonable.
>
> Just to follow up on this, since it was 7 months ago. Did you find
> the time to finish up this patch according to the comments by Lars?
> It sounds like a good addition to me.
I guess this is an example of how mis-communication retards progress. I
expressed approval with Lars' suggestion, but never said that I would be
the one to code it. Do you want to?
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2020-01-21 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 15:53 bug#32105: 25.2; calendar-read-date should default to today [PATCH INCLUDED] Boruch Baum
2019-06-24 15:24 ` Lars Ingebrigtsen
2019-06-24 16:52 ` Boruch Baum
2019-06-24 20:42 ` Lars Ingebrigtsen
2019-06-25 1:22 ` Boruch Baum
2020-01-20 19:50 ` Stefan Kangas
2020-01-21 4:19 ` Boruch Baum [this message]
2020-01-21 5:11 ` Stefan Kangas
2021-01-21 5:41 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200121041940.d2nk5kojso5zgmdg@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=32105@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=reingold@cs.uiuc.edu \
--cc=stefan@marxist.se \
/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.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).