GNU nano - Bugs: bug #32552, Three Mouse Clicks Needed Before...
You are not allowed to post comments on this tracker with your current authentication level.
bug #32552: Three Mouse Clicks Needed Before Mouse Works
Submitter: | None | ||
Submitted: | Mon 21 Feb 2011 06:47:46 AM UTC | ||
Severity: | 3 - Normal | Status: | Works For Me |
Assigned to: | astyanax | Open/Closed: | Closed |
Jump to the original submission
Tue 11 Apr 2017 12:16:15 PM UTC, comment #9: |
Benno Schulenberg <bens> |
Thu 16 Mar 2017 07:24:57 PM UTC, comment #8: OP? You mean you upgraded your server from Squeeze to Jessie, and then things worked fine? (Because as far as I can tell, Jessie still used nano-2.2.6, so that shouldn't have made a difference.) |
Benno Schulenberg <bens> |
Sat 19 Jul 2014 05:27:17 AM UTC, comment #7: Chris, everything works right on Debian Jessie. |
Anonymous |
Thu 26 Dec 2013 04:04:15 AM UTC, comment #6: Hmm, I see what you mean now that I tried out a similar setup. What seems to be happening is that ncurses is sending back MOUSE1_PRESSED some times, which means we're not getting normal events back from the mouse handler. I did try to work around this, but this led to some very undesirable behavior. So the bug is either in putty's xterm mouse events, or ncurses' handling of them. Unsure which it is, but I'll try some more experimentation. |
Chris Allegretta <astyanax> |
Sun 22 Dec 2013 12:37:46 AM UTC, comment #5: Hi Chris -- thanks so much for the response, and so sorry for the delay on my part! I am generating mouse events by opening a PuTTY terminal in Windows, logging on to my server, starting nano, and clicking on text. That used to work fine, but it's still broken as of now (version 2.3.1 running on Debian Wheezy). Thanks! |
Anonymous |
Sat 12 Jan 2013 03:10:36 AM UTC, comment #4: Hello,
|
Chris Allegretta <astyanax> |
Thu 10 Jan 2013 04:49:05 PM UTC, comment #3: I'm the OP. I'm pretty disappointed it's been a year and nobody ever responded to me. This reflects very poorly on nano. It's hard to recommend nano to people when it appears development and support have ended. |
Anonymous |
Fri 01 Apr 2011 09:53:30 PM UTC, comment #2: Message from OP: The problem persists in Nano 2.3.0. |
Anonymous |
Mon 21 Feb 2011 06:50:35 AM UTC, comment #1: Message from OP:
|
Anonymous |
Mon 21 Feb 2011 06:47:46 AM UTC, original submission:
Hi, the following problem seems to be in nano version 2.2.6. It's unclear to me if earlier versions have this problem as well.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-04-11 | bens | Status | In Progress | Works For Me | |
Open/Closed | Open | Closed | |||
2013-12-26 | astyanax | Status | Need Info | In Progress | |
2013-01-12 | astyanax | Status | None | Need Info | |
Assigned to | None | astyanax |
Powered by Savane 3.13-f8d8.
Corresponding source code
Closing this because things seem to have been solved for the OP (by a system upgrade), and the OP is unreachable, and it wasn't a bug in nano anyway.