From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: newsspam5REMOVETHIS@robf.de Newsgroups: gmane.emacs.help Subject: Re: How to debug "Debugger entered--Lisp error: (void-function nil)" Date: Mon, 09 Apr 2007 22:17:43 +0200 Organization: (posted via) M-net Telekommunikations GmbH Message-ID: <85irc5715k.fsf@robf.de> References: <85abygg2j7.fsf@robf.de> <873b485mnw.fsf@lion.rapttech.com.au> <85veghufnk.fsf@robf.de> <878xdcq268.fsf@lion.rapttech.com.au> <85slbafxa3.fsf@robf.de> <87abxif7pe.fsf@lion.rapttech.com.au> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1176167892 22092 80.91.229.12 (10 Apr 2007 01:18:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 10 Apr 2007 01:18:12 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Apr 10 03:17:40 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Hb0cT-00017l-EF for geh-help-gnu-emacs@m.gmane.org; Mon, 09 Apr 2007 22:37:45 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hb0gK-0004jV-Ap for geh-help-gnu-emacs@m.gmane.org; Mon, 09 Apr 2007 16:41:44 -0400 Original-Path: shelby.stanford.edu!newshub.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed.cw.net!cw.net!news-FFM2.ecrc.de!news.m-online.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 66 Original-NNTP-Posting-Host: ppp-82-135-87-180.dynamic.mnet-online.de Original-X-Trace: svr7.m-online.net 1176149864 8954 82.135.87.180 (9 Apr 2007 20:17:44 GMT) Original-X-Complaints-To: abuse@m-online.net Original-NNTP-Posting-Date: Mon, 9 Apr 2007 20:17:44 +0000 (UTC) User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux) Cancel-Lock: sha1:yTo6z+suIrUvdIi/y4no6lnu+Qk= Original-Xref: shelby.stanford.edu gnu.emacs.help:146936 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:42541 Archived-At: Tim X writes: > newsspam5REMOVETHIS@robf.de writes: > >> Tim X writes: >>> BTW, there is also a gnu.emacs.vm.bug group that may be able to provide more >>> specific assistance. >> >> It is basically dead and if there is someone answering to bug >> reports, then it is usually me. ;-) >> >> I was using gnu.emacs.help as it seemed to be a GNU Emacs problem >> and not a VM problem to me. >> > > Just a few more suggestions - > > 1. Grab the vm package from debian unstable (I think it is 7.19-12 rather than > -11). This is the very latest version for Debian, but I don't think its been > put into testing yet. > > 2. You asked about other 'forks' of VM. I probably over stated things by saying > they were forks - more correctly, they are versions that have been somewhat > customized/patched rather than being apropper fork. I only realised just now > that one of them is your patched version you mailed me about a few months ago > when I was having problems with VM's handling of apple mail attachments (I > didn't recognise your name/e-mail). There is one other, which I think is also > by someone in Germany, but I cannot find the URL I thought I had. > > 3. You mentioned you are trying this by running vm from another account and > connecting to the account from your Xsession using xauthority to handle display > access etc. you also mentioned you tried it without running it from another > account to eliminate xauthority issues. Make sure that when you do the su to > run emacs, you are oding an su - username and not just an su. The - will ensure > your reading the propper init files for the remote account and that the shell > for the remote account is being correctly setup. You can get some 'subtle' > and difficult to track down problems with just an su rather than an su - > (though therre are plenty of times you actually want su and not su -_) A common > problem is incorrect home directory settings. With just su, the account you > have logged into will have your home dir setting, with su - it will have the > remote home setting. This can affect things such as the user mailbox location > and config files that are read etc. . > > 4. From your posts, it seems you are getting the problem only when trying to > run emacs with VM under X, but not if you use -nw. This is quite interesting > and a valuable clue. This would indicate the problem is with something emacs > does under X that it does not do under a console. Some possibilities may be > > - coding systems (I seem to remember one of the backtraces you posted, the one > with BYTE-CODE MODIFIED BY ME on one of the lines also had errors about > coding systems and remote pop mailboxes or similar). > > - fonts and images. Maybe its something to do with the VM toolbar > images/pixmaps? I don't use these and have that disabled in my .vm I here the alarm bells! With (setq vm-use-toolbar nil) in my ~/.vm it is gone ... Now after some more testing I found that the following in the item spec is causing the trouble: ':button '(:toggle nil) Many thanks for guiding me in finding this! Robert.