From: Richard Kim <Richard.Kim1@synopsys.com>
To: 30051@debbugs.gnu.org
Subject: bug#30051: Acknowledgement (27.0.50; diary-lib.el uses lexical scoping when dynamic scope is needed)
Date: Tue, 09 Jan 2018 13:15:18 -0800 [thread overview]
Message-ID: <qtma7xm68ex.fsf@synopsys.com> (raw)
In-Reply-To: <qtmd12i68so.fsf@synopsys.com>
I should have also mentioned that if I revert 2017/12/04 change of
diary-lib.el so that it goes back to using dynamic scoping (by removing
"-*- lexical-binding: t -*-" in the first line of the file), then I no
longer encounter the error I reported.
next prev parent reply other threads:[~2018-01-09 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 21:07 bug#30051: 27.0.50; diary-lib.el uses lexical scoping when dynamic scope is needed Richard Kim
2018-01-09 21:15 ` Richard Kim [this message]
2018-01-10 0:41 ` Glenn Morris
2018-01-10 19:27 ` 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=qtma7xm68ex.fsf@synopsys.com \
--to=richard.kim1@synopsys.com \
--cc=30051@debbugs.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.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).