[bug #15712] pressing enter just after an x80 character in the editor causes Segmentation fault

2006-02-15 Thread Pavel Tsekov
Update of bug #15712 (project mc): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #1: This bug seems to be

[bug #12972] copy from fish vfs stalls on symlinks

2006-02-15 Thread Pavel Tsekov
Update of bug #12972 (project mc): Assigned to:None = ptsekov ___ Reply to this item at: http://savannah.gnu.org/bugs/?func=detailitemitem_id=12972

[bug #15080] directory keyword doesn't work in mc.ext

2006-02-15 Thread Leonard den Ottolander
Follow-up Comment #2, bug #15080 (project mc): Also the specific issue with /var/log/*.[0-9] has been fixed. ___ Reply to this item at: http://savannah.gnu.org/bugs/?func=detailitemitem_id=15080

[bug #15257] mc viewer enters a probably infinite cycle on some files with 8-bit characters

2006-02-15 Thread Pavel Tsekov
Follow-up Comment #2, bug #15257 (project mc): Do you mind attaching a simple file which triggers this behaviour ? A list of steps how to reproduce will be much appreciated. ___ Reply to this item at:

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread J.J. Garcia
URL: http://savannah.gnu.org/bugs/?func=detailitemitem_id=15758 Summary: Uncompressing .tar.bz2 leads to malformed filename extension eventually Project: GNU Midnight Commander Submitted by: sm0ketst Submitted on: Wed 02/15/06 at 19:15

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread Pavel Tsekov
Follow-up Comment #1, bug #15758 (project mc): Where did you get that file from ? At newlib's homepage I can only see .tar.gz files ? I've downloaded newlib-1.12.0.tar.gz and tried to reproduce but the file ip_mroute.h extracted just fine. I didn't bother to try with the second file. I pressed

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread J.J. Garcia
Follow-up Comment #2, bug #15758 (project mc): It's a tar.bz2 i did by using the same source as you and using the command: $ tar cvjf ./newlib-1.12.0.tar.bz2 ./newlib-1.12.0 I've patched this sources and packaged in a new tar.bz2 file, that's all. Don't know if you rebuilded it to a tar.bz2 or

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread Leonard den Ottolander
Follow-up Comment #3, bug #15758 (project mc): This looks very much like an issue for which I committed a fix 7 months ago where files with names of NAMSIZ were truncated one char. NAMSIZ = 100, and in this case the affected file names are both 50 chars. Exactly half that length. Odd. Try if

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread Pavel Tsekov
Follow-up Comment #4, bug #15758 (project mc): Leonard, this thought crossed my mind as soon as I noticed this bugreport but that fix was for filenames of length 100 so it I guess it must be something else. I'll try to follow J.J's instructions to create a tar.bz2 file off the original tar.gz