Too many compile errors in Windows command prompt, Can't see the first one

[JimmyD]

Hi,

I can't believe I have to post a thread to ask this, but I can't google the answer I need...

My java program gives too many error messages at compilation.

I am pretty sure they are caused by a small syntax error and are all chain-errored, as they are the result of an edit to a working .java file I am developing.. All I need is to see what's error no. 1.

However there are > 100 errors, so windows cmd windows cannot display them. I am not really using a IDE.. (I am installing eclipse right now.. but while I am doing that my curiosity drove me to post here..)

Is there a solution so that I can split the screen so that the screen pauses when the compiling error takes up 1 command window size? or can I output the compile error message the a file?

[kjkrum]

Easy enough on Linux. Perhaps the Windows command shell is similar.

You could pipe the output of javac to the 'more' program, which pauses between pages of output: javac YourClass.java | more

(Linux also has an improved version of 'more' called 'less', but I doubt Windows has that.)

Or you could redirect javac's output to a text file: javac YourClass.java > errors.txt

[JimmyD]

hi kjkrum!

Thanks for the reply. I've tried those approaches, but they don't work. I came to the conclusion that in windows cmd, the error messages is in a different stream from that in linux?

What I mean is that I can't pipe the compile errors or redirect them to be put in a file.

By the way, windows has more but no less=)

[kjkrum]

Hmm. The last Windows I really used was XP, and it had redirection. Microsoft Windows XP - Using command redirection operators What version are you using? Hopefully someone with more up-to-date Windows knowledge can help you.

Edit: maybe you need to specify 2 for the error channel: javac YourClass.java 2> errors.txt

[JimmyD]

That unfortunately doesn't work either >..<

javac: invalid flag: 2
Usage: javac <options> <source files>
use -help for a list of possible options

[DarrylBurke]

There are two varieties of the Command prompt: command.com and cmd.exe. Have you tried both?

db

[Tolls]

You can increase the screen buffer in the properties menu of the command terminal.
Just give it a 1000 line buffer (or more).

[JimmyD]

There are two varieties of the Command prompt: command.com and cmd.exe. Have you tried both?

db

I tried both, before I was doing right click on folder and chose "open command window here", now I typed "command" in start menu or "cmd" in start menu and started both command and cmd, unless I was not starting them right.. but it doesn work..

[JimmyD]

You can increase the screen buffer in the properties menu of the command terminal.
Just give it a 1000 line buffer (or more).

Tolls, I can't find the property to set the buffer size.. it only lets me to set history buffer size, changing which does not help to increase the execution output buffer. I am googling it though.. I am surprised javac does not have a good option here.. >..<

[JimmyD]

aha~ I found it after bit of googling.. "screen buffer size".. lol~ problem solved! Thanks Tolls!

[DarrylBurke]

I just tried what kjkrum suggested at #4 (after first commenting a variable declaration in a source file) and the error output was written to a file. Windows 7, Java 6.

javac FileName.java 2> errors.txt

If you're getting

javac: invalid flag: 2

it looks like you put a dash (-) ahead of the 2.

db

[JimmyD]

I just tried what kjkrum suggested at #4 (after first commenting a variable declaration in a source file) and the error output was written to a file. Windows 7, Java 6.

javac FileName.java 2> errors.txt

If you're gettingit looks like you put a dash (-) ahead of the 2.

db

I got it this time.. 2> muz be connected.. forgot about that! Thanks everyone for helping me out!