On Tue, Aug 13, 2013 at 11:21 AM, PHILIPP, Axel, Dr. <[email protected]> wrote: > Under certain circumstances command line editing does not work properly in > emacs multiline mode. The problem occurs in the current productive version as > well. > > cp003421_run> echo $KSH_VERSION > Version AIJM 93v- 2013-07-24 > cp003421_run> cat /etc/SuSE-release > SUSE Linux Enterprise Desktop 11 (x86_64) > VERSION = 11 > PATCHLEVEL = 2 > cp003421_run> stty -a > speed 38400 baud; rows 58; columns 100; > intr = ^C; quit = ^\; erase = ^H; kill = ^U; > eof = ^D; eol2 = <undef>; eol = <undef>; > start = ^Q; stop = ^S; susp = ^Z; > rprnt = ^R; flush = ^O; werase = ^W; lnext = ^V; > -parenb -parodd cread cs5 cs6 cs7 cs8 -hupcl -cstopb -crtscts -clocal > -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -iuclc ixon > -ixany -ixoff -imaxbel icrnl > isig icanon icannon iexten echo echoe echok echoke -echonl echoctl -echoprt > -xcase -flusho -pendin -noflsh -tostop > -olcuc onlcr -onlret -ocrnl -onocr -ofill -ofdel opost > cp003421_run> set -o > Current option settings > allexport off > bgnice on > braceexpand on > clobber off > emacs on > errexit off > exec on > glob on > globstar off > gmacs off > histexpand off > ignoreeof on > interactive on > keyword off > letoctal off > log off > login_shell off > markdirs off > monitor on > multiline on > notify off > pipefail off > privileged off > rc on > restricted off > showme off > trackall off > unset on > verbose off > vi off > viraw on > xtrace off > cp003421_run> typeset -p PS1 > PS1=$'\E[1mcp003421_run>\E[0m ' > cp003421_run> echo $COLUMNS > 100 > > The next line was produced by first entering the y*_y* string, then jumping > to Pos1 and inserting "echo " > cp003421_run> eo > yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy_y > _yyyyyyyyyyyyyyyy > yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy_yyyyyyyyyyyyyyyy > > the command is executed correctly, but the command line is not readable and > contains e.g. an additional "_". The problem occurs when the character "_" > arrives at the end of the first line and the total length of the command > exceeds $COLUMNS
Mhhh... which kind of terminal do you use, e.g. what does $TERM look like ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [email protected] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) _______________________________________________ ast-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-users
