From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joost Kremers Newsgroups: gmane.emacs.help Subject: Re: better error messages in my *Messages* buffer? Date: 19 Mar 2014 19:25:03 GMT Message-ID: References: NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1395257117 8144 80.91.229.3 (19 Mar 2014 19:25:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Mar 2014 19:25:17 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Mar 19 20:25:25 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WQM74-0003QS-Mk for geh-help-gnu-emacs@m.gmane.org; Wed, 19 Mar 2014 20:25:18 +0100 Original-Received: from localhost ([::1]:43414 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQM74-0002QW-73 for geh-help-gnu-emacs@m.gmane.org; Wed, 19 Mar 2014 15:25:18 -0400 Original-Path: usenet.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 17 Original-X-Trace: individual.net 5SYYjq4aFsM2KRAh0SRu+QhT76cUyqkde9AoLSO0WZGtOpf161 Cancel-Lock: sha1:SXg2Vv9s8W4cL1nrXduUHtsMfE4= Mail-Copies-To: nobody X-Editor: Emacs of course! User-Agent: slrn/pre1.0.0-18 (Linux) Original-Xref: usenet.stanford.edu gnu.emacs.help:204367 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:96638 Archived-At: kleinerdrache@gmx.at wrote: > error in process filter: Wrong type argument: listp, [...] > > What do you do in that case to find out which line of your code creates > that error? `M-x toggle-debug-on-error is the first thing that comes to mind. Or do `M-x debug-on-entry RET RET'. Make sure the relevant functions are not byte-compiled. And read up on the debugger: (info "(elisp) Debugging") (info "(elisp) Debugger") -- Joost Kremers joostkremers@fastmail.fm Selbst in die Unterwelt dringt durch Spalten Licht EN:SiS(9)