[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: |
Sean Whitton |
|
Subject: |
bug#61658: 30.0.50; server-eval-at might handle unreadable results better |
|
Date: |
Thu, 23 Feb 2023 10:27:11 -0700 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hello,
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.
--
Sean Whitton
- 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 <=
- 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