From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 13889@debbugs.gnu.org
Subject: bug#13889: lenient loading, feature request
Date: Thu, 15 Jul 2021 08:36:41 +0200 [thread overview]
Message-ID: <871r80nkw6.fsf@gnus.org> (raw)
In-Reply-To: <51378E07.2010705@easy-emacs.de> ("Andreas Röhler"'s message of "Wed, 06 Mar 2013 19:42:15 +0100")
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>> It might be a better idea to have a command that would continue
>> loading from where it stopped. This would allow the user to fix
>> manually whatever was broken, and then continue from there.
>
> Probably both is useful.
> Someone might face a deadline the very day.
> Emacs must work. No time to fix errors just now...
> Error must not be as simple as a missing parenthesis.
> Also imagine colleagues around, awaiting the result, wondering what
> the guy is doing ;)
Popping up the .emacs file with point where the error is would be more
helpful than the current:
---
Warning (initialization): An error occurred while loading ‘/home/larsi/.emacs’:
Invalid read syntax: ), 1, 0
---
I'm not sure how a general "continue loading" switch would work. It's
easy enough if there's a command that's erroring out -- we could ignore
the error and continue loading. But if it's a read-level error, then we
don't really know where to continue loading from.
I guess we could advance point by one character and try again in a loop
-- that'd usually get us past the error points after a while...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-15 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 16:42 bug#13889: lenient loading, feature request Andreas Röhler
2013-03-06 17:09 ` Eli Zaretskii
2013-03-06 18:42 ` Andreas Röhler
2021-07-15 6:36 ` Lars Ingebrigtsen [this message]
2021-07-15 6:56 ` Andreas Röhler
2021-07-15 7:08 ` Lars Ingebrigtsen
2021-07-15 7:25 ` Andreas Röhler
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=871r80nkw6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=13889@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).