GNU bug report logs - #43888
28.0.50; emacsclient not working properly

Previous Next

Full log

Message #37 received at 43888 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: larsi <at> gnus.org, hajovonta <at> gmail.com, npostavs <at> gmail.com,
 43888 <at> debbugs.gnu.org
Subject: Re: bug#43888: 28.0.50; emacsclient not working properly
Date: Mon, 12 Oct 2020 17:50:31 +0300

> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: Gábor <hajovonta <at> gmail.com>,  larsi <at> gnus.org,
>   npostavs <at> gmail.com,
>   43888 <at> debbugs.gnu.org
> Date: Mon, 12 Oct 2020 07:58:27 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > > *ERROR*: Wrong number of arguments: (1 . 4), 5
> 
> > But since with "emacs -Q" it does work, it is still some of your
> > customizations that are the prime suspect.
> 
> Is there a way for the user to get an error message more verbose than
> above?

Yes, make sure debug-on-signal and debug-on-error are both non-nil in
the Emacs that runs the server, then you will have the backtrace pop
up in Emacs.  Assuming there's some frame visible for the server, that
is.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.