Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00441.html below:
Re: Emacs crash backtrace.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Stefan Monnier Subject: Re: Emacs crash backtrace. Date: Tue, 08 Nov 2022 09:18:21 -0500 User-agent: Gnus/5.13 (Gnus v5.13)
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`, ...
Stefan
- 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 <=
- 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, 2022/11/09
- Re: Emacs crash backtrace., Andrea Corallo, 2022/11/09
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4