From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Problem when run-hook-with-args with closure
Date: Fri, 19 Dec 2014 12:13:50 +0100 [thread overview]
Message-ID: <87r3vvnb81.fsf@web.de> (raw)
In-Reply-To: CAJnfWeHS5KoCXyqREVjZ3feqNz9dOfR7bTgaK4BcErPTfqjw3A@mail.gmail.com
Zhongwei Yao <ashi08104@gmail.com> writes:
> However, a problem
> (http://sourceforge.net/p/cedet/mailman/message/33153606/)
> in latest emacs (24.4.1) prevents me upgrading:(
I see. Have you made a bug report about that issue?
I don't use the related packages. Looking at the code, evaluating
something like this might help as a workaround:
(defalias 'hif-equal (hif-mathify-binop equal))
next prev parent reply other threads:[~2014-12-19 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 6:57 Problem when run-hook-with-args with closure Zhongwei Yao
2014-12-19 9:09 ` Michael Heerdegen
2014-12-19 9:56 ` Zhongwei Yao
2014-12-19 11:13 ` Michael Heerdegen [this message]
2014-12-19 9:10 ` Michael Heerdegen
2014-12-19 14:11 ` Stefan Monnier
2014-12-22 11:20 ` Zhongwei Yao
2014-12-22 19:07 ` incremental search for "OK " matches "OK" followed by ^M for CR !? ISHIKAWA,Chiaki
2014-12-22 19:10 ` Drew Adams
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=87r3vvnb81.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).