Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Jesper Harder <harder@myrealbox.com>
Subject: Re: goal-column in summary buffer
Date: Sun, 22 Dec 2002 20:48:41 +0100	[thread overview]
Message-ID: <m37ke1omw6.fsf@defun.localdomain> (raw)
In-Reply-To: <87hed7ion8.fsf@jidanni.org>

Dan Jacobson <jidanni@dman.ddts.net> writes:

> I wish every time I select an article, the cursor in the summary
> buffer wouldn't be moved back over to the left.  If I moved it over to
> the right I wish it would stay there.
>
> Or maybe we can be allowed our choice of 'goal fields'.  E.g. I wish
> the cursor to stay on the first char of the subject, instead of the
> date where it goes now.

> From the Oort Gnus manual:

,----
| 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.
`----

The colon works in Gnus 5.9, but I think `%C' and the function
`gnus-goto-colon' might be new in Oort Gnus.


      parent reply	other threads:[~2002-12-22 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87hed7ion8.fsf@jidanni.org>
2002-12-22 19:46 ` Kai Großjohann
2002-12-22 19:48 ` Jesper Harder [this message]

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=m37ke1omw6.fsf@defun.localdomain \
    --to=harder@myrealbox.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).