From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Wandering cursor in summary buffer.
Date: Sun, 18 Aug 2002 21:20:22 +0200 [thread overview]
Message-ID: <vafu1ls3rex.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <oydofc6d6f0.fsf@bert.cs.rice.edu> (Scott A Crosby's message of "13 Aug 2002 12:17:55 -0500")
Scott A Crosby <scrosby@cs.rice.edu> writes:
> I noticed an annoying property of GNUS in the summary buffer..
>
> When I do a 'd' to mark a message as read and the curser goes to the
> next line, it gets repositioned after the first ':' in the subject
> line (first character in the line if there's no ':' in the
> subject)
Gnus expects that you have a colon somewhere else in your summary
lines. But Gnus wasn't Gnus, if it wasn't configurable: just
redefine the function gnus-goto-colon. For example:
(defun gnus-goto-colon ()
(beginning-of-line)
(forward-char 3))
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
next prev parent reply other threads:[~2002-08-18 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 17:17 Scott A Crosby
2002-08-18 19:20 ` Kai Großjohann [this message]
2002-08-21 21:00 ` Raymond Scholz
2002-08-22 16:07 ` Kai Großjohann
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=vafu1ls3rex.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).