From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: ndame Newsgroups: gmane.emacs.help Subject: Re: Is there a reason why iinvalid-read-syntax doesn't give me the location of the error? Date: Wed, 7 Aug 2019 16:34:31 +0200 (CEST) Message-ID: References: <871rxxdqkn.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="208717"; mail-complaints-to="usenet@blaine.gmane.org" Cc: "help-gnu-emacs@gnu.org" To: Michael Heerdegen Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Aug 07 16:34:46 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hvN1Z-000sBN-Nj for geh-help-gnu-emacs@m.gmane.org; Wed, 07 Aug 2019 16:34:45 +0200 Original-Received: from localhost ([::1]:41904 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hvN1Y-000375-F2 for geh-help-gnu-emacs@m.gmane.org; Wed, 07 Aug 2019 10:34:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41524) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hvN1P-00036w-5t for help-gnu-emacs@gnu.org; Wed, 07 Aug 2019 10:34:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hvN1O-00065m-8P for help-gnu-emacs@gnu.org; Wed, 07 Aug 2019 10:34:35 -0400 Original-Received: from fmfe09.onbox.hu ([46.107.16.202]:31183 helo=web-out.onbox.hu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hvN1N-00064g-MG for help-gnu-emacs@gnu.org; Wed, 07 Aug 2019 10:34:34 -0400 X-fm-smtp-source: yes Original-Received: from localhost (localhost [188.143.64.145]) by web-out.onbox.hu (Postfix) with SMTP id 463YtH0gJ7znb; Wed, 7 Aug 2019 16:34:31 +0200 (CEST) In-Reply-To: <871rxxdqkn.fsf@web.de> X-AccountId: 57978162 X-Originating-Ip: 188.143.64.145 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduvddrudduvddgjeekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpucfhtffggffotefknfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvkfgjfhfugggtihffsegrtdersgdttddunecuhfhrohhmpehnuggrmhgvuceovghmrggtshhushgvrhesfhhrvggvmhgrihhlrdhhuheqnecukfhppedukeekrddugeefrdeigedrudegheenucfrrghrrghmpehhvghloheppdhinhgvthepudekkedrudegfedrieegrddugeehpdhmrghilhhfrhhomhepvghmrggtshhushgvrhesfhhrvggvmhgrihhlrdhhuhdprhgtphhtthhopehmihgthhgrvghlpghhvggvrhguvghgvghnseifvggsrdguvgenucevlhhushhtvghrufhiiigvpedt DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/relaxed; t=1565188471; s=20181004; d=freemail.hu; h=From:To:Cc:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Date; l=1301; bh=mfduP1KurcD2V989BV1d8DVmOUTCKS0r80xmT+6UeYk=; b=lRtxWBt3823qiwN3TUWqIproAgb/TN/b1AULGXIb8Vklsb3U2D5CPBca2SR1h6ob b2C5EB+vhvlhMafx1xsaHSeyDe8+XFfSzbnmR7FyaoxHBvR/2N02EMXptrKGwOlB+O/ YEnRsa90rXTf01MQzRu7CtTQ2gUd1V+6bjQ4Ad6+kTkmRc91qVbMZ9fs4iJDV1T2zZz Bhwc/MQPL/VJuO5GQltOkN7mKtlsIHh74QCXpRIDcPnjvXAanygki2ZYQ2mFabGkj7Y ux3z5cs4g2j+TQg38JLGufHZu/bCW0ZBh1qAKubCTZeu1d7xIJU+vdn6XeJqduYjHtK 3d5vMvDX5g== X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 46.107.16.202 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 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:121319 Archived-At: > I don't have the answer to your question, only a workaround: turn on > debug-on-error and eval. =C2=A0When the debugger pops up, switch to the > source code buffer. =C2=A0Point will be likely near the problem (AFAICT > `read' just leaves point where it gave up). Yes, thank you.=C2=A0 I was so baffled by invalid-read-syntax not printing the position like scan-error (I tried it with 26.2) that it did not occur to me to try it with debug enabled.