From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: rms@gnu.org, bug-gnu-emacs@gnu.org
Subject: Re: recover-session doesn't
Date: Thu, 1 Aug 2002 08:26:33 +0300 (IDT) [thread overview]
Message-ID: <Pine.SUN.3.91.1020801082250.20714C-100000@is> (raw)
In-Reply-To: <E17Zoox-00039k-00@whorl.intern.opera.no>
On Wed, 31 Jul 2002, Edward Welbourne wrote:
> > Could you try stepping through the command recover-session-finish
> > and see why it did not ask you about the files?
>
> I'd be happy to, next time I'm trying to recover a session (I tidied
> away the previous recovery file once I'd hand-loaded the buffers it
> told me I'd had open). Is this stepping through elisp execution in
> the elisp debugger ?
Yes.
> How do I do that ?
Please read the "Debugger" node of the ELisp manual, it explains how to
use the ELisp debugger called Edebug.
In a nutshell, you instrument the function you want to debug with
edebug-defun, then use Edebug commands to step through the code.
> I take it I
> then set a break point on recover-session-finish, before invoking
> recover-session ?
No, you simply instrument only recover-session-finish. Then, when it's
called, Edebug will kick in automatically.
next prev parent reply other threads:[~2002-08-01 5:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 17:03 recover-session doesn't Edward Welbourne
2002-07-11 12:01 ` Richard Stallman
2002-07-30 16:30 ` Edward Welbourne
2002-07-31 5:55 ` Richard Stallman
2002-07-31 8:27 ` Edward Welbourne
2002-08-01 5:26 ` Eli Zaretskii [this message]
2002-08-01 8:58 ` Edward Welbourne
2002-08-01 16:20 ` Eli Zaretskii
2002-08-02 6:12 ` Richard Stallman
2002-08-02 8:25 ` Edward Welbourne
2002-08-02 9:03 ` Andreas Schwab
2002-08-02 13:52 ` Edward Welbourne
2002-08-02 11:21 ` fabrice bauzac
2002-08-02 13:44 ` Paul D. Smith
2002-08-02 6:12 ` Richard Stallman
2002-08-01 16:51 ` Richard Stallman
2002-08-16 14:26 ` Edward Welbourne
2002-08-17 4:51 ` Richard Stallman
2002-08-19 8:29 ` Edward Welbourne
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=Pine.SUN.3.91.1020801082250.20714C-100000@is \
--to=eliz@is.elta.co.il \
--cc=bug-gnu-emacs@gnu.org \
--cc=rms@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.
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).