From: nljlistbox2@gmail.com (N. Jackson)
To: 16647@debbugs.gnu.org
Subject: bug#16647: Imprecisions with window-resizing cursors
Date: Fri, 14 Feb 2014 18:53:07 -0400 [thread overview]
Message-ID: <87lhxdgvcc.fsf@moondust.localdomain> (raw)
In-Reply-To: <52FE5FA0.6020202@gmx.at> (martin rudalics's message of "Fri, 14 Feb 2014 19:25:36 +0100")
martin rudalics <rudalics@gmx.at> writes:
> Can you please try conducting the same experiments with emacs -Q
>
> (set-frame-parameter nil 'right-divider-width 6)
>
> and with scrollbars en-/and disabled?
emacs -Q
M-: (set-frame-parameter nil 'right-divider-width 6)
M-x split-window-right
With this I see Evgeni's original bug -- when the <=> handle first
appears beyond the vertical line, clicking on it and dragging has no
effect, if just disappears and returns to a normal cursor. It's
disorienting behaviour but I think it might be due to the lag --
i.e. maybe it's about to turn back to the normal mouse cursor but hasn't
gotten around to actually doing so yet.
I do _not_ see my "Another bug" with this configuration -- when the
vertical line is at its extreme left or right position, it doesn't
matter from which side one approaches it, one still get's the <=> handle
displayed.
emacs -Q
M-: (progn
(scroll-bar-mode -1) (set-frame-parameter nil 'right-divider-width 6)
(split-window-right) )
With this recipe I see nothing wrong at all (except for the
sluggishness).
Also I have a slight amendment to what I wrote earlier about my "Another
bug":
>> Another bug =========== When the vertical line is as far to the right
>> in the frame as it will go (i.e., when the right window is as narrow
>> as permitted), then the <=> handle only appears when the mouse cursor
>> approaches the vertical line from the right. If the mouse cursor
>> approaches the vertical line from the left, the <=> handle fails to
>> appear. (Ditto with "left" and "right" reversed in that statement.)
>
> Interesting. I cannot observe that here.
I double checked this. I definitely see this happening, but I was
mistaken about the "ditto". When the vertical line is as far to the left
as it will go, the <=> handle only appears when the mouse cursor
approaches the vertical line from the _right_ -- the same direction as
for the case with the vertical line as far to the left as it will go.
next prev parent reply other threads:[~2014-02-14 22:53 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 6:05 bug#16647: Imprecisions with window-resizing cursors E Sabof
2014-02-05 10:48 ` martin rudalics
2014-02-06 9:21 ` Evgkeni Sampelnikof
2014-02-06 10:26 ` martin rudalics
2014-02-07 17:32 ` E Sabof
2014-02-07 19:14 ` martin rudalics
2014-02-13 9:46 ` E Sabof
2014-02-14 11:39 ` martin rudalics
2014-02-14 16:13 ` N. Jackson
2014-02-14 18:25 ` martin rudalics
2014-02-14 22:53 ` N. Jackson [this message]
2014-02-16 10:32 ` martin rudalics
2014-02-16 18:17 ` N. Jackson
2014-02-20 4:32 ` N. Jackson
2014-02-21 18:53 ` martin rudalics
2014-02-21 23:33 ` N. Jackson
2014-02-22 9:17 ` martin rudalics
2014-02-22 18:06 ` N. Jackson
2014-02-22 18:33 ` E Sabof
2014-02-22 18:52 ` martin rudalics
2014-02-22 19:07 ` E Sabof
2014-02-23 0:27 ` N. Jackson
2014-02-23 10:53 ` martin rudalics
2014-02-24 2:01 ` N. Jackson
2014-02-24 7:40 ` martin rudalics
2014-02-24 15:30 ` N. Jackson
2014-02-24 18:12 ` martin rudalics
2014-02-24 18:39 ` N. Jackson
2014-02-24 18:58 ` martin rudalics
2014-02-27 19:59 ` martin rudalics
2014-02-28 0:49 ` N. Jackson
2014-02-28 6:47 ` Eli Zaretskii
2014-02-28 17:30 ` bug#16647: OT: window-resizing cursor for minibuffer (Imprecisions with window-resizing cursors) N. Jackson
2014-03-01 7:18 ` Eli Zaretskii
2014-02-28 10:59 ` bug#16647: Imprecisions with window-resizing cursors martin rudalics
2014-02-28 17:25 ` bug#16647: OT: window-resizing cursor for minibuffer (Imprecisions with window-resizing cursors) N. Jackson
2014-02-28 18:24 ` martin rudalics
2014-02-28 21:19 ` bug#16647: Imprecisions with window-resizing cursors N. Jackson
2014-09-19 8:18 ` martin rudalics
2014-02-23 10:53 ` martin rudalics
2014-02-23 23:29 ` E Sabof
2014-02-24 7:39 ` martin rudalics
2014-02-24 13:00 ` E Sabof
2014-02-24 18:12 ` martin rudalics
2014-02-24 23:06 ` E Sabof
2014-02-26 10:17 ` martin rudalics
2014-02-26 16:45 ` Eli Zaretskii
2014-02-27 20:00 ` martin rudalics
2014-02-27 20:38 ` Eli Zaretskii
2014-02-28 11:00 ` martin rudalics
2014-02-28 11:32 ` Eli Zaretskii
2014-02-28 12:47 ` martin rudalics
2014-02-28 14:29 ` Eli Zaretskii
2014-02-28 18:23 ` martin rudalics
2014-03-01 7:43 ` Eli Zaretskii
2014-02-27 19:59 ` martin rudalics
2014-02-27 19:59 ` martin rudalics
2014-02-22 18:44 ` martin rudalics
2014-02-22 23:33 ` N. Jackson
2014-02-27 19:58 ` martin rudalics
2014-02-28 0:39 ` N. Jackson
2014-02-27 19:58 ` martin rudalics
2014-02-28 0:38 ` N. Jackson
2014-02-14 23:13 ` Drew Adams
2014-02-06 10:32 ` Eli Zaretskii
2014-02-06 13:34 ` Stefan Monnier
2014-02-07 19:14 ` martin rudalics
2014-02-27 19:58 ` martin rudalics
2014-02-27 20:33 ` Eli Zaretskii
2014-02-28 11:00 ` martin rudalics
2014-02-28 11:28 ` Eli Zaretskii
2014-02-28 12:47 ` martin rudalics
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=87lhxdgvcc.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=16647@debbugs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.