From: Gregor Zattler <telegraph@gmx.net>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: bisected to commit since when this error occours (was: Re: isearch+ provoces error when starting eshell)
Date: Sun, 2 Jun 2013 22:45:01 +0200 [thread overview]
Message-ID: <20130602204501.GD27694@boo.workgroup> (raw)
In-Reply-To: <20130602134650.GA27694@boo.workgroup>
Hi Drew, Emacs developers,
* Gregor Zattler <telegraph@gmx.net> [02. Jun. 2013]:
>>> in emacs24 when isearch+ is loaded, starting eshell gives:
>>> byte-code: Key sequence C-c C-c starts with non-prefix key C-c
>>> and somehow freezes. It's possible to give a `ls' command but
>>> not twice.
>>>
>>> Minimal example:
>>> emacs-snapshot -Q -nw -l ~/.emacs.d/elpa/isearch+-20130513.1521/isearch+.el -f eshell
> I bisected the Emacs version history. Result is:
>
> ffc1d3e25cdae710e0f6057620af05c023a6e710 is the first bad commit
> commit ffc1d3e25cdae710e0f6057620af05c023a6e710
> Author: Glenn Morris <rgm@gnu.org>
> Date: Tue May 7 00:57:02 2013 -0700
>
> * lisp/eshell/em-hist.el (eshell-isearch-map): Initialize in the defvar.
> Remove explicit eshell-isearch-cancel-map.
>
> This commit changes the keymap for eshell. But I have no clue of
> elisp and therefore am not in the position to judge if the commit
> is wrong or if it exposes some bug in isearch+ or eshell.
FWIW I reverted this commit on top of newest Emacs trunk: It
compiles fine, the error is gone and some testing did not show
any side effects but since I do not understand the commits intend
I could not really test if something's now missing...
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
prev parent reply other threads:[~2013-06-02 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 22:22 isearch+ provoces error when starting eshell Gregor Zattler
2013-06-01 4:42 ` Drew Adams
2013-06-02 13:46 ` bisected to commit since when this error occours (was: Re: isearch+ provoces error when starting eshell) Gregor Zattler
2013-06-02 18:59 ` Drew Adams
2013-06-02 20:45 ` Gregor Zattler [this message]
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=20130602204501.GD27694@boo.workgroup \
--to=telegraph@gmx.net \
--cc=emacs-devel@gnu.org \
--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.
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.