[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61658: 30.0.50; server-eval-at might handle unreadable results bette
From: |
Eli Zaretskii |
Subject: |
bug#61658: 30.0.50; server-eval-at might handle unreadable results better |
Date: |
Thu, 23 Feb 2023 19:42:07 +0200 |
> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: 61658@debbugs.gnu.org
> Date: Thu, 23 Feb 2023 10:27:11 -0700
>
> On Thu 23 Feb 2023 at 08:24AM +02, Eli Zaretskii wrote:
>
> > So you want server.el to catch the error and re-throw it with a
> > different signal in this particular case? Or am I misunderstanding?
>
> Yes, that's what I'd like to do.
But then just define-error isn't enough, is it?
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better, Sean Whitton, 2023/02/20
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better, Eli Zaretskii, 2023/02/20
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better, Sean Whitton, 2023/02/22
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better, Eli Zaretskii, 2023/02/22
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better, Sean Whitton, 2023/02/22
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better, Eli Zaretskii, 2023/02/23
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better, Sean Whitton, 2023/02/23
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better,
Eli Zaretskii <=
- bug#61658: 30.0.50; server-eval-at might handle unreadable results better, Sean Whitton, 2023/02/23