From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: 5f095f5 is the first bad commit (for my use case) Date: Thu, 28 Feb 2013 09:18:03 +0100 Message-ID: <86vc9c97ic.fsf@somewhere.org> References: <86hakzz746.fsf@somewhere.org> <87hakzqlg4.fsf@gmail.com> <86k3pu9mdr.fsf@somewhere.org> <87wqturuyo.fsf@gmail.com> <86haky3ukz.fsf@somewhere.org> <87obf51qma.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Aaron, Aaron Ecay wrote: > 2013ko otsailak 27an, Sebastien Vauban-ek idatzi zuen: >>=20 >> Do you know if there was a way out -- other than killing Emacs -- in suc= h a >> case where `C-g' is not working? > > If you are on Linux (or OS X, I suppose), you can sometimes break an > infloop by sending emacs the SIGUSR2 signal (in the shell, =E2=80=9Ckill = -USR2 > `pidof emacs`=E2=80=9D). This also generates a backtrace in the lisp deb= ugger, > which is useful for debugging. See C-h v debug-on-event . Thanks for the info! Best regards, Seb --=20 Sebastien Vauban