GNU nano - Bugs: bug #24163, division by zero when entering...
You are not allowed to post comments on this tracker with your current authentication level.
bug #24163: division by zero when entering /home and others in read files browser
Submitter: | Jordi Mallach <jordi> | ||
Submitted: | Sat 30 Aug 2008 11:31:05 AM UTC | ||
Severity: | 3 - Normal | Status: | Fixed |
Assigned to: | astyanax | Open/Closed: | Closed |
Jump to the original submission
Tue 27 Oct 2009 04:13:58 AM UTC, comment #7: |
Chris Allegretta <astyanax> |
Sun 26 Jul 2009 11:35:26 PM UTC, comment #6: Ok, after some debugging of 2.1.10pre1 I found a fix/workaround:
|
Paul Wise <pabs> |
Sat 25 Jul 2009 05:36:05 PM UTC, comment #5: Chris, I've prepared a package of 2.1.10pre1 for pabs to test, and unfortunately the bug is still happening in his setup (not in mine). I hope we'll be able to find the culprit during this week while we both attend DebConf, in an attempt to be in time for a fix in 2.1.10. |
Jordi Mallach <jordi> |
Sun 31 Aug 2008 02:30:38 AM UTC, comment #4: I'm attaching /etc/nanorc ~/.nanorc and the output of export. |
Paul Wise <pabs> |
Sat 30 Aug 2008 11:38:54 PM UTC, comment #3: Im not sure what debian is doing differently, but I've been unable to reproduce this behavior on both i386 or x86_64 entering or existing any directory. Perhaps there is an environment variable I don't have set which is somehow affecting the issue?
|
Chris Allegretta <astyanax> |
Sat 30 Aug 2008 11:33:30 AM UTC, comment #2: Sigh, I need more sleep today. The original report can be found here:
|
Jordi Mallach <jordi> |
Sat 30 Aug 2008 11:32:32 AM UTC, comment #1: Ah, note Paul was using version 2.0.7-3 from Debian at the time. |
Jordi Mallach <jordi> |
Sat 30 Aug 2008 11:31:05 AM UTC, original submission:
I recently got this report in the Debian BTS.
|
Jordi Mallach <jordi> |
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 10 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-02-23 | bens | Status | Ready For Test | Fixed | |
Open/Closed | Open | Closed | |||
2009-10-27 | astyanax | Status | Need Info | Ready For Test | |
2008-08-31 | pabs | Attached File | - | Added .nanorc, #16403 | |
Attached File | - | Added nanorc, #16404 | |||
Attached File | - | Added export, #16405 | |||
2008-08-30 | astyanax | Severity | 4 - Important | 3 - Normal | |
Status | None | Need Info | |||
Assigned to | None | astyanax | |||
2008-08-30 | jordi | Carbon-Copy | - | Added paul wise <pabs@debian.org> |
Powered by Savane 3.13-f8d8.
Corresponding source code
okay this should be fixed in r4414. I decided to set width in that instance where we're initializing with no files in the directory to use the value of 'longest' which should always be at least 15, I'd hate to get int some odd situation where we're dividing by longest but it's somehow 0 due to some overflow bug or insanely long file path. Probably needless worry, but oh well.
Sorry I was not more help in helping you figure this elusive one, and I appreciate your dilligence in finding it!