From: Stefan Kangas <stefan@marxist.se>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 24616@debbugs.gnu.org,
"Clément Pit--Claudel" <clement.pit@gmail.com>,
"Noam Postavsky" <npostavs@users.sourceforge.net>
Subject: bug#24616: 26.0.50; No backtrace when emacsclient --eval fails
Date: Tue, 19 Nov 2019 15:31:15 +0100 [thread overview]
Message-ID: <CADwFkmk55A+VR3fnBTpcnJt4+xR9cEfbr_fEi4GtD3Lb-tvyEg@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkRR5CO_KVnZbGPcGp-S=6dn3QnidSx1yu75i044eARE6g@mail.gmail.com>
severity 24616 wishlist
thanks
Philipp Stephani <p.stephani2@gmail.com> writes:
> > Is there anything more to do here, or can this bug report be closed?
>
> Well, ideally the stacktrace would be printed on the terminal invoking
> emacsclient to ease debugging.
OK. You're probably right in that it would make for a better user
experience in this case.
I'm not sure how easy or hard this would be to do, but as it stands I
think this is a feature request rather than a bug. I'm therefore
changing the severity to wishlist. Feel free to change the severity
back to "minor" if you disagree.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-11-19 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 16:30 bug#24616: 26.0.50; No backtrace when emacsclient --eval fails Philipp Stephani
2016-10-04 17:15 ` Eli Zaretskii
2016-10-04 20:52 ` Noam Postavsky
2016-10-04 22:28 ` Clément Pit--Claudel
2016-10-04 23:50 ` Noam Postavsky
2016-10-05 0:02 ` Clément Pit--Claudel
2016-10-05 6:41 ` Eli Zaretskii
2016-10-22 15:35 ` npostavs
2016-10-22 15:52 ` Eli Zaretskii
2016-10-22 16:08 ` npostavs
2019-11-02 1:09 ` Stefan Kangas
2019-11-18 21:05 ` Philipp Stephani
2019-11-19 14:31 ` Stefan Kangas [this message]
2016-10-24 0:51 ` Live System User
2016-10-26 1:46 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmk55A+VR3fnBTpcnJt4+xR9cEfbr_fEi4GtD3Lb-tvyEg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=24616@debbugs.gnu.org \
--cc=clement.pit@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=p.stephani2@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.