GNU bug report logs -
#13889
lenient loading, feature request
Previous Next
To reply to this bug, email your comments to 13889 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13889
; Package
emacs
.
(Wed, 06 Mar 2013 16:43:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Andreas Röhler <andreas.roehler <at> easy-emacs.de>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 06 Mar 2013 16:43:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi all,
when Emacs starts, sometimes it raises an error, for example if init loads a file where
paren didn't match when saved.
Unfortunately Emacs doesn't proceed than with loading the remaining stuff from init.
User might be left with a core Emacs.
Thus user is more or less compelled to look for the error, nonewithstanding of other tasks, also
sometimes that kind of error is hidden, it might take time to spot it.
Would welcome a feature "lenient loading", which signals the error, but goes on, tries to load the
remaining stuff from init.
Best regards,
Andreas Röhler
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13889
; Package
emacs
.
(Wed, 06 Mar 2013 17:11:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 13889 <at> debbugs.gnu.org (full text, mbox):
> Date: Wed, 06 Mar 2013 17:42:20 +0100
> From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
>
> Would welcome a feature "lenient loading", which signals the error, but goes on, tries to load the
> remaining stuff from init.
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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13889
; Package
emacs
.
(Wed, 06 Mar 2013 18:43:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 13889 <at> debbugs.gnu.org (full text, mbox):
Am 06.03.2013 18:09, schrieb Eli Zaretskii:
>> Date: Wed, 06 Mar 2013 17:42:20 +0100
>> From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
>>
>> Would welcome a feature "lenient loading", which signals the error, but goes on, tries to load the
>> remaining stuff from init.
>
> 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 ;)
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13889
; Package
emacs
.
(Thu, 15 Jul 2021 06:38:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 13889 <at> debbugs.gnu.org (full text, mbox):
Andreas Röhler <andreas.roehler <at> 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
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13889
; Package
emacs
.
(Thu, 15 Jul 2021 06:57:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 13889 <at> debbugs.gnu.org (full text, mbox):
On 15.07.21 08:36, Lars Ingebrigtsen wrote:
> Andreas Röhler <andreas.roehler <at> 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...
>
Thought at something like
(unwind-protect BODYFORM UNWINDFORMS...)
here as
(unwind-protect load-current load-remaining...)
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13889
; Package
emacs
.
(Thu, 15 Jul 2021 07:10:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 13889 <at> debbugs.gnu.org (full text, mbox):
Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:
> Thought at something like
>
> (unwind-protect BODYFORM UNWINDFORMS...)
>
> here as
>
> (unwind-protect load-current load-remaining...)
Now you just have to implement load-remaining (and load-current).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13889
; Package
emacs
.
(Thu, 15 Jul 2021 07:27:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 13889 <at> debbugs.gnu.org (full text, mbox):
On 15.07.21 09:08, Lars Ingebrigtsen wrote:
> Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:
>
>> Thought at something like
>>
>> (unwind-protect BODYFORM UNWINDFORMS...)
>>
>> here as
>>
>> (unwind-protect load-current load-remaining...)
> Now you just have to implement load-remaining (and load-current).
>
Yeah, that's why I appreciate Emacs :)
This bug report was last modified 3 years and 338 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.