unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	 Vladimir Nikishkin <lockywolf@gmail.com>,
	 emacs-devel@gnu.org
Subject: Re: Emacs crash backtrace.
Date: Wed, 09 Nov 2022 21:05:07 +0800	[thread overview]
Message-ID: <87fses5ldo.fsf@yahoo.com> (raw)
In-Reply-To: <xjf35asxzh2.fsf@ma.sdf.org> (Andrea Corallo's message of "Wed, 09 Nov 2022 09:13:13 +0000")

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.



  parent reply	other threads:[~2022-11-09 13:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  5:59 Emacs crash backtrace Vladimir Nikishkin
2022-11-08 12:24 ` Po Lu
2022-11-08 13:13   ` Andrea Corallo
2022-11-08 13:42     ` Po Lu
2022-11-08 13:55       ` Andrea Corallo
2022-11-08 14:18       ` Stefan Monnier
2022-11-09  9:13         ` Andrea Corallo
2022-11-09 12:43           ` Eli Zaretskii
2022-11-09 13:52             ` Po Lu
2022-11-09 15:17             ` Andrea Corallo
2022-11-09 13:05           ` Po Lu [this message]
2022-11-09 15:17             ` Andrea Corallo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fses5ldo.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=akrl@sdf.org \
    --cc=emacs-devel@gnu.org \
    --cc=lockywolf@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).