Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: gnus-summary-catchup-and-exit not setting marks
Date: Wed, 25 Sep 2002 15:20:28 +0200	[thread overview]
Message-ID: <iluznu6gq8z.fsf@latte.josefsson.org> (raw)
In-Reply-To: <un0q6zbvb.fsf@axis.com> (Niklas Morberg's message of "Wed, 25 Sep 2002 10:56:08 +0200")

Niklas Morberg <niklas.morberg@axis.com> writes:

>> Maybe this should go into the manual somewhere?
>
> I certainly think so.

I added something like it to the troubleshooting section:

   If you want to debug your problem further before reporting, possibly
in order to solve the problem yourself and send a patch, you can use
edebug.  Debugging lisp code is documented in the Elisp manual (*note
Debugging Lisp Programs: (elisp)Debugging.).  To get you started with
edebug, consider if you discover some weird behaviour when pressing
`c', the first step is to do `C-h k c' and click on the hyperlink
(Emacs only) in the documentation buffer that leads you to the function
definition, then press `M-x edebug-defun RET' with point inside that
function, return to Gnus and press `c' to invoke the code.  You will be
placed in the lisp buffer and can single step using `SPC' and evaluate
expressions using `M-:' or inspect variables using `C-h v', abort
execution with `q', resume execution with `c' or `g'.




  reply	other threads:[~2002-09-25 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 19:20 David S Goldberg
2002-09-23  9:56 ` Niklas Morberg
2002-09-23 12:51   ` Jinhyok Heo
2002-09-23 10:24 ` Simon Josefsson
2002-09-23 21:22   ` Clemens Fischer
2002-09-24 11:49     ` Simon Josefsson
2002-09-25  8:56       ` Niklas Morberg
2002-09-25 13:20         ` Simon Josefsson [this message]
2002-09-24 15:26     ` David S Goldberg

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=iluznu6gq8z.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=ding@gnus.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 NNTP newsgroup(s).