help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to debug "Debugger entered--Lisp error: (void-function nil)"


From: newsspam5REMOVETHIS
Subject: Re: How to debug "Debugger entered--Lisp error: (void-function nil)"
Date: Mon, 09 Apr 2007 22:17:43 +0200
User-agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux)

Tim X <address@hidden> writes:
> address@hidden writes:
>
>> Tim X <address@hidden> 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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]