Tom Rodman wrote:
On Thu 8/28/08 22:38 +0200 Reini Urban wrote:
Larry Hall (Cygwin) schrieb:
There hasn't been any effort to support Windows paths in Cygwin for a long
time. That doesn't mean it wouldn't have worked sometime in the past.
it worked in cygwin 1.5.19-4
A nice long ride it h
On Thu 8/28/08 22:38 +0200 Reini Urban wrote:
> Larry Hall (Cygwin) schrieb:
> > There hasn't been any effort to support Windows paths in Cygwin for a long
> > time. That doesn't mean it wouldn't have worked sometime in the past.
it worked in cygwin 1.5.19-4
> > It's just that doing so is not
Larry Hall (Cygwin) schrieb:
There hasn't been any effort to support Windows paths in Cygwin for a long
time. That doesn't mean it wouldn't have worked sometime in the past.
It's
just that doing so is not a goal of this project. Use the POSIX form of
the
path and will work nicely for you -
Tom Rodman wrote:
Greetings:
~ $ date;cygcheck -c cygwin
Sun Aug 24 11:37:36 CDT 2008
Cygwin Package Information
Package VersionStatus
cygwin 1.5.25-15 OK
~ $ "$COMSPEC"
-bash: D:\WINNT\system32\cmd.exe: command not found
~ $ ls -l "$COMSPE
patrickinminneapolis wrote:
I modified Cygwin.bat to the following,
bash --login -i -c 'cd /cygdrive/c && exec bash'
and it still exits.
I think you can get the effect you want by changing your home directory
in /etc/passwd to /cygdrive/c
--
Unsubscribe info: http://cygwin.com/ml/#unsu
On 26 September 2007 15:09, patrickinminneapolis wrote:
> I modified Cygwin.bat to the following,
> bash --login -i -c 'cd /cygdrive/c && exec bash'
> and it still exits.
Use double quotes; this batch file is parsed by cmd.exe, which doesn't
recognize single quotes, but it does recognise the '&
I modified Cygwin.bat to the following,
bash --login -i -c 'cd /cygdrive/c && exec bash'
and it still exits.
--
View this message in context:
http://www.nabble.com/Bash--c-without-exiting-tf4518164.html#a12901775
Sent from the Cygwin Users mailing list archive at Nabble.com.
--
Unsubscrib
On Tue, 25 Sep 2007, patrickinminneapolis wrote:
> I'd like to drop to the current directory like this,
>
> bash --login -i -c 'Drop to current directory'
>
> without exiting cygwin. Thanks.
Not Cygwin-specific. Try
bash --login -i -c 'cd /tmp && exec bash'
HTH,
Igor
--
On 28 February 2006 03:04, Igor Peshansky wrote:
> On Mon, 27 Feb 2006, Poor Yorick wrote:
>
>> Greetings, Cygwin users,
>>
>> From a terminal:
>>
>> [EMAIL PROTECTED] ~yorickp1 21:43:48
>> $bash -c "echo $1" yada
>>
>> [EMAIL PROTECTED] ~yorickp1 21:43:52
>> $bash -c "echo $*" bri
On Mon, 27 Feb 2006, Poor Yorick wrote:
Greetings, Cygwin users,
From a terminal:
[EMAIL PROTECTED] ~yorickp1 21:43:48
$bash -c "echo $1" yada
[EMAIL PROTECTED] ~yorickp1 21:43:52
$bash -c "echo $*" bright sunshiny day
[EMAIL PROTECTED] ~yorickp1 21:45:54
Shouldn't I have
Eric Blake wrote
This was just a minimal test case.
$ bash -c time ls
Segmentation fault (core dumped)
That is equivalent to 'bash -c time', except that $0 is set to "ls"
instead of "bash" or "time" for the duration of the command
Oh, I wasn't aware of that. Thanks for explanation.
Krzyszt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Krzysztof Duleba on 1/10/2006 7:14 AM:
>
> This was just a minimal test case.
>
> $ bash -c time ls
> Segmentation fault (core dumped)
That is equivalent to 'bash -c time', except that $0 is set to "ls"
instead of "bash" or "time" for t
Krzysztof Duleba wrote:
> > near future. In the meantime, avoid invalid uses of time (POSIX states
> > that time takes a mandatory argument of the utility name to run; the
> > bash
> > extension of letting time take no arguments was the culprit here).
>
> This was just a minimal test case.
I th
Eric Blake
Thanks for the backtrace. I'll see about rolling a bash 3.0-15 in the
near future. In the meantime, avoid invalid uses of time (POSIX states
that time takes a mandatory argument of the utility name to run; the
bash
extension of letting time take no arguments was the culprit here).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Brian Dessent on 1/9/2006 10:29 AM:
>
>>$ bash -c time
>>Segmentation fault (core dumped)
>>
>
> This looks like a bash bug. It looks like only 3.0 is affected, as it works
> fine in 3.1. Since 'time' is a builtin, it appears to be a b
Dave Korn wrote:
Just try running 'time' from the bash prompt. You get a SEGV from
strlen
AFAICT.
No, I don't. But I do get a strange behaviour with
time for ((i=0;i<=100++)) do :; done
It works fine if you fix the bug :)
I know, which is even more amusing.
Krzysztof Duleba
--
Krzysztof Duleba wrote:
> Christopher Faylor wrote:
>
>>> $ bash -c time
>>> Segmentation fault (core dumped)
>>>
>>> $ uname -a
>>> CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
>>> unknown Cygwin
>>>
>>> Reproduced on several machines. I wonder what can it be.
>>
>> J
Christopher Faylor wrote:
$ bash -c time
Segmentation fault (core dumped)
$ uname -a
CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
unknown Cygwin
Reproduced on several machines. I wonder what can it be.
Just try running 'time' from the bash prompt. You get a SEGV fro
Krzysztof Duleba wrote:
> $ bash -c time
> Segmentation fault (core dumped)
>
> $ uname -a
> CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
> unknown Cygwin
This looks like a bash bug. It looks like only 3.0 is affected, as it works
fine in 3.1. Since 'time' is a builtin
Christopher Faylor wrote:
> Just try running 'time' from the bash prompt. You get a SEGV from strlen
> AFAICT.
>
> This doesn't seem to have anything to do with "-c". It seems to be an
> issue with the time command.
Not my experience:
[EMAIL PROTECTED] ~
$ time
real0m0.000s
user0m0.0
On Mon, Jan 09, 2006 at 05:13:54PM +0100, Krzysztof Duleba wrote:
>$ bash -c time
>Segmentation fault (core dumped)
>
>$ uname -a
>CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
>unknown Cygwin
>
>Reproduced on several machines. I wonder what can it be.
Just try running 'ti
> >Chris F.: Please do write that book!
>
> I'm negotiating as fast as I can. :-)
>
> cgf
Would it help if everyone politely asked the potential publisher "when" they'll ever
have a Cygwin book?
;-)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http
On Sun, Oct 20, 2002 at 03:10:45PM -0400, Scott Prive wrote:
>> >Chris F.: Please do write that book!
>>I'm negotiating as fast as I can. :-)
>
>Would it help if everyone politely asked the potential publisher "when"
>they'll ever have a Cygwin book?
:-) So far, I think everyone is convinced.
I
On Sun, Oct 20, 2002 at 08:55:53AM -0700, Randall R Schulz wrote:
>I'm not completely well-versed on this detail, but I'm under the impression
>that the interpretation of "*" is different when a Cygwin command is
>invoked directly from a Windows CMD.exe. (In a fully Cygwin context, the
>shell it
G,
At 08:37 2002-10-20, g frances wrote:
Hi,
I'm new to cygwin and have a simple question. Tried to find the answer on
the mailing list search archive, but no luck. I've just downloaded the
lastest version of Cygwin on Windows 2000 Professional, SP2. When trying
to invoke a command at the N
25 matches
Mail list logo
