> Try it sometime; fire up vi on a file, escape via :sh
> resize the window, and ^D out of the subshell. Vi
> won't realize the window's size has changed.
Possibly the same issue (but without a subshell):
Start vi with some file, start a search via '/',
resize the window, complete the '/' searc
Alan Coopersmith writes:
> > The distinction is that window size isn't an environment string. It's
> > a property known to the tty subsystem. Since this is shared between
> > the job that's stuck in wait(2) (i.e., vi) and the job that's running,
> > it's at least feasible to have vi check for cha
James Carlson wrote:
Larry Becke writes:
Resize the window while in vi, before you run the sub-shell
The distinction is that window size isn't an environment string. It's
a property known to the tty subsystem. Since this is shared between
the job that's stuck in wait(2) (i.e., vi) and th
Larry Becke writes:
> Resize the window while in vi, before you run the sub-shell
The distinction is that window size isn't an environment string. It's
a property known to the tty subsystem. Since this is shared between
the job that's stuck in wait(2) (i.e., vi) and the job that's running,
i
When you *escape* to a shell, you are running a subshell. Any changes to the
environment while running a sub-shell are lost - ie not passed back to the
parent when you exit.
It would be like running a sub-shell that changes IFS, then expecting the
changed IFS to apply to the parent shell..
Re
