[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs crash backtrace.
From: |
Po Lu |
Subject: |
Re: Emacs crash backtrace. |
Date: |
Wed, 09 Nov 2022 21:05:07 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Andrea Corallo <akrl@sdf.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Po Lu [2022-11-08 21:42:47] wrote:
>>> Andrea Corallo <akrl@sdf.org> writes:
>>>> not sure if this was discussed already but, shouldn't we warn the user
>>>> running an Emacs in such unsupported configuration?
>>> That's already done so, in NEWS and other associated documentation.
>>
>> I think Andrea was thinking of something more "in your face", like on
>> the splash screen or in the *scratch* buffer's initial text, or as
>> a `display-warning`, ...
>
> Exactly, if Emacs is not supposed to work properly in a certain
> configuration I believe we definitely should inform the user of this.
>
> Andrea
Sounds reasonable, now done.
- Emacs crash backtrace., Vladimir Nikishkin, 2022/11/08
- Re: Emacs crash backtrace., Po Lu, 2022/11/08
- Re: Emacs crash backtrace., Andrea Corallo, 2022/11/08
- Re: Emacs crash backtrace., Po Lu, 2022/11/08
- Re: Emacs crash backtrace., Andrea Corallo, 2022/11/08
- Re: Emacs crash backtrace., Stefan Monnier, 2022/11/08
- Re: Emacs crash backtrace., Andrea Corallo, 2022/11/09
- Re: Emacs crash backtrace., Eli Zaretskii, 2022/11/09
- Re: Emacs crash backtrace., Po Lu, 2022/11/09
- Re: Emacs crash backtrace., Andrea Corallo, 2022/11/09
- Re: Emacs crash backtrace.,
Po Lu <=
- Re: Emacs crash backtrace., Andrea Corallo, 2022/11/09