From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Morgan Newsgroups: gmane.emacs.bugs Subject: bug#20521: setq-local definitely behaving oddly for viper mode Date: Wed, 27 May 2015 09:50:28 -0700 Message-ID: <0DBA2ACE64E8894F80DEC59F1EB9BE2304A3028A56A1@NXT-EXCH.nextlabs.com> References: <0DBA2ACE64E8894F80DEC59F1EB9BE23048E1E554241@NXT-EXCH.nextlabs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_0DBA2ACE64E8894F80DEC59F1EB9BE2304A3028A56A1NXTEXCHnext_" X-Trace: ger.gmane.org 1432745596 20828 80.91.229.3 (27 May 2015 16:53:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 27 May 2015 16:53:16 +0000 (UTC) To: "20521@debbugs.gnu.org" <20521@debbugs.gnu.org> Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed May 27 18:53:04 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 1YxeZi-0001yv-HW for geb-bug-gnu-emacs@m.gmane.org; Wed, 27 May 2015 18:53:02 +0200 Original-Received: from localhost ([::1]:54797 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxeZh-00014k-QX for geb-bug-gnu-emacs@m.gmane.org; Wed, 27 May 2015 12:53:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35388) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxeYF-0000cZ-Dr for bug-gnu-emacs@gnu.org; Wed, 27 May 2015 12:52:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YxeXn-0003Vn-OU for bug-gnu-emacs@gnu.org; Wed, 27 May 2015 12:51:31 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:48591) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxeXn-0003Vd-Go for bug-gnu-emacs@gnu.org; Wed, 27 May 2015 12:51:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YxeXm-0004hq-QS for bug-gnu-emacs@gnu.org; Wed, 27 May 2015 12:51:03 -0400 X-Loop: help-debbugs@gnu.org In-Reply-To: <0DBA2ACE64E8894F80DEC59F1EB9BE23048E1E554241@NXT-EXCH.nextlabs.com> Resent-From: Alan Morgan Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 27 May 2015 16:51:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20521 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 20521-submit@debbugs.gnu.org id=B20521.143274543818057 (code B ref 20521); Wed, 27 May 2015 16:51:02 +0000 Original-Received: (at 20521) by debbugs.gnu.org; 27 May 2015 16:50:38 +0000 Original-Received: from localhost ([127.0.0.1]:58566 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YxeXM-0004h9-BY for submit@debbugs.gnu.org; Wed, 27 May 2015 12:50:38 -0400 Original-Received: from mail1.bemta7.messagelabs.com ([216.82.254.108]:54086) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YxeXH-0004gz-Qi for 20521@debbugs.gnu.org; Wed, 27 May 2015 12:50:33 -0400 Original-Received: from [216.82.254.51] by server-12.bemta-7.messagelabs.com id 6B/D9-16335-6D5F5655; Wed, 27 May 2015 16:50:30 +0000 X-Env-Sender: Alan.Morgan@nextlabs.com X-Msg-Ref: server-11.tower-144.messagelabs.com!1432745429!11386579!1 X-Originating-IP: [173.167.112.114] X-StarScan-Received: X-StarScan-Version: 6.13.15; banners=nextlabs.com,-,- X-VirusChecked: Checked Original-Received: (qmail 12995 invoked from network); 27 May 2015 16:50:30 -0000 Original-Received: from customer.nextlabs.com (HELO mail.nextlabs.com) (173.167.112.114) by server-11.tower-144.messagelabs.com with AES128-SHA encrypted SMTP; 27 May 2015 16:50:30 -0000 Original-Received: from NXT-EXCH.nextlabs.com ([169.254.1.23]) by nxt-exchfe01.nextlabs.com ([10.187.2.93]) with mapi; Wed, 27 May 2015 09:50:29 -0700 Thread-Topic: setq-local definitely behaving oddly for viper mode Thread-Index: AdCYnJSNkridmpkoTNCdSpagcYUBAA== Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US 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:103231 Archived-At: --_000_0DBA2ACE64E8894F80DEC59F1EB9BE2304A3028A56A1NXTEXCHnext_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I must be going crazy. Here is my latest sanity check code in viper-check-= state in viper-cmd.el (when (eq (default-value 'viper-current-state) 'vi-state) (message "Doomed going in")) (setq-local viper-current-state new-state) (when (eq (default-value 'viper-current-state) 'vi-state) (message "Doomed. viper-current-state is now vi-state")) The setq-local replaces a simple setq at about line 380. When the problem = starts I see the "Doomed. Viper-current-state is now vi-state", but I do *= not* see the "Doomed going in" message. This implies that setq-local is se= tting the default value of the variable and that really shouldn't be possi= ble. Either I'm nuts or this is an emacs bug. --------------------------------------------------------------------- STATEMENT OF CONFIDENTIALITY =20 The information contained in this electronic message and any attachments t= o this message are intended for the exclusive use of the addressee(s) and = may contain confidential or privileged information. No representation is=20= made on its accuracy or completeness of the information contained in this = electronic message. Certain assumptions may have been made in the preparat= ion of this material as at this date, and are subject to change without no= tice. If you are not the intended recipient, you are hereby notified that = any dissemination, distribution or copying of this e-mail and any attachme= nt(s) is strictly prohibited. Please reply to the sender at NextLabs Inc a= nd destroy all copies of this message and any attachments from your system= . =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --_000_0DBA2ACE64E8894F80DEC59F1EB9BE2304A3028A56A1NXTEXCHnext_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I must= be going crazy. Here is my latest sanity check code in viper-check-state = in viper-cmd.el

 

  (when (eq (default-value 'viper-current-state) '= vi-state)

    (message &= quot;Doomed going in"))

 (se= tq-local viper-current-state new-state)

  (when (eq (default-value 'viper-current-state) 'vi-state)

    (message "Doomed. viper= -current-state is now vi-state"))

=  

The setq-local replaces a simple= setq at about line 380. When the problem starts I see the “Doomed. = Viper-current-state is now vi-state”, but I do *not* see the = “Doomed going in” message. This implies that setq-local is set= ting the default value of the variable and that really shouldn’t be = possible. Either I’m nuts or this is an emacs bug.

 


---------------------------------------------------------------------
= STATEMENT OF CONFIDENTIALITY

The information contained in this electronic message and any attachments t= o this message are intended for the exclusive use of the addressee(s) and = may contain confidential or privileged information. No representation is m= ade on its accuracy or completeness of the information contained in this e= lectronic message. Certain assumptions may have been made in the preparati= on of this material as at this date, and are subject to change without not= ice. If you are not the intended recipient, you are hereby notified that a= ny dissemination, distribution or copying of this e-mail and any attachmen= t(s) is strictly prohibited. Please reply to the sender at NextLabs Inc an= d destroy all copies of this message and any attachments from your system.= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--_000_0DBA2ACE64E8894F80DEC59F1EB9BE2304A3028A56A1NXTEXCHnext_--