From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Don Woods Newsgroups: gmane.emacs.help Subject: Re: cannot disable paren matching Date: Tue, 27 Dec 2016 15:35:20 -0700 (MST) Message-ID: <201612272235.uBRMZKL1041301@home.icynic.com> References: NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1482878390 16632 195.159.176.226 (27 Dec 2016 22:39:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 27 Dec 2016 22:39:50 +0000 (UTC) Cc: don@icynic.com To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Dec 27 23:39:44 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cM0PG-0003Dw-T7 for geh-help-gnu-emacs@m.gmane.org; Tue, 27 Dec 2016 23:39:43 +0100 Original-Received: from localhost ([::1]:56526 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cM0PL-0003EX-Kk for geh-help-gnu-emacs@m.gmane.org; Tue, 27 Dec 2016 17:39:47 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40560) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cM0Ou-0003ER-T9 for help-gnu-emacs@gnu.org; Tue, 27 Dec 2016 17:39:21 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cM0Or-0000vA-K8 for help-gnu-emacs@gnu.org; Tue, 27 Dec 2016 17:39:20 -0500 Original-Received: from home.icynic.com ([75.148.112.132]:46953) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cM0Or-0000up-Co for help-gnu-emacs@gnu.org; Tue, 27 Dec 2016 17:39:17 -0500 Original-Received: from home.icynic.com (localhost [127.0.0.1]) by home.icynic.com (8.14.5/8.14.4) with ESMTP id uBRMZKPe041302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Dec 2016 15:35:20 -0700 (MST) (envelope-from don@home.icynic.com) Original-Received: (from don@localhost) by home.icynic.com (8.14.5/8.14.5/Submit) id uBRMZKL1041301; Tue, 27 Dec 2016 15:35:20 -0700 (MST) (envelope-from don) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 75.148.112.132 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:112012 Archived-At: Thanks John and Skip for the answers so far. I tried (show-paren-mode -1) and it seems to be the same as (show-paren-mode 0) in that it yields nil, whereas (show-paren-mode 1) yields t. I've also tried M-x show-paren-mode, which toggles the state. Interestingly, even in fundamental-mode, turning show-paren-mode off does NOT stop emacs from briefly moving to the matching open when I type a close, whether or not I'm in overwrite-mode. As to John's scenario starting with emacs -Q, I tried it on my emacs and ended with "a{b}c{d}r}" in the buffer, i.e. with two extra chars at the end due to the two occurrences of buggy behavior on close. I have emacs 24.2.1 on another system (unix not Mac, not that that should matter) and it shows the same bug. I guess I'll have to see if I can get 25 installed on either or both of those systems. Perhaps someone who has Emacs 24 installed can try John's scenario and shed further light? -- Don.