From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Niessen <fni-news@pirilampo.org>
Cc: 16832@debbugs.gnu.org
Subject: bug#16832: 24.3.50; Emacs goes crazy when deleting lines
Date: Tue, 25 Feb 2014 18:26:42 +0200 [thread overview]
Message-ID: <831tyr17lp.fsf@gnu.org> (raw)
In-Reply-To: <86eh2r4ipj.fsf@somewhere.org>
> From: "Fabrice Niessen" <fni-news@pirilampo.org>
> Cc: 16832@debbugs.gnu.org
> Date: Tue, 25 Feb 2014 10:58:32 +0100
>
> > One thing to try is to set debug-on-quit to a non-nil value, repeat
> > the steps to reproduce the problem, then type C-g. If all goes well,
> > you should see a Lisp backtrace that might shed some light on this.
>
> Euh, that brought me once:
>
> --8<---------------cut here---------------start------------->8---
> Debugger entered--Lisp error: (quit)
> --8<---------------cut here---------------end--------------->8---
>
> Very disappointing in this case...
>
> On other trials, C-g stays unresponsive: nothing happens, I can type
> 10's of them in a row, and Emacs still does not react.
Then try F12 (if you are on XP), or try attaching a debugger and
getting a C and Lisp backtrace.
Thanks.
next prev parent reply other threads:[~2014-02-25 16:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 16:15 bug#16832: 24.3.50; Emacs goes crazy when deleting lines Fabrice Niessen
2014-02-21 17:07 ` Eli Zaretskii
[not found] ` <mailman.15712.1393002495.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.15712.1393002495.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-02-24 10:58 ` Fabrice Niessen
2014-02-24 16:28 ` Eli Zaretskii
[not found] ` <mailman.15925.1393259354.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.15925.1393259354.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-02-25 9:58 ` Fabrice Niessen
2014-02-25 16:26 ` Eli Zaretskii [this message]
[not found] ` <mailman.16008.1393345635.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.16008.1393345635.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-02-26 11:06 ` Fabrice Niessen
2014-02-26 19:02 ` Eli Zaretskii
[not found] ` <83txbly9xq.fsf-mXXj517/zsQ@public.gmane.org>
2014-02-26 19:42 ` Fabrice Niessen
2014-02-26 19:49 ` Eli Zaretskii
[not found] ` <mailman.16142.1393444275.10748.bug-gnu-emacs@gnu.org>
[not found] ` <86d2igl9x3.fsf-oHC15RC7JGTNLxjTenLetw@public.gmane.org>
2014-03-14 16:00 ` bug#16832: " Fabrice Niessen
2014-03-15 15:47 ` Eli Zaretskii
[not found] ` <83y50bbh01.fsf@gnu.org>
2014-03-15 16:17 ` Nicolas Goaziou
[not found] ` <87ob17sag9.fsf@gmail.com>
2014-03-15 17:36 ` Eli Zaretskii
[not found] ` <83wqfvbbzy.fsf@gnu.org>
2014-03-15 17:57 ` Nicolas Goaziou
[not found] ` <87ob17sag9.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-20 11:33 ` Fabrice Niessen
2014-03-17 14:57 ` Stefan
[not found] ` <jwvsiqg6fn6.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <jwvsiqg6fn6.fsf-monnier+emacsbugs-mXXj517/zsQ@public.gmane.org>
2014-03-17 21:29 ` Fabrice Niessen
2014-03-17 23:28 ` Stefan
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=831tyr17lp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16832@debbugs.gnu.org \
--cc=fni-news@pirilampo.org \
/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).