Error: End of file during parsing

Error: End of file during parsing

[Jean Louis]

This condition is terrible:

Compiling file /home/data1/protected/Programming/emacs-lisp/rcd-cf.el at Tue Sep 27 09:18:19 2022
rcd-cf.el: Error: End of file during parsing

If there is end of file during parsing, then why Emacs cannot tell me
at what line number it encountered error?


Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: Error: End of file during parsing

[Emanuel Berg]

Jean Louis wrote:

> If there is end of file during parsing, then why Emacs
> cannot tell me at what line number it encountered error?

And the answer is even more specific: at the end of the
last line.

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

Re: Error: End of file during parsing

[Eli Zaretskii]

> Date: Tue, 27 Sep 2022 09:20:34 +0300
> From: Jean Louis <bugs@gnu.support>
> 
> This condition is terrible:
> 
> Compiling file /home/data1/protected/Programming/emacs-lisp/rcd-cf.el at Tue Sep 27 09:18:19 2022
> rcd-cf.el: Error: End of file during parsing
> 
> If there is end of file during parsing, then why Emacs cannot tell me
> at what line number it encountered error?

It did tell you: the error is at EOF.  That's where Emacs realized
that there is an error.  It cannot do that earlier.

The problem is likely unbalanced parentheses somewhere.

Re: Error: End of file during parsing

[Michael Heerdegen]

Eli Zaretskii <eliz@gnu.org> writes:

> It did tell you: the error is at EOF.  That's where Emacs realized
> that there is an error.  It cannot do that earlier.
>
> The problem is likely unbalanced parentheses somewhere.

Yes, likely.

If a file contains N open parens and N+1 closing parens, or the other
way round, Emacs can't even know or conclude what the programmer
actually wanted to write.  This kind of problem requires some manual
error searching by the programmer.

Michael.

Re: Error: End of file during parsing

[Gregory Heytings]

>> It did tell you: the error is at EOF.  That's where Emacs realized that 
>> there is an error.  It cannot do that earlier.
>>
>> The problem is likely unbalanced parentheses somewhere.
>
> If a file contains N open parens and N+1 closing parens, or the other 
> way round, Emacs can't even know or conclude what the programmer 
> actually wanted to write.  This kind of problem requires some manual 
> error searching by the programmer.
>

If a file contains N open parens and N+1 closing parens, Emacs displays an 
error message pointing to the closing paren to which no opening paren 
corresponds.

If a file contains N+1 open parens and N closing parens, Emacs displays an 
"End of file during parsing" error message.  It could be a bit smarter, 
though: if one assumes that the file is properly indented, which is 
usually the case, whenever a parenthesis is read in column 1, the number 
of opening and closing parens must match.  IOW, Emacs could point to the 
first such place where this is not the case.  Such a hint would not be 
100% accurate, but would be helpful.

Re: Error: End of file during parsing

[Jean Louis]

* Michael Heerdegen <michael_heerdegen@web.de> [2022-09-27 13:57]:
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > It did tell you: the error is at EOF.  That's where Emacs realized
> > that there is an error.  It cannot do that earlier.
> >
> > The problem is likely unbalanced parentheses somewhere.
> 
> Yes, likely.
> 
> If a file contains N open parens and N+1 closing parens, or the other
> way round, Emacs can't even know or conclude what the programmer
> actually wanted to write.  This kind of problem requires some manual
> error searching by the programmer.

I am manually using the number guessing method:

- If there are 12000 lines, I go to middle of that one, like line
  6000, somewhere from there up or to bottom, I do M-x eval-region

- Then if there is failure, I go to half between x and 6000, if it is
  in bottom region I go to line 9000 and eval region from 9000 to
  12000;

- Then if problem is between 6000 - 9000, then I go to to half of it,
  to line 7500 and again verify 50% of region;

That way I arrive fastest to the location.

Could that same algorithm be used in Emacs for function to narrow it
to lines from X to Y?

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: Error: End of file during parsing

[Emanuel Berg]

Jean Louis wrote:

>> If there is end of file during parsing, then why Emacs
>> cannot tell me at what line number it encountered error?

And the answer is even more specific: at the end of the
last line.

Maybe also it should say unbalanced parens? But actually it
can also be e.g. a string that isn't closed.

E.g.,

  EOF during file persing (do you have unbalanced parens?)

Well, that would be the most likely in Lisp at least ...

But cannot this be fixed mechanically by just adding closing
parens (or the corresponding close char) until it's OK? Yes,
the balancing problem can, but it may still be incorrect
Elisp, e.g

((   (err msg "Containing expression ends prematurely")

damn

->

(()) (Symbol’s function definition is void: nil

rats

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

Re: Error: End of file during parsing

[Michael Heerdegen]

Gregory Heytings <gregory@heytings.org> writes:

> If a file contains N+1 open parens and N closing parens, Emacs
> displays an "End of file during parsing" error message.  It could be a
> bit smarter, though: if one assumes that the file is properly
> indented, which is usually the case, whenever a parenthesis is read in
> column 1, the number of opening and closing parens must match.  IOW,
> Emacs could point to the first such place where this is not the case.
> Such a hint would not be 100% accurate, but would be helpful.

Would be helpful, yes.  I'm not sure about the usually intact
indentation, though: sometimes when that happened to me indentation of
other top-level expressions had been messed up.  Can happen very quickly
once such an accident occurred.

Anyway - does that mean you think the compiler should do this?

Michael.

Re: Error: End of file during parsing

[Michael Heerdegen]

Jean Louis <bugs@gnu.support> writes:

> I am manually using the number guessing method:

Yes - that's what Gregory suggests: works but relies on intact
indentation of top-level expressions.

Michael.

Re: Error: End of file during parsing

[Christopher M. Miles]

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]


Is there Elisp helper code method to automatic this unbalanced
parenthesis searching?

Jean Louis <bugs@gnu.support> writes:

> This condition is terrible:
>
> Compiling file /home/data1/protected/Programming/emacs-lisp/rcd-cf.el at Tue Sep 27 09:18:19 2022
> rcd-cf.el: Error: End of file during parsing
>
> If there is end of file during parsing, then why Emacs cannot tell me
> at what line number it encountered error?
>
>
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> In support of Richard M. Stallman
> https://stallmansupport.org/


-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Error: End of file during parsing

[Stefan Monnier via Users list for the GNU Emacs text editor]

>> If a file contains N open parens and N+1 closing parens, or the other
>> way round, Emacs can't even know or conclude what the programmer
>> actually wanted to write.  This kind of problem requires some manual
>> error searching by the programmer.
>
> I am manually using the number guessing method:

Try `M-x check-parens RET`


        Stefan

Re: Error: End of file during parsing

[Jean Louis]

* Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2022-09-28 16:36]:
> >> If a file contains N open parens and N+1 closing parens, or the other
> >> way round, Emacs can't even know or conclude what the programmer
> >> actually wanted to write.  This kind of problem requires some manual
> >> error searching by the programmer.
> >
> > I am manually using the number guessing method:
> 
> Try `M-x check-parens RET`

That is good, thank you.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: Error: End of file during parsing

[Emanuel Berg]

Jean Louis wrote:

>>>> If a file contains N open parens and N+1 closing parens,
>>>> or the other way round, Emacs can't even know or conclude
>>>> what the programmer actually wanted to write. This kind
>>>> of problem requires some manual error searching by
>>>> the programmer.
>>>
>>> I am manually using the number guessing method:
>> 
>> Try `M-x check-parens RET`
>
> That is good, thank you.

But nothing ever happens with that?

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

Re: Error: End of file during parsing

[Jean Louis]

* Emanuel Berg <incal@dataswamp.org> [2022-10-06 11:59]:
> >> 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. 

It should also be involved in those error messages to at least
estimate where is the problem or provide link to quickly go to place
where parenthesis is missing.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: Error: End of file during parsing

[Emanuel Berg]

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" :)

> 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?

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

Re: Error: End of file during parsing

[Jean Louis]

* Emanuel Berg <incal@dataswamp.org> [2022-10-11 10:24]:
> 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 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.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: Error: End of file during parsing

[Emanuel Berg]

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

Re: Error: End of file during parsing

[Jean Louis]

* Emanuel Berg <incal@dataswamp.org> [2022-10-12 12:17]:
> > I did not know that function exist. It is not enough
> > integrated in Emacs.
> 
> Do it yourself, Jean :)

I have balls, but not kottbullar.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: Error: End of file during parsing

[Emanuel Berg]

Jean Louis wrote:

>>> I did not know that function exist. It is not enough
>>> integrated in Emacs.
>> 
>> Do it yourself, Jean :)
>
> I have balls, but not kottbullar.

So did Lance Armstrong ...

But he also had "Edgar" (EPO), additional testosterone and his
own blood re-injected into him at a later stage, and maybe
that's where Jean is lacking?

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

Re: Error: End of file during parsing

[Alessandro Bertulli]

>> I have balls, but not kottbullar.
>
> So did Lance Armstrong ...
>
> But he also had "Edgar" (EPO), additional testosterone and his
> own blood re-injected into him at a later stage, and maybe
> that's where Jean is lacking?

... I really can't follow your point guys.

-- 
Alessandro Bertulli