Re: vi editing at bash command line: cc command doesn't work

2014-09-10 Thread Bob McGowan
On 9/10/14, 6:36 AM, "Mr. Bob 2001" wrote: >vim 7.4.417-1 OK > >Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1 > >Cygwin DLL version info: >DLL version: 1.7.32 > >cc in vi or vim, or gvim Works for me, on 64-bit, without admin rights. > >PS. Thanks fo

Re: vi editing at bash command line: cc command doesn't work

2014-09-10 Thread Mr. Bob 2001
vim 7.4.417-1   OK Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1     Cygwin DLL version info:     DLL version: 1.7.32 cc in vi or vim, or gvim Works for me, on 64-bit, without admin rights. PS. Thanks for prompting me to finally notice the mirror I was using

Re: vi editing at bash command line: cc command doesn't work

2014-09-09 Thread Paul . Domaskis
Gary Johnson spocom.com> writes: > I have both 32-bit and 64-bit versions of Cygwin installed on a > Windows 7 Enterprise SP1 system. I can confirm that using a Cygwin > Terminal, cc works on the 32-bit installation but not on the 64-bit > installation. > > There is no connection between the vi

Re: vi editing at bash command line: cc command doesn't work

2014-09-09 Thread Gary Johnson
I have both 32-bit and 64-bit versions of Cygwin installed on a Windows 7 Enterprise SP1 system. I can confirm that using a Cygwin Terminal, cc works on the 32-bit installation but not on the 64-bit installation. There is no connection between the vi mode of the bash command line and Vim. Regard

Re: vi editing at bash command line: cc command doesn't work

2014-09-09 Thread Bob McGowan
I have the same problem. My system details (abbreviated): Windows 7 Home Premium Ver 6.1 Build 7601 Service Pack 1 Cygwin installations found in the registry: System: Key: e022582115c10879 Path: C:\cygwin64 User: Key: e022582115c10879 Path: C:\cygwin64 Cygwin DLL version info: DL

Re: vi editing at bash command line: cc command doesn't work

2014-09-09 Thread Paul . Domaskis
writes: > writes: >> I needed cygwin on a new work computer that was locked down. I >> created a DVD from all the 64-bit packages some time in the first >> quarter of 2014, then took the several months needed to get >> approval for its installation. I then replicated the environment >> from an o

Re: vi editing at bash command line: cc command doesn't work

2014-09-08 Thread Paul . Domaskis
writes: > I needed cygwin on a new work computer that was locked down. I > created a DVD from all the 64-bit packages some time in the first > quarter of 2014, then took the several months needed to get approval > for its installation. I then replicated the environment from an old > work compute

vi editing at bash command line: cc command doesn't work

2014-09-08 Thread Paul . Domaskis
vi editing at bash command line: cc command doesn't work - I needed cygwin on a new work computer that was locked down. I created a DVD from all the 64-bit packages some time in the first quarter of 2014, then took the several months n

Re: at + bash

2002-02-10 Thread Christopher Faylor
On Sun, Feb 10, 2002 at 04:19:47PM +, Don Sharp wrote: > > >Christopher Faylor wrote: >> >> On Sat, Feb 09, 2002 at 02:34:11PM -0500, David Means wrote: >> >Try: >> > >> >mkdir /tmp >> > >> >mount /cygdrive/c/tmp /tmp >> >> Uh, no. There is no need for the mount command. It will royally co

Re: at + bash

2002-02-10 Thread Don Sharp
Christopher Faylor wrote: > > On Sat, Feb 09, 2002 at 02:34:11PM -0500, David Means wrote: > >Try: > > > >mkdir /tmp > > > >mount /cygdrive/c/tmp /tmp > > Uh, no. There is no need for the mount command. It will royally confuse > things if you use it. > Why Chris? I have been using the foll

Re: Followup: at + bash

2002-02-10 Thread Randall R Schulz
David, Use a system mount, and all users will "see" it. % mount --help ... -s, --systemadd mount point to system-wide registry location -u, --user (default) add mount point to user registry location ... Randall Schulz Mountain View, CA USA At 06:22 2002-02-10, David wrote: >Hel

Followup: at + bash

2002-02-10 Thread David
Hello > I am having a problem running perl in an at command on windows nt > because perl says it can't find some @INC libs I added. So, I'm > trying to run perl in a bash shell: Thanks for the answers. The problem is that I installed cygwin as Administrator and at commands run as SYSTEM. So,

Re: at + bash

2002-02-09 Thread Christopher Faylor
On Sat, Feb 09, 2002 at 02:34:11PM -0500, David Means wrote: >Try: > >mkdir /tmp > >mount /cygdrive/c/tmp /tmp Uh, no. There is no need for the mount command. It will royally confuse things if you use it. /tmp is created by setup.exe. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsub

Re: at + bash

2002-02-09 Thread David Means
Try: mkdir /tmp mount /cygdrive/c/tmp /tmp David wrote: > > Hello > > I am having a problem running perl in an at command on windows nt > because perl says it can't find some @INC libs I added. So, I'm > trying to run perl in a bash shell: > > at 12:00 /every:M,T cmd /c "bash -c 'p

at + bash

2002-02-09 Thread David
Hello I am having a problem running perl in an at command on windows nt because perl says it can't find some @INC libs I added. So, I'm trying to run perl in a bash shell: at 12:00 /every:M,T cmd /c "bash -c 'perl script.pl'" However, bash will not start, saying: bash.exe: warn