From: Eli Zaretskii <eliz@gnu.org>
To: "Shuguang Sun" <shuguang79@qq.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 41285@debbugs.gnu.org
Subject: bug#41285: 28.0.50; bibtex-Book not defined
Date: Sat, 16 May 2020 10:05:56 +0300 [thread overview]
Message-ID: <83wo5ctl4b.fsf@gnu.org> (raw)
In-Reply-To: <tencent_1AF895CE17D7C33965B2A281834C79E9BE09@qq.com> (shuguang79@qq.com)
> From: "Shuguang Sun" <shuguang79@qq.com>
> Date: Sat, 16 May 2020 10:22:43 +0800
>
> It looks like the enclosing of the defalias and lamba is wrong. The body of th lambda is enclosed in the document.
>
> Patch attached. Please review.
CC'ing Stefan, who made that change.
next prev parent reply other threads:[~2020-05-16 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 12:25 bug#41285: 28.0.50; bibtex-Book not defined Shuguang Sun
2020-05-16 2:22 ` Shuguang Sun
2020-05-16 7:05 ` Eli Zaretskii [this message]
2020-05-16 13:09 ` Stefan Monnier
2020-05-16 7:34 ` Andreas Schwab
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=83wo5ctl4b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41285@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=shuguang79@qq.com \
/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).