gnus-goto-colon

gnus-goto-colon

[Pavel Janík]

Hi,

in gnus.el we have:

;; 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?
-- 
Pavel Janík

In the beginning was the word, and the word was content-type: text/plain.
                  -- Kilian A. Foth in comp.emacs.xemacs

Re: gnus-goto-colon

[Simon Josefsson]

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.

Re: gnus-goto-colon

[Pavel Janík]

   From: Simon Josefsson <jas@extundo.com>
   Date: Sat, 01 Dec 2001 17:10:39 +0100

   > > ; Workaround for Gnus inconvenience
   > > (defalias 'gnus-summary-position-point 'beginning-of-line)
   > >
   > > What was the reason for this change?
   > 
   > What change?

For that change in the past. I did not looked at the time of that change.

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

Yes, that is much better way then I'm doing right now, but when I added %C
at the beginning of gnus-summary-line-format, I can no longer enter into
Summary buffer:

Debugger entered--Lisp error: (args-out-of-range 0 1)
  gnus-put-text-property(0 1 gnus-position t)
  (progn (gnus-put-text-property (1- ...) (point) (quote gnus-position) t) (insert gnus-tmp-unread gnus-tmp-replied gnus-tmp-score-char gnus-tmp-indentation) (gnus-put-text-property (point) (progn ... ...) gnus-mouse-face-prop gnus-mouse-face) (insert " ") (gnus-add-text-properties (point) (progn ... ...) (quote ...)) (insert gnus-tmp-subject-or-nil "\n"))
  eval((progn (gnus-put-text-property (1- ...) (point) (quote gnus-position) t) (insert gnus-tmp-unread gnus-tmp-replied gnus-tmp-score-char gnus-tmp-indentation) (gnus-put-text-property (point) (progn ... ...) gnus-mouse-face-prop gnus-mouse-face) (insert " ") (gnus-add-text-properties (point) (progn ... ...) (quote ...)) (insert gnus-tmp-subject-or-nil "\n")))
  gnus-summary-insert-line([0 "" "" "05 Apr 2001 23:33:09 +0400" "" "" 0 0 "" nil] 0 nil 128 t nil "" nil 1)
  gnus-update-summary-mark-positions()
  gnus-summary-mode("LinuxKernel")
  gnus-summary-setup-buffer("LinuxKernel")
  gnus-summary-read-group-1("LinuxKernel" nil t nil nil nil)
  gnus-summary-read-group("LinuxKernel" nil t nil nil nil nil)
  gnus-group-read-group(nil t)
  gnus-group-select-group(nil)
  gnus-topic-select-group(nil)
  call-interactively(gnus-topic-select-group)

-- 
Pavel Janík

What do you want to happen? You want to have an interface like
	echo 0 > /proc/bugs/mm
that makes mm bugs go away?
                  -- Linus Torvalds in LKML about "Tuning for bugs"

Re: gnus-goto-colon

[ShengHuo ZHU]

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

>    From: Simon Josefsson <jas@extundo.com>
>    Date: Sat, 01 Dec 2001 17:10:39 +0100
>
>    > > ; Workaround for Gnus inconvenience
>    > > (defalias 'gnus-summary-position-point 'beginning-of-line)
>    > >
>    > > What was the reason for this change?
>    > 
>    > What change?
>
> For that change in the past. I did not looked at the time of that change.
>
>    > Maybe you can customize `gnus-summary-line-format' as described below
>    > to achieve what you want instead?
>
> Yes, that is much better way then I'm doing right now, but when I added %C
> at the beginning of gnus-summary-line-format, I can no longer enter into
> Summary buffer:
>
> Debugger entered--Lisp error: (args-out-of-range 0 1)
>   gnus-put-text-property(0 1 gnus-position t)

Fixed.  (Maybe you have to reevaluate gnus-summary-line-format because
of the cache.)

ShengHuo