emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#13979: closed (24.3.50; NS: scroll-bar not draggab


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#13979: closed (24.3.50; NS: scroll-bar not draggable)
Date: Mon, 18 Mar 2013 17:26:02 +0000

Your message dated Mon, 18 Mar 2013 18:23:56 +0100
with message-id <address@hidden>
and subject line Re: bug#13979: 24.3.50; NS: scroll-bar not draggable
has caused the debbugs.gnu.org bug report #13979,
regarding 24.3.50; NS: scroll-bar not draggable
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
13979: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13979
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3.50; NS: scroll-bar not draggable Date: Sun, 17 Mar 2013 03:37:23 +0800
turn on scroll-bar mode
 (scroll-bar-mode t)

then open a file and drag the scroll bar, it shows:

`mouse-on-link-p: Wrong type argument: listp, handle'

the stacktrace:

Debugger entered--Lisp error: (wrong-type-argument listp handle)
  mouse-posn-property((#<window 0x10506e250 on *info*>
vertical-scroll-bar (4 . 428) 95079520 handle) follow-link)
  mouse-on-link-p((#<window 0x10506e250 on *info*> vertical-scroll-bar
(4 . 428) 95079520 handle))
  mouse--down-1-maybe-follows-link(nil)

Also with scroll-bar turned on, horizontally splitted windows can not be
resized by dragging.

In GNU Emacs 24.3.50.3 (x86_64-apple-darwin12.2.1, NS apple-appkit-1187.37)
 of 2013-03-17 on Darren-rMBP
Bzr revision: 112060 address@hidden
Windowing system distributor `Apple', version 10.3.1187
Configured using:
 `configure --with-ns'



--- End Message ---
--- Begin Message --- Subject: Re: bug#13979: 24.3.50; NS: scroll-bar not draggable Date: Mon, 18 Mar 2013 18:23:56 +0100
Hello.

This has been fixed in trunk.

        Jan D.

17 mar 2013 kl. 16:37 skrev Stefan Monnier <address@hidden>:

>>>> Which code has changed to care about mouse-1 versus down-mouse-1?
>>> The code that turns mouse-1 into mouse-2 in case of follow-link (which
>>> is now run more often: it used to be done in the mouse-drag-region
>>> command, but is now done in a key-translation-map entry).
>> So shall we change key-translation-map or is it better for the NS-port to
>> use mouse-1 for scroll events?
> 
> I don't know the backtrace for your latest problem, but for the other
> the bug was in mouse-on-link-p which just needs to be fixed to return
> the proper boolean for that case.
> 
> 
>        Stefan



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]