Re: End of file during parsing

[Stephen Berman <stephen.berman@gmx.net>]

On Thu, 01 Aug 2024 12:33:31 -0400 aalinovi@riseup.net wrote:

> 'M-x check-parens' doesn't find any unmatched parentheses.
>
> Wouldn't this indicate that my problem lies elsewhere?

Probably.

> Also, if there is a problem with my init.el file, shouldn't I be getting
> this error everytime I start emacs and not only when I try to move/rename
> a file in dired?

It could be due to an error in a function called from your init file,
which wouldn't be triggered just by loading the init file.  But you can
start emacs with the command line flag --debug-init to get a backtrace
if loading your init file does raise an error.  But for the problem
you're having in Dired, it might help to check the item "Enter Debugger
on Error" in the Options menu; then when you invoke the Dired command
that raises the error, you should get a backtrace.  If you do and don't
see what the problem is, you could post the backtrace here and maybe
someone else will see the problem.  If you don't get a backtrace, the
next thing I would try is stepping through the source of the Dired
command with Edebug, but if you've never done that, you'll have to spend
some time learning how to use it; Edebug is documented in the Elisp
manual, (info "(elisp) Edebug").

Steve Berman

> Help appreciated.
>
> Thanks
> Arthur
>
>
> In message <874j849t2o.fsf@gmx.net>, Stephen Berman writes:
>>On Thu, 01 Aug 2024 10:55:15 -0400 Arthur Alinovi <aalinovi@riseup.net> wrote:
>>
>>> In trying to move/rename a file in dired I get "end of file during
>>> parsing".
>>>
>>> From what I've read I should then use parens-mode to track down an
>>> unmatched parentheses.
>>>
>>> Any hint would be appreciated.
>>
>>Try `M-x check-parens'.
>>
>>Steve Berman