From: Shenghuo ZHU <zsh@cs.rochester.edu>
Cc: bugs@gnus.org
Subject: bug: push-button in XEmacs
Date: 21 Oct 1998 03:35:55 -400 [thread overview]
Message-ID: <2nogr6v02s.fsf@zsh.cs.rochester.edu> (raw)
When push mime button with mouse-2 in XEmacs, mime part is not
displayed at a correct position.
A patch is attached.
--
Shenghuo
:- cut ------------------------------------------------------------
--- ChangeLog 1998/10/21 07:26:01 1.2
+++ ChangeLog 1998/10/21 07:26:47
@@ -1,3 +1,8 @@
+Wed Oct 21 03:26:30 1998 Shenghuo ZHU <zsh@cs.rochester.edu>
+
+ * gnus-xmas.el (gnus-xmas-article-push-button): Go to the
+ position.
+
Tue Oct 20 23:37:43 1998 Shenghuo ZHU <zsh@cs.rochester.edu>
* gnus-art.el (gnus-mime-display-mixed): Multipart in
--- gnus-xmas.el 1998/10/21 07:24:10 1.1
+++ gnus-xmas.el 1998/10/21 07:24:26
@@ -246,6 +246,7 @@
(let* ((pos (event-closest-point event))
(data (get-text-property pos 'gnus-data))
(fun (get-text-property pos 'gnus-callback)))
+ (goto-char pos)
(when fun
(funcall fun data))))
reply other threads:[~1998-10-21 7:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2nogr6v02s.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
--cc=bugs@gnus.org \
/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).