From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: hi@ypei.me, 50195@debbugs.gnu.org
Subject: bug#50195: [PATCH] Adding diary-offset, a diary-sexp offsetting another diary-sexp.
Date: Wed, 25 Aug 2021 15:24:54 +0300 [thread overview]
Message-ID: <83fsuxvhih.fsf@gnu.org> (raw)
In-Reply-To: <875yvtk9ud.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 25 Aug 2021 14:06:02 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Yuchen Pei <hi@ypei.me>, 50195@debbugs.gnu.org
> Date: Wed, 25 Aug 2021 14:06:02 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> + (with-no-warnings (defvar date) (defvar entry))
> >
> > Why did you need this?
>
> It's how all these functions in diary-lib are defined after the lexical
> rewrite -- the `eval' depends on those dynamic variables.
Ugh! Is it worth it? If we cannot convert these functions to use
lexical-binding, maybe we should say lexical-binding: nil in the first
line of the file, and remove all those gross kludges?
next prev parent reply other threads:[~2021-08-25 12:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 3:46 bug#50195: [PATCH] Adding diary-offset, a diary-sexp offsetting another diary-sexp Yuchen Pei
2021-08-25 11:31 ` Lars Ingebrigtsen
2021-08-25 11:52 ` Eli Zaretskii
2021-08-25 12:06 ` Lars Ingebrigtsen
2021-08-25 12:24 ` Eli Zaretskii [this message]
2021-08-25 12:38 ` Lars Ingebrigtsen
2021-08-25 15:22 ` Michael Heerdegen
2021-08-25 15:32 ` Michael Heerdegen
2021-08-25 16:07 ` Eli Zaretskii
2021-08-25 16:22 ` Michael Heerdegen
2021-08-26 6:52 ` Yuchen Pei
2021-08-26 9:26 ` Michael Heerdegen
2021-08-26 6:49 ` bug#50195: [PATCH] Adding diary-offset to diary-lib.el Yuchen Pei
2021-08-26 6:54 ` Yuchen Pei
2021-08-27 13:16 ` Yuchen Pei
2021-09-03 22:40 ` Yuchen Pei
2021-09-04 6:15 ` Eli Zaretskii
2021-09-04 6:29 ` Lars Ingebrigtsen
2021-09-04 7:21 ` Yuchen Pei
2021-08-26 10:26 ` bug#50195: [PATCH] Adding diary-offset, a diary-sexp offsetting another diary-sexp Michael Heerdegen
2021-08-27 13:11 ` Yuchen Pei
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fsuxvhih.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50195@debbugs.gnu.org \
--cc=hi@ypei.me \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.