Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Walters <walters@cis.ohio-state.edu>
Subject: Re: emacs-21 and gnus
Date: Thu, 12 Jul 2001 15:02:04 -0400	[thread overview]
Message-ID: <87y9pu9djn.church.of.emacs@cis.ohio-state.edu> (raw)
In-Reply-To: <ysd6r8vnt5u6.fsf@sol-cmarquar.pet.usa.alcatel.com> (Colin Marquardt's message of "Wed, 11 Jul 2001 16:16:01 -0700")

Colin Marquardt <colin.marquardt@usa.alcatel.com> writes:

> WIBNI Gnus used this for showing the current article in the summary
> buffer? Might be a more generic way than the recent discussions
> about highline.el etc.

How about the following?  I couldn't find a way to do this in XEmacs;
maybe an XEmacs guru will have a way to make it work there too.

2001-07-12  Colin Walters  <walters@cis.ohio-state.edu>

	* gnus-sum.el (gnus-summary-set-article-display-arrow): New function.
	(gnus-summary-goto-subject): Use it.

--- gnus-sum.el.~6.72.~	Thu Jul 12 13:04:12 2001
+++ gnus-sum.el	Thu Jul 12 14:59:47 2001
@@ -2703,6 +2703,17 @@
 	  (aset table i [??]))))
     (setq buffer-display-table table)))
 
+(defun gnus-summary-set-article-display-arrow (pos)
+  "Update the overlay arrow to point to line at position POS.
+Currently, this only works in Emacs 21."
+  (when (and (boundp 'overlay-arrow-position)
+	     (boundp 'overlay-arrow-string))
+    (setq overlay-arrow-string "=>"
+	  overlay-arrow-position (save-excursion
+				   (goto-char pos)
+				   (beginning-of-line)
+				   (point-marker)))))
+
 (defun gnus-summary-buffer-name (group)
   "Return the summary buffer name of GROUP."
   (concat "*Summary " group "*"))
@@ -6123,7 +6134,9 @@
 	  (unless silent
 	    (gnus-message 3 "Can't find article %d" article))
 	  nil)
-      (goto-char (gnus-data-pos data))
+      (let ((pt (gnus-data-pos data)))
+	(goto-char pt)
+	(gnus-summary-set-article-display-arrow pt))
       (gnus-summary-position-point)
       article)))
 


  parent reply	other threads:[~2001-07-12 19:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11 19:34 reader
2001-07-11 20:09 ` Colin Walters
2001-07-11 22:20   ` Harry Putnam
2001-07-11 22:49     ` Kai Großjohann
2001-07-11 23:16       ` Colin Marquardt
2001-07-12 11:17         ` Kai Großjohann
2001-07-12 19:02         ` Colin Walters [this message]
2001-07-12 20:41           ` Colin Walters
2001-07-13  0:12             ` Colin Marquardt
2001-07-13  4:51               ` Colin Walters
2001-07-13 18:46                 ` Colin Marquardt
2001-07-18 12:58                   ` Fabien Penso
2001-07-20 17:13                     ` Mattias Ahnberg
2001-07-30 13:06                       ` Fabien Penso
2001-07-13  8:51             ` Kai Großjohann
2001-07-13 15:12               ` Colin Walters
2001-07-12  3:20       ` Harry Putnam
2001-07-12 11:19         ` Kai Großjohann
2001-07-12 18:25           ` Harry Putnam
2001-07-12  3:07   ` Karl Eichwalder
2001-07-12 10:28     ` Gerd Moellmann
2001-07-12 20:34       ` Karl Eichwalder
2001-07-13  9:19     ` Richard Stallman
2001-07-19  5:55       ` Karl Eichwalder
2001-07-19  6:57         ` Eli Zaretskii
2001-07-11 20:50 ` luis fernandes
2001-07-11 22:20   ` Harry Putnam

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=87y9pu9djn.church.of.emacs@cis.ohio-state.edu \
    --to=walters@cis.ohio-state.edu \
    /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).