🚀 go-pugleaf

>>>>> weemba@sagi.wistar.upenn.edu (Matthew P Wiener) (MPW) writes:

MPW> Concerning Gnews, you can get threads by using the index (=) and
MPW> sorting the index buffer (S).  You can also read threads backwards
MPW> very easily--you enter the group at the end (.$), back your way
MPW> through the articles (p) and when you hit an interesting article,
MPW> backtrace (t) your way through the previous articles, using (T) to
MPW> return.

What I would like is a command to do the opposite of 't', i.e. one step
back. I find it most logical to trace back to the beginning and then read
the thread in the original order.

Also a tree-like index structure for the threads would be nice.

I found a bug with the index stuff by the way. If your index contains
article numbers with different lengths (e.g going from 9 to 10) when
going back to the index (with the = command from an article) the cursor
positions sometimes in the wron place in the index. This is
because it searches for something like "1" and matches on "10".

The code is in group-index:

	      (if (re-search-forward (concat "^ *" article-current) nil t)

Changing this to 

	      (if (re-search-forward
			 (concat "^ *" article-current "[^0-9]") nil t)

helps a lot.
-- 
Piet* van Oostrum, Dept of Computer Science, Utrecht University,
Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands.
Telephone: +31 30 531806   Uucp:   uunet!mcsun!ruuinf!piet
Telefax:   +31 30 513791   Internet:  piet@cs.ruu.nl   (*`Pete')