This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 32331 - ide.log newline endings incorrect
Summary: ide.log newline endings incorrect
Alias: None
Product: platform
Classification: Unclassified
Component: Module System (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Jesse Glick
Depends on:
Reported: 2003-03-26 02:38 UTC by dnoyeB
Modified: 2008-12-23 08:37 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

*attached* sample log file ;-} (26.34 KB, text/plain)
2003-04-03 17:24 UTC, dnoyeB
Probably fix (untested) (1.11 KB, patch)
2003-04-05 08:51 UTC, Jesse Glick
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description dnoyeB 2003-03-26 02:38:49 UTC
The log file no longer is using the correct return 
characters on windows.  This changed in about the last week 
or so.

Please change back to using the proper return character for 
windows.  Else I can not open the file and comprehend it 
Comment 1 Jesse Glick 2003-04-03 14:30:27 UTC
Wow - no wonder this issue was being ignored. You filed it in a module
which is barely maintained and is not in NetBeans builds at all!
Please, if you don't know what Issuezilla component to use, file in
core and it will get reassigned.

Please supply better details. What builds are you using precisely?
Please attach sample log files.
Comment 2 dnoyeB 2003-04-03 15:07:40 UTC
  Product Version       = NetBeans IDE Dev (Build 200304010100)
  Operating System      = Windows 2000 version 5.0 running on x86
  Java; VM; Vendor      = 1.3.1_07; Java HotSpot(TM) Client VM
1.3.1_07-b02; Sun Microsystems Inc.
  Java Home             = c:\jdk1.3.1_07\jre
Comment 3 Jesse Glick 2003-04-03 15:20:09 UTC
Please *attach* a sample log file (click "Create a new attachment").
Comment 4 dnoyeB 2003-04-03 17:24:52 UTC
Created attachment 9687 [details]
*attached* sample log file ;-}
Comment 5 Jesse Glick 2003-04-03 18:35:21 UTC
Thanks. Problem is in list of modules - separated by \n even on Windows.
Comment 6 Marian Mirilovic 2003-04-04 14:38:19 UTC
This issue will not be solved for 3.5, TM=4.0
Comment 7 dnoyeB 2003-04-04 18:25:28 UTC
This regression is a regressivly regressive regression.  

Thats the magic word to get it fixed right away right? 

:D :D

This will be a major deterrent for windows users diagnosing 
any bugs that show up.  I'm dreding it already.  We can use 
wordpad though...
Comment 8 Jesse Glick 2003-04-04 18:47:03 UTC
REGRESSION is the keyword you are looking for. :-)

Raising the priority may be warranted. It would have to be pretty
severe to get into 3.5 this late. I don't personally have any opinion
as to its severity.

Yes you can use WordPad if need be.
Comment 9 dnoyeB 2003-04-05 04:05:21 UTC
Pretty severe bug, or pretty trivial fix.

I'm hoping for the latter.
Comment 10 Jesse Glick 2003-04-05 08:50:50 UTC
OK, the fix should be trivial. Attaching (haven't tested it yet, and
can't really test it properly myself - someone with Windows will have to).
Comment 11 Jesse Glick 2003-04-05 08:51:24 UTC
Created attachment 9717 [details]
Probably fix (untested)
Comment 12 dnoyeB 2003-04-05 17:20:35 UTC
Comment 13 Jesse Glick 2003-04-09 22:04:51 UTC
Fixed in the trunk. Feel free to petition on nbdev to have priority
increased to justify a 3.5 merge. I don't have an opinion about it.

committed     Up-To-Date  1.34       
Comment 14 dnoyeB 2003-04-09 23:24:41 UTC
I am not going to petition.  I will use my own build since I wont be
using debugging build anyway...

I don't see the point in a log if its unreadable.I dont think it would
be so nice if the nix log has windows returns.  Time will tell.
Comment 15 Jesse Glick 2003-04-10 01:23:51 UTC
Well, the question is whether this would be a serious annoyance to a
typical Windows user. Summary of impact as I understand it:

The Unix log is fine - it uses all NL's.

The problem is that on Windows, *most* of the log uses the normal CRNL
sequence appropriate to that platform. However the list of enabled
modules which is printed during startup is internally separated by NL,
not CRNL, without this patch. If you look at it under Windows Notepad
(I assume - I don't have a Windows install to test), you should see
most of the log normally, but the module list displayed as one long
line with a "broken box" character in place of line breaks, i.e:

Turning on modules:#    x.y [...]#    z.w [...]#(etc.)

(using '#' for the box symbol)

This part would be hard (but possible) to read and use.

If you open under Wordpad, or in a web browser, it should be displayed
normally, I guess.
Comment 16 dnoyeB 2003-04-10 02:21:32 UTC
Yes, wordpad is fine.  No, my last experience showed it was not just
the modules list, but the whole dang thing.  I can't test now though.

I suppose one will just have to map .log to wordpad instead of notepad.

wordpad is not as nice to use as notepad because wordpad is a little
too 'smart' and it gets in your way...But yes, any application
_except_ notepad will work.  Well thats on NT, I don't think wordpad
on 95 works!!! j/k...

c'est la vie.  que sera sera.  beez like that sometimes. etc... its
patched in the dev so ill just use the first "Q."
Comment 17 Marian Mirilovic 2005-07-13 13:23:16 UTC