From: Klaus Zeitler <kzeitler@lucent.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: gnus-carpal-mode and mouse-autoselect-window
Date: Thu, 24 Feb 2005 14:16:22 +0100 [thread overview]
Message-ID: <q5gbraacd3t.fsf@lucent.com> (raw)
In-Reply-To: <v9k6p2x84s.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 21 Feb 2005 16:09:07 +0100")
>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:
Reiner>
Reiner> I don't use gnus-carpal-mode normally. I couldn't see any
Reiner> difference in the behavior with or without this patch[1]:
do you want to say that this doesn't happen to you at all or that is doesn't
change with your patch?
Here's a (I hope) fairly accurate description what happens for me:
my Gnus frame first looks like this:
-----------------------------------------------------------------------------
|. |
|. |
|. (35 lines) |
|. |
|. |
---- *Group* ----------------------------------------------------------------
| next prev read select catch-up new-news toggle-sub subscribe kill yank |
| describe list subscribed all killed zombies matching post mail local rescan |
| browse-foreign exit |
---- *Carpal Group* ---------------------------------------------------------
now when I move the mouse pointer to the carpal buffer, this buffer is
automatically scrolled, i.e. it changes to
---- *Group* ----------------------------------------------------------------
| browse-foreign exit |
| |
| |
---- *Carpal Group* ---------------------------------------------------------
when I now scroll up again, this buffer will stay visible until I enter and
quit a summary buffer. Then the same thing happens again when I move the mouse
to this buffer for the first time.
Reiner> Or did you mean to add (goto-char (point-min)) _after_ the `if'
Reiner> clause?
I've added it right at the end of the save-excursion, i.e. the function ends
like this:
--- snip ---
(set-window-point (get-buffer-window (current-buffer))
(point-min)))
(goto-char (point-min))
))))
--- snip ---
Reiner> But I saw some strange display problem: After scrolling down in the
Reiner> Carpal Summary buffer with <mouse-5>, I get...
Reiner>
Reiner> --8<---------------cut here---------------start------------->8---
Reiner> mark read tick clear expirable move scroll next-unread prev-unread first best
Reiner> article headers uudecode enter-digest fetch-parent mail move copy respool
Reiner> article headers uudecode enter-digest fetch-parent mail move copy respool
Reiner> --8<---------------cut here---------------end--------------->8---
I haven't seen this (so far :-) and I can't reproduce it. But I don't have
mouse-5, i.e. I always scroll with mouse-1.
Thanks
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
For every problem there is a solution which is simple,
clean and wrong. -- Henry Louis Mencken
next prev parent reply other threads:[~2005-02-24 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 9:42 Klaus Zeitler
2005-02-21 15:09 ` Reiner Steib
2005-02-24 13:16 ` Klaus Zeitler [this message]
2005-02-24 21:02 ` Reiner Steib
2005-03-30 11:01 ` Klaus Zeitler
2005-04-04 6:18 ` Richard Stallman
2005-02-25 9:47 ` Kim F. Storm
2005-03-07 15:07 ` Klaus Zeitler
2005-03-07 19:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q5gbraacd3t.fsf@lucent.com \
--to=kzeitler@lucent.com \
--cc=emacs-pretest-bug@gnu.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).