From: "Christopher M. Miles" <numbchild@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Error: End of file during parsing
Date: Wed, 28 Sep 2022 14:24:46 +0800 [thread overview]
Message-ID: <20572.548434005$1664346575@news.gmane.org> (raw)
In-Reply-To: <courier.0000000063329666.00002741@stw1.rcdrun.com>
[-- 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 --]
prev parent reply other threads:[~2022-09-28 6:24 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
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 [this message]
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='20572.548434005$1664346575@news.gmane.org' \
--to=numbchild@gmail.com \
--cc=bugs@gnu.support \
--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).