unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Error: End of file during parsing
Date: Wed, 12 Oct 2022 00:26:12 +0200	[thread overview]
Message-ID: <87a6620zgb.fsf@dataswamp.org> (raw)
In-Reply-To: Y0W9aevCw7Aps4Le@protected.localdomain

Jean Louis wrote:

>>>>>> Try `M-x check-parens RET`
>>>>>
>>>>> That is good, thank you.
>>>> 
>>>> But nothing ever happens with that?
>>>
>>> Since then I have used it, it finds the place where
>>> parenthesis is missing.
>> 
>> Ah, I see now, you have to remove a paren (break the code)
>> for it to "work" :)
>
> check-parens finds the missing parenthesis, so it is other
> way around.

It can't, and it isn't :)

>>> It should also be involved in those error messages
>> 
>> Yes, sounds reasonable, I wonder tho if you can get "out
>> parsed" only by parenthesis mismatch or if there are other
>> ways to do that?
>> 
>>> to at least estimate
>> 
>> Estimate, that's how it works?
>
> When there is compiling process, then such fails without
> giving enough information. Instead of failing, process could
> use functions in check-parens to indicate where could be the
> problem in the code, and provide link for user to click on
> the link and quickly invoke check-parens
>
> I did not know that function exist. It is not enough
> integrated in Emacs.

Do it yourself, Jean :)

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-10-11 22:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  6:20 Error: End of file during parsing Jean Louis
2022-09-27  6:31 ` Emanuel Berg
2022-09-27 13:28   ` Emanuel Berg
2022-09-27  6:46 ` Eli Zaretskii
2022-09-27 10:37   ` Michael Heerdegen
2022-09-27 11:48     ` Gregory Heytings
2022-09-27 15:06       ` Michael Heerdegen
2022-09-27 11:50     ` Jean Louis
2022-09-27 15:44       ` Michael Heerdegen
2022-09-28 11:42       ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-03 23:35         ` Jean Louis
2022-10-04  1:41           ` Emanuel Berg
2022-10-10  6:08             ` Jean Louis
2022-10-10 23:24               ` Emanuel Berg
2022-10-11 19:00                 ` Jean Louis
2022-10-11 22:26                   ` Emanuel Berg [this message]
2022-10-12 13:14                     ` Jean Louis
2022-10-12 20:02                       ` Emanuel Berg
2022-10-15 14:28                         ` Alessandro Bertulli
2022-09-28  6:24 ` Christopher M. Miles

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6620zgb.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).