Greetings, Buchbinder, Barry (NIH/NIAID) [E]!
> Andrey Repin sent the following at Tuesday, September 09, 2014 9:08 AM
>>That makes little sense. Could be solved, though. CMD doesn't offer a
>>way to distinguish between file and directory, but we have test.
> Every directory contains a virtual fi
Andrey Repin sent the following at Tuesday, September 09, 2014 9:08 AM
>That makes little sense. Could be solved, though. CMD doesn't offer a
>way to distinguish between file and directory, but we have test.
Every directory contains a virtual file named nul (note: only one L;
serves the function o
Greetings, Gary Johnson!
>> @START "" /D "%~1" "%~dp0\mintty.exe"
>> > - run_bash_here.sh -
>> >
>> This all is just not needed.
>> Just create a shortcut in "Sent to" to your bas
On 09/09/2014 03:15 AM, Achim Gratz wrote:
>
> If you want to get this right, you should work it out from the inside.
> You want the cd command to get a directory name from a subcommand that
> may contain spaces, so you need to quote the result:
>
> cd "$( ... )"
>
If you want to also guarante
Gary Johnson writes:
> After much fiddling (programming by successive approximation),
You should drop the cargo-cult programming before it hurts you.
> I came up with this:
>
> @START "" "C:\cygwin\bin\mintty.exe" /bin/bash --login -c "cd $(cygpath
> -u $0); exec bash -i" "%~p1\"
You want a
On 2014-09-08, Gary Johnson wrote:
> On 2014-09-09, Andrey Repin wrote:
> > Greetings, Gary Johnson!
> >
> > > I wrote a batch file and a shell script to implement a Run Bash Here
> > > feature from the Windows file manager "Send to" context menu, much
> > > like chere but without having to mess w
On 2014-09-09, Andrey Repin wrote:
> Greetings, Gary Johnson!
>
> > I wrote a batch file and a shell script to implement a Run Bash Here
> > feature from the Windows file manager "Send to" context menu, much
> > like chere but without having to mess with the registry. The
> > hardest part was get
Greetings, Gary Johnson!
> I wrote a batch file and a shell script to implement a Run Bash Here
> feature from the Windows file manager "Send to" context menu, much
> like chere but without having to mess with the registry. The
> hardest part was getting the quoting in the run command line right
On 2014-09-08, Gary Johnson wrote:
> On 2014-09-06, Gary Johnson wrote:
> > On 2014-09-05, Gerry Reno wrote:
> >
> > > To clarify this request a bit:
> > >
> > > Both run-1.2.0-1 and 1.3.1-1 are broken. Neither one properly runs a
> > > command.
> > > The only recent package that actually worke
On 2014-09-06, Gary Johnson wrote:
> On 2014-09-05, Gerry Reno wrote:
>
> > To clarify this request a bit:
> >
> > Both run-1.2.0-1 and 1.3.1-1 are broken. Neither one properly runs a
> > command.
> > The only recent package that actually worked was run-1.3.0-1.
>
> That has not been my experi
Greetings, Gerry Reno!
> On 09/06/2014 04:12 PM, Gary Johnson wrote:
>> On 2014-09-05, Gerry Reno wrote:
>>
>>> To clarify this request a bit:
>>>
>>> Both run-1.2.0-1 and 1.3.1-1 are broken. Neither one properly runs a
>>> command.
>>> The only recent package that actually worked was run-1.3.0-
Greetings, Gary Johnson!
>> To clarify this request a bit:
>>
>> Both run-1.2.0-1 and 1.3.1-1 are broken. Neither one properly runs a
>> command.
>> The only recent package that actually worked was run-1.3.0-1.
> That has not been my experience. In my experience, run-1.2.0-1
> works fine but
On 09/06/2014 04:12 PM, Gary Johnson wrote:
> On 2014-09-05, Gerry Reno wrote:
>
>> To clarify this request a bit:
>>
>> Both run-1.2.0-1 and 1.3.1-1 are broken. Neither one properly runs a
>> command.
>> The only recent package that actually worked was run-1.3.0-1.
> That has not been my experie
On 2014-09-05, Gerry Reno wrote:
> To clarify this request a bit:
>
> Both run-1.2.0-1 and 1.3.1-1 are broken. Neither one properly runs a command.
> The only recent package that actually worked was run-1.3.0-1.
That has not been my experience. In my experience, run-1.2.0-1
works fine but 1.3.
On 06/09/14 02:14, Gerry Reno wrote:
Can run-1.3.0-1 be added back into the Setup as an alternate choice until 'run'
can be fixed?
You should be able to get run-1.3.0 from the Cygwin Time Machine [1].
Based on the file timestamps of various versions of 'run', try dates in
the range August 20
On 09/05/2014 09:14 PM, Gerry Reno wrote:
> On 09/03/2014 03:48 PM, Achim Gratz wrote:
>> Gerry Reno writes:
>>> On the 32-bit system cygwin installs that haven't been updated yet
>>> 'run.exe' shows:
>>>
>>> $ ls -l /usr/bin/run.exe
>>> -rwxr-xr-x 1 Administrator None 65053 Jul 24 2013 /
On 09/03/2014 03:48 PM, Achim Gratz wrote:
> Gerry Reno writes:
>> On the 32-bit system cygwin installs that haven't been updated yet 'run.exe'
>> shows:
>>
>> $ ls -l /usr/bin/run.exe
>> -rwxr-xr-x 1 Administrator None 65053 Jul 24 2013 /usr/bin/run.exe
>>
>> On a 32-bit system with this
On 09/03/2014 03:48 PM, Achim Gratz wrote:
> cygcheck -f /usr/bin/run.exe
Working systems:
$ cygcheck -f /usr/bin/run.exe
run-1.3.0-1
Broken systems:
$ cygcheck -f /usr/bin/run.exe
run-1.3.1-1
Your guess was correct.
Gerry
--
Problem reports: http://cygwin.com/prob
Gerry Reno writes:
> On the 32-bit system cygwin installs that haven't been updated yet 'run.exe'
> shows:
>
> $ ls -l /usr/bin/run.exe
> -rwxr-xr-x 1 Administrator None 65053 Jul 24 2013 /usr/bin/run.exe
>
> On a 32-bit system with this latest cygwin 'run.exe' shows:
>
> $ ls -l /usr
Gerry Reno writes:
[...]
> On the 32-bit system cygwin installs that haven't been updated yet
'run.exe' shows:
>
> $ ls -l /usr/bin/run.exe
> -rwxr-xr-x 1 Administrator None 65053 Jul 24 2013 /usr/bin/run.exe
>
> On a 32-bit system with this latest cygwin 'run.exe' shows:
>
> $ ls -
On 09/02/2014 08:59 PM, Gerry Reno wrote:
> On 09/02/2014 01:50 PM, Marco Atzeri wrote:
>>
>> On 02/09/2014 19:37, Achim Gratz wrote:
>>> Gerry Reno writes:
I have a script that issues this command:
run $WINDIR/system32/mstsc.exe /multimon /v:$IP:3389
And before
On 09/02/2014 01:50 PM, Marco Atzeri wrote:
>
>
> On 02/09/2014 19:37, Achim Gratz wrote:
>> Gerry Reno writes:
>>> I have a script that issues this command:
>>>
>>> run $WINDIR/system32/mstsc.exe /multimon /v:$IP:3389
>>>
>>>
>>> And before this script has always succeeded but now it errors
On 02/09/2014 19:37, Achim Gratz wrote:
Gerry Reno writes:
I have a script that issues this command:
run $WINDIR/system32/mstsc.exe /multimon /v:$IP:3389
And before this script has always succeeded but now it errors as follows:
Invalid connection file (/v:192.168.1.27:3389) spec
Gerry Reno writes:
> I have a script that issues this command:
>
> run $WINDIR/system32/mstsc.exe /multimon /v:$IP:3389
>
>
> And before this script has always succeeded but now it errors as follows:
>
> Invalid connection file (/v:192.168.1.27:3389) specified
>
> In a terminal window I ca
I just updated to the latest cygwin via setup and now my run commands are
failing.
I have a script that issues this command:
run $WINDIR/system32/mstsc.exe /multimon /v:$IP:3389
And before this script has always succeeded but now it errors as follows:
Invalid connection file (/v:192.
25 matches
Mail list logo
