[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs crash backtrace.

From: Eli Zaretskii
Subject: Re: Emacs crash backtrace.
Date: Wed, 09 Nov 2022 14:43:41 +0200

> From: Andrea Corallo <akrl@sdf.org>
> Cc: Po Lu <luangruo@yahoo.com>, Vladimir Nikishkin <lockywolf@gmail.com>,
>  emacs-devel@gnu.org
> Date: Wed, 09 Nov 2022 09:13:13 +0000
> 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.

Why not simply refuse to start in that case?  We could add a special
command-line option to override that, to leave users a "fire escape".

reply via email to

[Prev in Thread] Current Thread [Next in Thread]