zsh script wipes out my PROMPT and RPROMPT

zsh script wipes out my PROMPT and RPROMPT

[Timothy J Luoma]

This script wipes out the PROMPT and RPROMPT

This is for zsh 3.0.5 (both the script and my login shell)


#!/usr/local/bin/zsh -f

PATH=/Users/luomat/Unix/bin:/Users/luomat:/usr/local/gnu/bin:/usr/local/bin:/bin:/usr/ucb:/usr/bin:/usr/etc:/usr:/etc

TIME=`date +"%s"`

NAME=`basename $0`

FILE=${HOME}/.$NAME.$TIME

netstat -n 				|\
	fgrep ESTABLISHED 		|\
	fgrep -v '192.42.172.2'		|\
	awk '{print $4"\t\t"$5}' > $FILE

LINES=`wc -l $FILE | awk '{print $1}'`

for i in {1..$LINES}; do

	INFO=`cat -n $FILE |\
		sed 's/ *//g' |\
			grep -w "^$i" |\
				awk '{print $2" "$3}'`
	
	echo "Line $i: $INFO"	

done

echo "Here is the file:"
cat $FILE

rm -f $FILE

exit 0

Re: zsh script wipes out my PROMPT and RPROMPT

[Bart Schaefer]

On Jan 24,  3:23pm, Timothy J Luoma wrote:
} Subject: zsh script wipes out my PROMPT and RPROMPT
}
} This script wipes out the PROMPT and RPROMPT

Can you explain further, please?

If you run this as an actual script, it -shouldn't- be able to have any
effect on your prompt at all, because it runs in a second shell.

If you run this as a shell function (e.g. by autoloading it), the "exit 0"
at the end should kill the shell entirely.

If you source or execute as a function this script from your .zlogin or
other init file, the "exit 0" will abort reading that file, which will of
course leave unfinished anything that appears later in the file.  My guess
is that this is what you're seeing, and that if you get rid of "exit 0"
then things will improve.

Another problem is that

LINES=`wc -l $FILE | awk '{print $1}'`

is changing zsh's idea of the size of your terminal; LINES is a reserved
variable name, along with COLUMNS.  You shouldn't use it as a temporary.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Re: zsh script wipes out my PROMPT and RPROMPT

[Timothy J Luoma]

	Author:        "Bart Schaefer" <schaefer@brasslantern.com>
	Original-Date: Sat, 24 Jan 1998 14:13:39 -0800
	Message-ID:    <980124141339.ZM23464@candle.brasslantern.com>

> If you run this as an actual script, it -shouldn't- be able to have any
> effect on your prompt at all, because it runs in a second shell.

It is run as an actual script


> If you run this as a shell function (e.g. by autoloading it), the "exit 0"
> at the end should kill the shell entirely.

Nope, it is its own script, chmod 755


> Another problem is that
>
> LINES=`wc -l $FILE | awk '{print $1}'`

AH... I used another variable instead.

The behavior seems to have stopped.... I'm not sure why.... but since it  
shouldn't have happened anyway....

TjL

Re: zsh script wipes out my PROMPT and RPROMPT

[Bart Schaefer]

On Jan 24,  5:29pm, Timothy J Luoma wrote:
} Subject: Re: zsh script wipes out my PROMPT and RPROMPT
}
} > LINES=`wc -l $FILE | awk '{print $1}'`
} 
} AH... I used another variable instead.
} 
} The behavior seems to have stopped.... I'm not sure why.... but since it  
} shouldn't have happened anyway....

Could be that the zsh executing the script was improperly resetting the
tty driver's idea of the terminal dimensions when it saw the assignment
to LINES.  The parent zsh would then see the new tty configuration when
the script exited, and reset its own LINES.  If LINES became sufficiently
small, zle might decide that it couldn't draw a prompt, or some such.

There were a number of changes to zsh's tty-size handling in 3.0.5 that
I still think were bad ideas; in the face of too little information, I'd
rather that the shell did nothing, rather than reconfigure the tty based
on partial data that might be wrong.  However, I can't definitely point
to any particular bug (not even this one) that is directly attributable
to the new code.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com