From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kaushal Newsgroups: gmane.emacs.bugs Subject: bug#20532: 25.0.50; void-variable cursor-sensor-inhibit Date: Fri, 08 May 2015 18:10:35 +0000 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e014953a2e55c65051595f11b X-Trace: ger.gmane.org 1431108682 23684 80.91.229.3 (8 May 2015 18:11:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 May 2015 18:11:22 +0000 (UTC) Cc: 20532@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 08 20:11:13 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Yqmjv-0000RB-42 for geb-bug-gnu-emacs@m.gmane.org; Fri, 08 May 2015 20:11:11 +0200 Original-Received: from localhost ([::1]:57207 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yqmju-0006LC-GI for geb-bug-gnu-emacs@m.gmane.org; Fri, 08 May 2015 14:11:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34992) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yqmjq-0006L5-QV for bug-gnu-emacs@gnu.org; Fri, 08 May 2015 14:11:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yqmjn-0003Vw-Iu for bug-gnu-emacs@gnu.org; Fri, 08 May 2015 14:11:06 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:57266) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yqmjn-0003Vi-EG for bug-gnu-emacs@gnu.org; Fri, 08 May 2015 14:11:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Yqmjm-0005pa-R6 for bug-gnu-emacs@gnu.org; Fri, 08 May 2015 14:11:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Kaushal Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 08 May 2015 18:11:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20532 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 20532-submit@debbugs.gnu.org id=B20532.143110864522384 (code B ref 20532); Fri, 08 May 2015 18:11:02 +0000 Original-Received: (at 20532) by debbugs.gnu.org; 8 May 2015 18:10:45 +0000 Original-Received: from localhost ([127.0.0.1]:39008 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YqmjU-0005ow-2f for submit@debbugs.gnu.org; Fri, 08 May 2015 14:10:44 -0400 Original-Received: from mail-yk0-f175.google.com ([209.85.160.175]:34175) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YqmjR-0005oi-R8 for 20532@debbugs.gnu.org; Fri, 08 May 2015 14:10:42 -0400 Original-Received: by ykft189 with SMTP id t189so22463131ykf.1 for <20532@debbugs.gnu.org>; Fri, 08 May 2015 11:10:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=iikBmjbxWNHc2e//xbXiX7Ys+yKUgga+mLxZzv3PChY=; b=ZrG4XZkhwS2Cd4+U0tULMdNsfr9QeylKsNz4Vsp7SycfurCdJBuzlRfmbgJZVYC41H O91S9Abda4PBtwkADkm3P0SlgCV1SGOluvBxgsQN2U340tvWwYSZBhzyhwQi2b7f2uUs sHzHOB4mvYbP32CSYmHEY0v6CtyouiJAGqXV4AnCUeX0AS+dVEf98tOXjpRZKNFHDuEe jMZ3wx+s1NlMHv0PDrMePTnRgcs5JgLBPjLGlrwRV8doq0EfwaUv/1NwQYv9E93ut+O9 wIO6WBDeilY0ZznTbpxhUrscr6VjVgYhwiQ3KSLv9J9kC+eNLdUtR4auegZhgbk0sXH7 I8Gg== X-Received: by 10.236.26.43 with SMTP id b31mr4161986yha.53.1431108636202; Fri, 08 May 2015 11:10:36 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:102604 Archived-At: --089e014953a2e55c65051595f11b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > Can you think of any reason why you might have started your search in > one buffer and ended it in another? I hit C-' by mistake inbetween an isearch while in an org file and that called `org-cycle-agenda-files` and switched to a different org file while the search was active. I tried doing - C-s - search something that fails search / search something that has search hit= s - C-' (switch to a different org file) - C-g But that issue did not occur this time; isearch quit gracefully. > what kind of advice do you have on > call-interactively (in case it might interact in odd ways and ends up > changing the current buffer, for example)? Doing ag showed me that the ido-ubiquitous.el is advising that: (defadvice call-interactively (around ido-ubiquitous activate) "Implements the behavior specified in `ido-ubiquitous-command-overrides'.= " (let* ((cmd (ad-get-arg 0)) (override (ido-ubiquitous-get-command-override cmd))) (when override (ido-ubiquitous--debug-message "Using override `%s' for command `%s'" override cmd)) (ido-ubiquitous-with-override override ad-do-it))) I don't understand what it's doing in this advice though. On Fri, May 8, 2015 at 2:02 PM Stefan Monnier wrote: > > I get this error when I am trying to quit isearch. I don't know if this > > happens when I try to quit after I tried to search for a term that fail= ed > > to be found in the buffer or when I try to quit after a successful sear= ch > > hit. > > Hmmm... I can see 2 ways it could happen: > 1- isearch-done is called without having called isearch-mode earlier. > 2- isearch-done is called in a different buffer than the one in which > isearch-mode was called. > > I expect you're in case n=B02. > Can you think of any reason why you might have started your search in > one buffer and ended it in another? If not, maybe next time you bump > into it, try to figure what you've done in that search that might have > caused the buffer to be different at the end. > > > ad-Advice-call-interactively(# isearch-abort > nil nil) > > Obligatory side-question: what kind of advice do you have on > call-interactively (in case it might interact in odd ways and ends up > changing the current buffer, for example)? > > > Stefan > --089e014953a2e55c65051595f11b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
>=A0Can you think of any reason why you might have sta= rted your search in
> one buffer and ended it in another?=A0

I hit C-' by mistake inbetween an ise= arch while in an org file and that called `org-cycle-agenda-files` and swit= ched to a different org file while the search was active.
=
I tried doing=A0
- C-s
- search something that fails search / search something that has se= arch hits
- C-' (switch to a different org file)
- C-g

But that issue= did not occur this time; isearch quit gracefully.

>=A0what kind of advice do you have on> call-interactively (in case it might interact in odd ways and end= s up
> changing the current buffer, for example)?

=
Doing ag showed me that the ido-ubiquitous.el is advisin= g that:

(defadvice call-intera= ctively (around ido-ubiquitous activate)
=A0 "Implements the= behavior specified in `ido-ubiquitous-command-overrides'."
<= div>=A0 (let* ((cmd (ad-get-arg 0))
=A0 =A0 =A0 =A0 =A0(override = (ido-ubiquitous-get-command-override cmd)))
=A0 =A0 (when overrid= e
=A0 =A0 =A0 (ido-ubiquitous--debug-message "Using override= `%s' for command `%s'"
=A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0override cmd))
=A0= =A0 (ido-ubiquitous-with-override override
=A0 =A0 =A0 =A0 ad-do= -it)))

I don't understand what it's doin= g in this advice though.


On Fri, May 8, 2015 at 2:02 PM Stefan Monnier <monnier@iro.umontreal.ca> w= rote:
> I get this error when I am try= ing to quit isearch. I don't know if this
> happens when I try to quit after I tried to search for a term that fai= led
> to be found in the buffer or when I try to quit after a successful sea= rch
> hit.

Hmmm... I can see 2 ways it could happen:
1- isearch-done is called without having called isearch-mode earlier.
2- isearch-done is called in a different buffer than the one in which
=A0 =A0isearch-mode was called.

I expect you're in case n=B02.
Can you think of any reason why you might have started your search in
one buffer and ended it in another?=A0 If not, maybe next time you bump
into it, try to figure what you've done in that search that might have<= br> caused the buffer to be different at the end.

> ad-Advice-call-interactively(#<subr call-interactively> isearch-= abort nil nil)

Obligatory side-question: what kind of advice do you have on
call-interactively (in case it might interact in odd ways and ends up
changing the current buffer, for example)?


=A0 =A0 =A0 =A0 Stefan
--089e014953a2e55c65051595f11b--