Again, thank you very much for taking your time to look at my problem.
On 12. aug 2005, at 21:34, Greg Guerin wrote:
Stian Lavik wrote:
Thanks very much. But this was not the problem. And I have used long
command lines before, withou getting this problem.
Please provide a complete example that demonstrates the problem,
along with
a precise description of how to cause the problem and exactly what
it looks
like.
Example that does work perfectly:
'echo asdjhasakvjnaerkufniunaiudnvai rfavuicans dofivja rpf
asdfpasodjf j fvasid fas dfasdofijasdofiasovcinsaodifnsaoidfv sd
vsdfvsodivjasodijfaosihjfasokdjhf\303\246PEORF\303\206POWeijfsavsdfs
dflajds\303246lkj\303\246p\302\250falsdijf alskdjf alksdj fasf asdf'
In this command, the line break works as expected, and resizing the
Terminal window also works as expected.
Example where trouble begins:
'java sadfljsdfaisjdfas fas dofiajsdoifjasodimosaidjfo asidjf asdf
asdfijasdofijasodfijasodifja sdf asdfoiasjdflkasjdf\303\270iasjerfoaf
sa doifjs odijf asldjf oasidjf oasidj asdfasdfasoiejf alkf aslkdjf
kdjf laskdj flksajdaslkdjf alskdjf'
In this case, as I type in the nonsense, after typing the full line,
my insertion point does start over on the last line when it is full,
in stead of jumping one line down as expected. However (important):
my java commands *executes* as expected (no arguments lost), so this
is only an annoying problem with display, it seems. And just to be
clear on this point: This is a problem *before* I hit the RETURN key,
before I actually ask Terminal to execute the command.
It is as if the Terminal does the right thing (insertion point jumps
to a new line), but it forgets to take it to new line when
displaying. This way, it sometimes gets hard to read what commands
and arguments I'm actually asking it to execute. I guess another way
to put this could be to say that if Terminal moved all display of
previous printed text upwards, there would be no problem. Somehow,
maybe Terminal *thinks* that the next available line in the display
is the same line it already is on. Sometimes it even jumps *up* a
line. (Sounds like it doesn't count the lines correctly for the
output to the window, or something.)
If I later resize the Terminal window, that helps nothing in this
latter case. It does stretch the text/change it in some way, but I
have not been able to find any particular pattern, it is very confusing.
A list of the Terminal window settings would also be helpful,
including your terminal emulation options (the TERM env-var).
Escape non-ASCII characters: On.
Option-click to position cursor: Off.
Paste newlines as carriage returns: On.
Strict VT-100 keypad behaviour: Off.
Reverse linewrap: On.
Audible bell: On.
Visual bell: Off.
Since you also have long command lines that don't show the problem, I
suggest providing an example of a long command line that DOESN'T
show the
problem, so we have a comparison.
See above
Your email program or the list-server might wrap long lines, so you're
going to have to visually indicate exactly where you actually hit the
RETURN key, and also where the incorrect line-overwriting occurs.
As for RETURN keys, I didn't hit it myself, and to where and when
Terminal decides to jump to a new line in its display when using java
as the first command is inconsistent, as far as I can see.
In short, please be specific and detailed.
One other thing to try is dragging your Terminal window wider, and
see if
it changes where the problem occurs. Resizing Terminal windows
changes the
shell-vars that indicate window size (COLUMNS and LINES), and sends
signals
to running apps that want to learn of the change.
See above.
After rereading your original description, along with your
followups, the
only thing I can think of is that some shell or environment
variable has
been incorrectly set to a CR (0x0D) when it should be a LF (0x0A). I
suggest checking your shell-startup config-files, opening them in
an editor
that can show all invisible chars.
When an isolated CR is emitted in a Terminal window, it moves the
cursor to
the beginning of the line. I'm assuming that's what you mean by
"overwrite
the text already on the same line" in your original post, though I can
imagine other line-overwriting behavior that involves backspaces.
You can demonstrate the behavior of CR-only line-terminators by
editing a
text file with multiple lines in Xcode or Project Builder, then
changing
the file's format to have CR-only line-endings. Then 'cat' the
file in
Terminal. All the lines should overwrite on a single line.
-- GG
Stian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
