From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Heller Subject: Re: [OT] M-x not working anymore Date: Tue, 01 Feb 2011 13:46:10 -0800 Message-ID: <0vy65zig2l.fsf@gmail.com> References: <0vaaifk231.fsf@gmail.com> <87y65zpmuo.fsf@member.fsf.org> <0v39o7jzny.fsf@gmail.com> <4D486D19.9070801@ccbr.umn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=54239 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PkO7B-0005RJ-KS for emacs-orgmode@gnu.org; Tue, 01 Feb 2011 16:50:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PkO3N-0000wu-SO for emacs-orgmode@gnu.org; Tue, 01 Feb 2011 16:46:26 -0500 Received: from lo.gmane.org ([80.91.229.12]:57081) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PkO3N-0000wo-LU for emacs-orgmode@gnu.org; Tue, 01 Feb 2011 16:46:25 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PkO3J-0006tT-Uc for emacs-orgmode@gnu.org; Tue, 01 Feb 2011 22:46:21 +0100 Received: from 142.103.191.98 ([142.103.191.98]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 Feb 2011 22:46:21 +0100 Received: from hellerm2 by 142.103.191.98 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 Feb 2011 22:46:21 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Erik Iverson writes: > Markus Heller wrote: >> Tassilo Horn writes: >> >>> Markus Heller writes: >>> >>> Hi Markus, >>> >>>> M-x doesn't work anymore!! The M key works, e.g. M-w still does what >>>> it's supposed to if a region is active, and I can use ESC x instead. >>> What does C-h k M-x say? >> >> For C-h k M-x, it doesn't say anything. >> >> For C-h k ESC-x, it says the following: > > > > You should start emacs with the -q flag and see if it still > happens. Assuming M-x returns, comment out 1/2 of your .emacs > file and determine by binary search where the problem is. That might be a stupid question, but how do I do this under Win 7? I just double-click on runemacs.exe ... Markus