On 2011-05-06, Tony Mechelynck wrote:
> - I *think* it would also be better to avoid starting any GUI program
> from a gvim shell command.
Doing that should be OK. The GUI program will inherit gvim's
environment, which was good enough to start gvim, so it should be
good enough to start any othe
On 05/05/11 20:05, David Ohlemacher wrote:
OK, thanks for the help link.
It does say commands like ls and grep mostly work fine. But it seems
only for a very bare-bones shell. I was hoping it was possible to get
rudimentary commands like ls to work. Is there a way to configure my
.gvimrc file to
Interesting...
Thanks Tim. I'll play with it. I could specify a --init-file as well
with that, if needed.
-d
On 05/05/2011 01:24 PM, Tim Chase wrote:
On 05/05/2011 12:09 PM, Jean-Rene David wrote:
You seem to use 'shell' and 'terminal' interchangeably. They
are not the same thing. 'tcsh'
OK, thanks for the help link.
It does say commands like ls and grep mostly work fine. But it seems
only for a very bare-bones shell.I was hoping it was possible to get
rudimentary commands like ls to work.Is there a way to configure my
.gvimrc file to use another special initializatio
On 05/05/2011 12:09 PM, Jean-Rene David wrote:
You seem to use 'shell' and 'terminal' interchangeably. They
are not the same thing. 'tcsh' and 'bash' are shells, not
terminals.
It doesn't matter *how* you start gvim. You will always get a
limited functionality terminal from it.
You can hack ar
* David Ohlemacher [2011.05.05 12:30]:
> Hi all,
>
> When I use ":sh" within gvim, I see this:
>
>:sh
>Warning: no access to tty (Inappropriate ioctl for device).
>Thus no job control in this shell.
>?codes> ?
When you type ':sh' from gvim, you are provided a rather rudimenta
Hi all,
When I use ":sh" within gvim, I see this:
:sh
Warning: no access to tty (Inappropriate ioctl for device).
Thus no job control in this shell.
? ?
At this point, I can enter commands, but the shell is broken. Backspace
key only adds ^H. Letters typed overwrite each other. ls
