From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: John Mastro Newsgroups: gmane.emacs.help Subject: Re: cannot disable paren matching Date: Tue, 27 Dec 2016 13:30:24 -0800 Message-ID: References: <201612272029.uBRKTl39040819@home.icynic.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1482874281 12682 195.159.176.226 (27 Dec 2016 21:31:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 27 Dec 2016 21:31:21 +0000 (UTC) Cc: Don Woods 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 22:31:17 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 1cLzKy-0001yk-3i for geh-help-gnu-emacs@m.gmane.org; Tue, 27 Dec 2016 22:31:12 +0100 Original-Received: from localhost ([::1]:56379 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cLzL2-0000ni-RP for geh-help-gnu-emacs@m.gmane.org; Tue, 27 Dec 2016 16:31:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60200) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cLzKa-0000nV-Nw for help-gnu-emacs@gnu.org; Tue, 27 Dec 2016 16:30:49 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cLzKZ-0001Ki-Ld for help-gnu-emacs@gnu.org; Tue, 27 Dec 2016 16:30:48 -0500 Original-Received: from mail-qt0-x22d.google.com ([2607:f8b0:400d:c0d::22d]:33635) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cLzKZ-0001KU-Gu for help-gnu-emacs@gnu.org; Tue, 27 Dec 2016 16:30:47 -0500 Original-Received: by mail-qt0-x22d.google.com with SMTP id p16so333844159qta.0 for ; Tue, 27 Dec 2016 13:30:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hFTlofBabSlj+5kg/XwHIbE1o8noQLg8WTq8nZrBLfY=; b=AJ5LePRFb6ekRtUQ/IR9suFD6I55VlqN5TVc/cBycHkwnP1JNTusMZGS53Bu8yI3gs uz4CICVmdc2Ve2jjdxA4yejAW6gTFW3UKnA2ZxXtqB5L6s0LbXgIr6r2cwVbbNgp2HO9 3Ha76hXeQ3P5R1SreQYbAiGr8/Z9x0wP2STKKFV/LCFry4ROu74p2JUeUMlrxHB169iB Q8AJuZkFeoBNGVGg+Ihxf1nGet1IcZGaIuSMFV7F3JpwGEEeoLKTBRzFcDJbtozakquE dycusvmJ9eiwaySzk7a07H/j1WE8Wop5wUbsphQmFbF3+CERqqPhml9Ezp9PeEMmI8zS Nd4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hFTlofBabSlj+5kg/XwHIbE1o8noQLg8WTq8nZrBLfY=; b=JdCSNuM8OP4qeBU+CYGlTUUMtvKNCezxlvxIyR9ZI7yzJyqeAzRSD0ntcYWSSsIGR4 7JeNgmPPVpZ7S/bKu/IpldzOME8NuAwdXJ7yVQBggCdIrK2iUhyDlMmbGWvwynYdkC3w tEUJgzTsIpX7H8KCrxNhXnFKAVt/ou6OTjSidz2cG4/ONYdhwaWfivvmKIPQ4brPnaL2 P9MmixrSyUCRSrSZx8emz1VVG1PMuJhoxT4o9F7AzzEx/qYlfQra+kC4PYE4HQMPC7q8 jZKlOsbPE5M/3kBPR9581So1KXcrYEKoQRaz4uYXHUPdR05Q2k1CrqdbfQEySCQMJh3d ycZw== X-Gm-Message-State: AIkVDXLmpG71Bu+ILQYvjLqbcbij2iHfbInds526nMkB+BiwSR1/Ug/IREHjyqP++VKU5eop0wktQg2uBojkOg== X-Received: by 10.200.39.90 with SMTP id h26mr30218254qth.88.1482874245502; Tue, 27 Dec 2016 13:30:45 -0800 (PST) Original-Received: by 10.200.61.130 with HTTP; Tue, 27 Dec 2016 13:30:24 -0800 (PST) In-Reply-To: <201612272029.uBRKTl39040819@home.icynic.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400d:c0d::22d 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:112009 Archived-At: Don Woods wrote: > I am having a problem where paren matching is not working as desired, > and I am unable either to turn it off or to make it work correctly. > > The specific case where I'm having trouble is in PostScript mode, > when also in Overwrite mode. When I type a character that acts as a > close paren -- such as > or } -- the character is inserted instead of > overwriting the current char. Emacs briefly highlights the matching > open paren, or reports a mismatch, as the case may be, but does NOT > remove the char I was intending to overwrite. > > Since I don't especially need the paren highlighting in my current > editing, most of my attempts to work around this bug have involved > trying to disable the paren-matching behavior. I have tried such > things as > > (show-paren-mode 0) ;; no noticeable change > > (show-paren-mode nil) ;; no longer shows matching open > ;; but still does not overwrite > > (modify-syntax-entry ?> "w" ps-mode-syntax-table) > ;; > now highlights the char AFTER the matching < > ;; but still does not overwrite > (modify-syntax-entry ?< "w" ps-mode-syntax-table) > ;; when combined with previous, > goes back to > ;; showing matching <, but still does not overwrite > > I know I've tinkered with other paren-related vars without success, > but no longer recall everything I tried. > > My only successful workaround so far is to scrap postscript-mode and > use fundamental-mode. I'm using overwrite-mode while editing a portion > of the PostScript file that is a block of "ascii art" data, so don't > really need postscript-mode there, but it's awkward when switching > between the data and code portions of the file. > > Note: emacs-version is: > "GNU Emacs 22.1.1 (mac-apple-darwin) > of 2016-04-22 on osx143.apple.com" I'm not totally sure I understand the scenario, but I tried to reproduce this in Emacs 25 using the steps below and everything seemed to work as intended. Specifically, at the end of the steps, the buffer contained "a{b}c{d}". Here are the steps I tried: emacs -Q C-x b ps RET M-x ps-mode RET M-x show-paren-mode RET M-x overwrite-mode RET foo{bar} C-a a{b}c{d} If my recipe above would indeed trigger the problem you're describing, perhaps using a newer version of Emacs would do the trick - Emacs 22 is quite old (circa 2006 I believe). If the recipe above does not capture the problem, can you provide similar steps from "emacs -Q" that we can experiment with? John