Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

Java Java Basics Perfecting the Prototype Censoring Words - Using Logical ORs

Michael Franklin
Michael Franklin
308 Points

I have noticed an issue with the workspaces regarding console instructions, anyone know a fix?

I am using a macintosh with safari, and i have noticed that when in console if you try to use the back arrows to edit, delete or change instructions. Well the console becomes very confused. IE

Input:

treehouse:~/workspace$ clear && javac TreeStory.Jaca && java TreeStory

As you can see above i accidentally hit C instead of V in Java. If i utilize the arrow keys to go back and fix this the making it

input:

treehouse:~/workspace$ clear && javac TreeStory.Java && java TreeStory

My output will then be this

Output:

Picked up JAVA_TOOL_OPTIONS: -Xmx128m
Picked up _JAVA_OPTIONS: -Xmx128m
error: Class names, 'TreeStory.Javca', are only accepted if annotation processing is e xplicitly requested
1 error

This issue is persistent when using arrow keys to scroll through previously entered commands as-well.

1 Answer

I've been dealing with this problem for so long now so I feel your pain. The only solution I have found is to close the console window by clicking on the "x" within the workspace (NOT the workspace's browser window!) and opening it again by going to "View" -> "Show console". That should restart the console and get rid of that bug while keeping the history of previously entered commands. Hope that helps.