From: Drew Adams <drew.adams@oracle.com>
To: Gracjan Polak <gracjanpolak@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: RE: Wrong type argument: arrayp, nil
Date: Sun, 20 Apr 2014 14:00:21 -0700 (PDT) [thread overview]
Message-ID: <3feea04b-4f24-455d-a672-bbfac743f564@default> (raw)
In-Reply-To: <CAChsM3RMkV9s85E-uXyhJWDE_RmU-7fv+fUzRFRy0iM4utVcTQ@mail.gmail.com>
> Is there a debug tutorial somewhere or d and c and q is all that is needed
> in real life?
See the Elisp manual, node `Using Debugger'. See in fact all of the nodes
under node `Debugger'.
> How does you debug-edit-debug cycle look like? Is C-x C-e all I should be
> using or is there something that has a concept of 'a breakpoint'?
You can place an explicit call to `debug' in the source code (or a copy
of the source code, anywhere you like. That makes the debugger enter at
that point.
next prev parent reply other threads:[~2014-04-20 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 17:44 Wrong type argument: arrayp, nil Gracjan Polak
2014-04-20 18:16 ` Drew Adams
2014-04-20 18:25 ` Gracjan Polak
2014-04-20 21:00 ` Drew Adams [this message]
[not found] <mailman.19942.1398016221.10748.help-gnu-emacs@gnu.org>
2014-04-20 18:17 ` Pascal J. Bourguignon
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=3feea04b-4f24-455d-a672-bbfac743f564@default \
--to=drew.adams@oracle.com \
--cc=gracjanpolak@gmail.com \
--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).