Re: EWW with Duck-Duck-Go

[email protected] Fri, 29 May 2026 14:29:52 -0400
Newsgroups gmane.emacs.help
Message-ID <[email protected]>
gfp <[email protected]> writes:

>
> Am 29.05.26 um 16:02 schrieb tpeplt:
>> gfp <[email protected]> writes:
>> 
>>>>
>>>>
>>> it did not find an expression that would try to open the "eww" buffer,
>>> but there were two other backtraces:
>>>
>>> 1.
>>>
>> ...
>>>
>>> 2.
>> 
>> If you have not done so already, then you should follow the
>> earlier step-by-step instructions, but you should *NOT*
>> evaluate the two expressions that are causing problems.  (I
>> suspect that no one will be able to use those two
>> expressions to diagnose the source of the problems.  Fixing
>> the problem likely will still have to wait until someone can
>> produce the steps to create the problem.)  After that, you
>> should be able to save your new, error-free, desktop
>> session, then shut down Emacs and restart it without any
>> problems.
>> 
>
> I had to evaluate the expressions as you said.
> So I tried all.
> How can I know which expression I should not evaluate?
>
>
> After folling the steps you proposed, I restarted emacs and the 
> backtrace concerning EWW did not come up. Even with this 2 backtraces 
> which came up earlier.
> But I have not used EWW yet.
> I will see if I am using EWW, if the problems appear again.
>

Yes, my suspicion about EWW was incorrect (although I have
seen a similar problem that was somehow connected to EWWW).
Based on what you reported, there are two buffers that
‘desktop’ cannot recover.  You will need to identify those
by using the information you posted earlier or by
reevaluating the expressions.  When you identify the two
that trigger the debugger, you will need to avoid those two.
What you are attempting to do is restore your desktop as it
was before you encountered this problem.

So,

  1. Evaluate your expressions in your (saved) desktop file.
  2. When you trigger the debugger, note which files/buffers
     those are, exit the debugger, and continue evaluating
     expressions until you either trigger it again or you
     reach the final expression.
  3. When you have evaluated the final expression, you
     should now have your Emacs session restored, with the
     exception for those files/buffers that triggered the
     debugger.  You will have to reload those files later,
     if they still interest you.
  4. You should then be able to M-x desktop-save
     This will create a new .emacs.desktop file, which you
     can test by exiting Emacs and restarting.  Because you
     have not recreated the buffers/files that were causing
     the debugger to be triggered, Emacs ought to start and
     restore your desktop session without any errors.

-- 
The lyf so short, the craft so long to lerne.
- Geoffrey Chaucer, The Parliament of Birds.