unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Piet van Oostrum <piet@cs.uu.nl>
Subject: Re: Mouse-1 behaviour changed in gnus?
Date: Thu, 05 Jan 2006 22:01:43 +0100	[thread overview]
Message-ID: <m2psn6gzig.fsf@ordesa.lan> (raw)
In-Reply-To: <v97j9ekar5.fsf@marauder.physik.uni-ulm.de>

>>>>> Reiner Steib <reinersteib+gmane@imap.cc> (RS) wrote:

>RS> On Thu, Jan 05 2006, Piet van Oostrum wrote:
>>> A few days ago (Tuesday) I checked out a new copy from the CVS and installed
>>> it. I noticed one problem and I am not sure if it is a bug, a policy change
>>> or just a matter of a different configuration:

>RS> Which was the last version where you did _not_ notice this behavior?
>RS> I don't recall any relevant changes in Gnus.  And there were no
>RS> check-ins in lisp/gnus/ at all since 2005-12-16.

The previous version I had was Oct 28

>>> When I click mouse-1 on a link in a gnus *Article* buffer, the link isn't
>>> followed, as in the previous version I had, but the buffer scrolls one
>>> line. Mouse-2 does follow the link. Why is this?

>RS> Which kind of link?

>RS> Some test links follow: http://www.gnu.org (info "(gnus)Article
>RS> Buttons") `gnus-button-emacs-level' <reinersteib+gmane@imap.cc>

I see 3 links above (gnus-button-emacs-level isn't a link) and all 3 have
this effect. When the cursor is already in the Article buffer it works.
-- 
Piet van Oostrum <piet@cs.uu.nl>
URL: http://www.cs.uu.nl/~piet [PGP 8DAE142BE17999C4]
Private email: piet@vanoostrum.org

  reply	other threads:[~2006-01-05 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05  7:28 Mouse-1 behaviour changed in gnus? Piet van Oostrum
2006-01-05 14:30 ` Reiner Steib
2006-01-05 21:01   ` Piet van Oostrum [this message]
2006-01-05 16:30 ` Piet van Oostrum
2006-01-07 12:06   ` public
2006-01-11 15:31     ` Piet van Oostrum
2006-02-16 21:19   ` Reiner Steib
2006-02-18  0:06     ` Richard M. Stallman
2006-02-18 10:36       ` Reiner Steib

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2psn6gzig.fsf@ordesa.lan \
    --to=piet@cs.uu.nl \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).