From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Noam Postavsky 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 10:17:41 -0400 Message-ID: References: <871rxxdqkn.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="136161"; mail-complaints-to="usenet@blaine.gmane.org" Cc: "help-gnu-emacs@gnu.org" , ndame To: Michael Heerdegen Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Aug 07 16:18:09 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 1hvMlV-000ZIW-5n for geh-help-gnu-emacs@m.gmane.org; Wed, 07 Aug 2019 16:18:09 +0200 Original-Received: from localhost ([::1]:41706 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hvMlT-0001jB-LP for geh-help-gnu-emacs@m.gmane.org; Wed, 07 Aug 2019 10:18:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38072) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hvMlM-0001is-Tw for help-gnu-emacs@gnu.org; Wed, 07 Aug 2019 10:18:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hvMlM-0006D4-3C for help-gnu-emacs@gnu.org; Wed, 07 Aug 2019 10:18:00 -0400 Original-Received: from mail-ot1-x32c.google.com ([2607:f8b0:4864:20::32c]:36598) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hvMlL-0006Cd-SE for help-gnu-emacs@gnu.org; Wed, 07 Aug 2019 10:18:00 -0400 Original-Received: by mail-ot1-x32c.google.com with SMTP id r6so104876703oti.3 for ; Wed, 07 Aug 2019 07:17:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ATZTI2i3d/SNJjKhlMwBMq54FbKbSnZhXUaaUTcrKEo=; b=Zaq/YMTjZez5E4umTo3vCpLyPAw+HkHuu2RNU6iqnBjvlkQXmwgKwuZtHr5b889eSy IqfIojrm35NYpn2bXP32e/6S78vMzzc62iHGkgbrCjyhQha8JP6yvGlKsmn97Ke+VY1Z xnHA7c8F0PoQn5bzmX+yKh6ofcs+ObG0sjklfe3NvCK+PH/31MvTWweSXjzHBmOI094T zC3P3GuEqgsfWVEvJ5b3230eb1rUoeZXbHzQj/9NNIoNlELb6Ip3i9b/1KaCAa696kmI GohNJyhW2ylNBJ9RVhe+IhSc7zrj0qTZjs+yL9xlRZ4bhndyt+yAd0NlPc7QDE2Ipo68 QEBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ATZTI2i3d/SNJjKhlMwBMq54FbKbSnZhXUaaUTcrKEo=; b=fxkYCcLpHiwNZZmqlZTwoD1zX/RhBGMUJeS2aiJATUbP8sE9yVFLEKBqSJEEMpWzW7 HaEBslAZB3YZzxbgazTq2yJkxvEd3aU8IMoONAOPE1qGbjb5NZzpd8nP1tJBDCh/r2bz FttGBW/qSNupF8IdnonA1rkZPTBgCylT7s/XqiyFiNhlpWUE5aAuSNX7aYrMHt+QLdi1 k0iL467egzqucWFeQg6JvyYm05bFd0sDUJOSc6uTGaUueuWOOh+PUb5miIIw63hEdtCb z2VSeVxp7smlTdBZmqxk0OzcAIknfr1TGY3S0DNONICVfaSeDkETU31uQnld4qLRuK7h SdEQ== X-Gm-Message-State: APjAAAUsg15ZyHM7BBquazav12CCQZ8aigR+Kl8BQMsq/PC3twaJVPF6 Ht+VJp0JrzSGQIpl8pM0db0wHzUksKsQmnZnTaI= X-Google-Smtp-Source: APXvYqwXDqcnkKMVWBOXc1gPEPJjTm+RQ043T+ZoMpgxohwQTLn3fhGptmLJo6if296kFJ4z6AAKJHD3axVS84nDPag= X-Received: by 2002:a9d:6644:: with SMTP id q4mr8605607otm.308.1565187478532; Wed, 07 Aug 2019 07:17:58 -0700 (PDT) In-Reply-To: <871rxxdqkn.fsf@web.de> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::32c 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:121318 Archived-At: On Wed, 7 Aug 2019 at 09:59, Michael Heerdegen wrote: > > ndame writes: > > > I wonder why the error message doesn't give me the location of the > > error like scan-error. I have to bisect the file to find the bad part. > > I don't have the answer to your question, only a workaround: turn on > debug-on-error and eval. When the debugger pops up, switch to the > source code buffer. Point will be likely near the problem (AFAICT > `read' just leaves point where it gave up). The backtrace itself should mention the exact location where the last `read' was. In Emacs 27, you can click on it to jump there. See Bug#6435.