From: Ralf Fassel <ralfixx@gmx.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Function behaves differently when debugged
Date: Tue, 15 May 2018 16:48:32 +0200 [thread overview]
Message-ID: <ygao9hhc6v3.fsf@akutech.de> (raw)
In-Reply-To: mailman.3.1526337298.20804.help-gnu-emacs@gnu.org
* Matthias Pfeifer <pfemat@web.de>
| I bind it to some key in ibuffer-mode. it should print the path to a
| buffer's file. When point is on a line of a buffer that is not backed by a
| file (eg *Messages*) then i get this output:
>
| wrong type argument: strinp, nil
You could set the variable debug-on-error to t to see where the error
occurs and protect that function call by 'stringp'.
| Also I do not understand why my function behaves differently when my
| defun is debugged and when it run without debugging.
Probably because the current buffer query function does not return
'nil' when you are in the debugging console...
HTH
R'
next parent reply other threads:[~2018-05-15 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1526337298.20804.help-gnu-emacs@gnu.org>
2018-05-15 14:48 ` Ralf Fassel [this message]
2018-05-21 21:34 ` Function behaves differently when debugged Robert L.
2018-05-14 22:34 Matthias Pfeifer
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=ygao9hhc6v3.fsf@akutech.de \
--to=ralfixx@gmx.de \
--cc=help-gnu-emacs@gnu.org \
/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.
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).