unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: larsi@gnus.org, hajovonta@gmail.com, npostavs@gmail.com,
	43888@debbugs.gnu.org
Subject: bug#43888: 28.0.50; emacsclient not working properly
Date: Mon, 12 Oct 2020 17:50:31 +0300	[thread overview]
Message-ID: <83zh4r33d4.fsf@gnu.org> (raw)
In-Reply-To: <87h7r0kmt8.fsf@web.de> (message from Michael Heerdegen on Mon, 12 Oct 2020 07:58:27 +0200)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Gábor <hajovonta@gmail.com>,  larsi@gnus.org,
>   npostavs@gmail.com,
>   43888@debbugs.gnu.org
> Date: Mon, 12 Oct 2020 07:58:27 +0200
> 
> Eli Zaretskii <eliz@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.





  reply	other threads:[~2020-10-12 14:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 18:25 bug#43888: 28.0.50; emacsclient not working properly Gábor
2020-10-09 19:35 ` Eli Zaretskii
2020-10-09 20:13   ` Lars Ingebrigtsen
2020-10-10 20:51 ` Lars Ingebrigtsen
2020-10-11 12:23   ` Noam Postavsky
2020-10-11 15:09     ` Gábor
2020-10-11 15:13       ` Gábor
2020-10-11 16:16       ` Eli Zaretskii
2020-10-11 19:44         ` Gábor
2020-10-12  5:58         ` Michael Heerdegen
2020-10-12 14:50           ` Eli Zaretskii [this message]
2020-10-13  7:17             ` Gábor
2020-10-13  7:30               ` Gábor
2020-10-13  7:36                 ` Gábor
2020-10-28 13:11                   ` Gábor
2020-10-28 13:52                     ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zh4r33d4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=43888@debbugs.gnu.org \
    --cc=hajovonta@gmail.com \
    --cc=larsi@gnus.org \
    --cc=michael_heerdegen@web.de \
    --cc=npostavs@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).