alwayslastprompt problem

alwayslastprompt problem

[Greg Klanderman]

Hi,

In upgrading to zsh 4.0.6 I noticed the following problem:
When run, the script below does not obey alwayslastprompt.

---
#!/phl/build/zsh-4.0.6/Src/zsh -f

setopt alwayslastprompt

prompt="foo%B%%%b "
while cmd="" && vared -h -p "$prompt" cmd ; do 
  echo " -- got: $cmd"
  print -s - "$cmd"
done
---

However, if I run "zsh -f" and paste the contents, then
alwayslastprompt does work correctly (same zsh binary).

What's going on?  

Please include me in any reply as I am not on the list.

many thanks,
Greg

Re: alwayslastprompt problem

[Bart Schaefer]

On Feb 3,  5:05pm, Greg Klanderman wrote:
} 
} What's going on?  

The alwayslastprompt option does not apply to non-interactive shells.  A
script is not "interactive", even if it calls "vared".  If the shell from
which you are calling the script is also zsh, try autoloading the script
as a shell function instead of running it as a separate process.

Re: alwayslastprompt problem

[Greg Klanderman]

Hi Bart,

Is there any reason zsh couldn't handle alwayslastprompt in this
situation?  The other completion options seem to work in this context.

Using a shell function is not really an option.  While I run zsh as my
interactive shell, others here do not.

I can certainly live without alwayslastprompt, but it would be
preferable... 

thanks to you and the other zsh workers for continuing to produce
such a truly incredible shell,
Greg



>>>>> Bart Schaefer <schaefer@brasslantern.com> writes:

> On Feb 3,  5:05pm, Greg Klanderman wrote:
> } 
> } What's going on?  

> The alwayslastprompt option does not apply to non-interactive shells.  A
> script is not "interactive", even if it calls "vared".  If the shell from
> which you are calling the script is also zsh, try autoloading the script
> as a shell function instead of running it as a separate process.

Re: alwayslastprompt problem

[Bart Schaefer]

On Feb 3, 11:26pm, Greg Klanderman wrote:
}
} Is there any reason zsh couldn't handle alwayslastprompt in this
} situation?

It appears to be an order-of-initialization issue.  In a non-interactive
shell, the terminal isn't set up until vared is actually invoked, and
for some reason that causes the ZLE refresh routines to believe that it
isn't possible to do alwayslastprompt.

I haven't figured out exactly what is different in the two cases.

Re: alwayslastprompt problem

[Greg Klanderman]

Interesting.. if you haven't figured it out I'll probably look 
into this sometime but not for at least a week or two.

greg


>>>>> Bart Schaefer <schaefer@brasslantern.com> writes:

> On Feb 3, 11:26pm, Greg Klanderman wrote:
> }
> } Is there any reason zsh couldn't handle alwayslastprompt in this
> } situation?

> It appears to be an order-of-initialization issue.  In a non-interactive
> shell, the terminal isn't set up until vared is actually invoked, and
> for some reason that causes the ZLE refresh routines to believe that it
> isn't possible to do alwayslastprompt.

> I haven't figured out exactly what is different in the two cases.