Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00507.html below:
Re: Emacs crash backtrace.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Po Lu Subject: Re: Emacs crash backtrace. Date: Wed, 09 Nov 2022 21:52:37 +0800 User-agent: Gnus/5.13 (Gnus v5.13)
Eli Zaretskii <eliz@gnu.org> writes:
> 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".
I made it display a large dialog box upon startup on X instead. But
that would be fine with me too.
- 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 <=
- 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