Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: gnus-goto-colon
Date: Sat, 01 Dec 2001 17:10:39 +0100	[thread overview]
Message-ID: <ilu7ks6kjk0.fsf@dhcp128.extundo.com> (raw)
In-Reply-To: <m3u1vbxbx9.fsf@Janik.cz> (Pavel@Janik.cz's message of "Sat, 01 Dec 2001 15:17:06 +0100")

Pavel@Janik.cz (Pavel Janík) writes:

> ;; Fix by Hallvard B Furuseth <h.b.furuseth@usit.uio.no>.
> ;; If you want the cursor to go somewhere else, set these two
> ;; functions in some startup hook to whatever you want.
> (defalias 'gnus-summary-position-point 'gnus-goto-colon)
> (defalias 'gnus-group-position-point 'gnus-goto-colon)
>
> It is the cause of my problems in groups where I have customised
> gnus-summary-line-format to include only the subjects and these subjects
> can be very long (~80 chars) and can contain colons. Now, when I'm reading
> by subjects, when moving to next article, the point jumps here and there
> (if the subject contains `:') and it is really distracting. I'd like to get
> rid of this in my .gnus:
>
> ; Workaround for Gnus inconvenience
> (defalias 'gnus-summary-position-point 'beginning-of-line)
>
> What was the reason for this change?

What change?  The code you cite has been the same since (at least)
Gnus version 5.0.

Maybe you can customize `gnus-summary-line-format' as described below
to achieve what you want instead?

Positioning Point
-----------------

   Gnus usually moves point to a pre-defined place on each line in most
buffers.  By default, point move to the first colon character on the
line.  You can customize this behaviour in three different ways.

   You can move the colon character to somewhere else on the line.

   You can redefine the function that moves the point to the colon.  The
function is called `gnus-goto-colon'.

   But perhaps the most convenient way to deal with this, if you don't
want to have a colon in your line, is to use the `%C' specifier.  If you
put a `%C' somewhere in your format line definition, Gnus will place
point there.




  reply	other threads:[~2001-12-01 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01 14:17 gnus-goto-colon Pavel Janík
2001-12-01 16:10 ` Simon Josefsson [this message]
2001-12-01 18:39   ` gnus-goto-colon Pavel Janík
2001-12-01 20:16     ` gnus-goto-colon ShengHuo ZHU

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=ilu7ks6kjk0.fsf@dhcp128.extundo.com \
    --to=jas@extundo.com \
    /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).