From: Ed Reingold <edward.reingold@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Old style backquotes warning
Date: Fri, 18 Mar 2011 09:20:10 -0700 (PDT) [thread overview]
Message-ID: <285598d7-24c4-4ebd-9680-e05a3a18d1be@n2g2000prj.googlegroups.com> (raw)
I have a macro definition in my .emacs that (now that I have switched
to 23.3) causes a warning
about old backquotes detected. How do I fix the macro? Here it is:
(defmacro squash (month day year time &optional court)
(backquote
(squash-internal (, month) (, day) (, year) (quote (, time)) (,
court))))
next reply other threads:[~2011-03-18 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 16:20 Ed Reingold [this message]
2011-03-18 20:51 ` Old style backquotes warning Drew Adams
2011-03-18 20:54 ` Drew Adams
[not found] ` <mailman.9.1300481525.31996.help-gnu-emacs@gnu.org>
2011-03-18 21:35 ` Ed Reingold
2011-03-22 14:27 ` Uday Reddy
2011-03-22 14:34 ` Uday Reddy
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=285598d7-24c4-4ebd-9680-e05a3a18d1be@n2g2000prj.googlegroups.com \
--to=edward.reingold@gmail.com \
--cc=help-gnu-emacs@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.
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).