Brian Dessent wrote:
Lennart Borgman wrote:
I do not remember anything about this now, but comparing to my current
PS1 I can see that I has a \] after the last m. I have
PS1=\[\033[32;47m\w >\033[0m\]
That's incorrect. The \[ and \] are to be used only to delineate
nonprinting s
Lennart Borgman wrote:
> Thanks very much this! However I still have problem with long commands.
> I start Cygwin with
>
> ** cygwin.cmd:
> @echo off
> set chere_invoking=1
> D:\cygwin\bin\bash --login -i
>
> When the command wraps into the next line then I can not edit the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 10/19/2005 11:11 AM:
>>utimes(dest,...); // at this point, timestamp is correct
>>fchmod(dest_desc,...);
>>close(dest_desc); // oops, timestamp changed
>
>
> Apparently NT overwrites the mtime timestamp on close, as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Lennart Borgman on 10/19/2005 4:40 PM:
> If I do
>
> info bash
>
> from the bash prompt and try to open "*Bash Features::" I get the error
> message in the subject line.
>
> Is this expected or a known bug?
It works for me. You'll ha
Volker Quetschke wrote:
Christopher Faylor wrote:
On Wed, Oct 19, 2005 at 03:45:30PM -0400, Volker Quetschke wrote:
(snip)
Given the number of changes that have been made to cygwin, particularly
in /proc handling, it's very difficult for me to believe that you are
not seeing *any* differences in
Hi,
I'm using g++ on cygwin for developping some c++
programs.
I noticed that everytime i manipulate pointers i have
an error saying:
"Segmentation Fault ".
An other file is added to the working directory. If i
compile with the following:
g++ -o file_name file_name.cc
i have a file_name.exe but
On Oct 20 06:17, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Corinna Vinschen on 10/19/2005 11:11 AM:
> >>utimes(dest,...); // at this point, timestamp is correct
> >>fchmod(dest_desc,...);
> >>close(dest_desc); // oops, timestamp changed
> >
> >
> > Ap
On Thu, Oct 20, 2005 at 08:48:05AM -0400, Volker Quetschke wrote:
>Volker Quetschke wrote:
>>Christopher Faylor wrote:
>>>On Wed, Oct 19, 2005 at 03:45:30PM -0400, Volker Quetschke wrote:
>>>(snip)
>>>Given the number of changes that have been made to cygwin, particularly
>>>in /proc handling, it's
On Thu, Oct 20, 2005 at 06:17:17AM -0600, Eric Blake wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>According to Corinna Vinschen on 10/19/2005 11:11 AM:
>>>utimes(dest,...); // at this point, timestamp is correct
>>>fchmod(dest_desc,...);
>>>close(dest_desc); // oops, timestamp change
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to community help on 10/20/2005 7:06 AM:
> Hi,
>
> I'm using g++ on cygwin for developping some c++
> programs.
>
> I noticed that everytime i manipulate pointers i have
> an error saying:
> "Segmentation Fault ".
Well, it's because you ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> It's not POSIX!
>
> But I must admit that it exists on Linux, even though they didn't bother
> to create a man page for it.
> Corinna, I think I win the bet, right?
>
Ooh, having fun on the closed -developers list at my expense, are we? ;)
At l
Hi,
I'm sorry. After your answer i realised that my
message should be posted on a c/c++ mailing list not
in this one.
Sorry again
--- Eric Blake <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to community help on 10/20/2005 7:06 AM:
> > Hi,
> >
> >
Hi all,
the command-line completion doesn't work properly in a case-insensitive
fashion regardless of the setting:
set completion-ignore-case On
in ~/.inputrc. That issue is every time reproducible on both 32 and
64-bit Windows systems.
Is there something to work around that?
Regards,
--
Chr
Hi all,
there is a bug in this version:
Supposed, you have a file X.sh ( exactly in this spelling ).
If you enter:
vim x.sh ( also exactly in this spelling )
and write it back after any modification, the file will be
renamed even to x.sh. This behavior is very nasty if such
file is used by pr
On Thu, Oct 20, 2005 at 04:15:34PM +0200, Christoph Jeksa wrote:
>there is a bug in this version:
>
>Supposed, you have a file X.sh ( exactly in this spelling ). If you
>enter:
>
>vim x.sh ( also exactly in this spelling )
>
>and write it back after any modification, the file will be renamed even
On Wed, Oct 19, 2005 at 03:27:40PM -0700, Brian Dessent wrote:
> Brian Dessent wrote:
>
> > No, it's a red herring. The host keys should be readable only by the
> > process that runs sshd. This must be SYSTEM in order for impersonation
> > to work. Thus they should be readable only by SYSTEM, a
On Thu, 20 Oct 2005, Christopher Faylor wrote:
> On Thu, Oct 20, 2005 at 04:15:34PM +0200, Christoph Jeksa wrote:
> >there is a bug in this version:
> >
> >Supposed, you have a file X.sh ( exactly in this spelling ). If you
> >enter:
> >
> >vim x.sh ( also exactly in this spelling )
> >
> >and wr
On Thu, Oct 20, 2005 at 12:26:58PM -0400, Igor Pechtchanski wrote:
>On Thu, 20 Oct 2005, Christopher Faylor wrote:
>>On Thu, Oct 20, 2005 at 04:15:34PM +0200, Christoph Jeksa wrote:
>>>there is a bug in this version:
>>>
>>>Supposed, you have a file X.sh ( exactly in this spelling ). If you
>>>ent
Hi all,
I began typing this mail as a problem report, but thanks to a gracious reply
from Chloe Chang, it turned out that I had not yet set my HOME environment
variable to complete the installation. I'll describe the problem anyway to
help steer future Cygwin-er's clear of this issue.
I had j
On Thu, 20 Oct 2005, Jason Fritz (CO/EWU) wrote:
> Hi all,
>
> I began typing this mail as a problem report, but thanks to a gracious
> reply from Chloe Chang, it turned out that I had not yet set my HOME
> environment variable to complete the installation. I'll describe the
> problem anyway to h
> On Thu, 20 Oct 2005, Igor Pechtchanski wrote:
>
> Yes, but that doesn't guarantee that you would *run* that
> version. Again,
> the Cygwin version of bash will *not* look for
> /usr/local/etc/profile.global -- that message comes from some
> other bash.
> The analysis is correct, AFAICS.
>
>
On Thu, 20 Oct 2005, Jason Fritz (CO/EWU) wrote:
> > On Thu, 20 Oct 2005, Igor Pechtchanski wrote:
> >
> > Yes, but that doesn't guarantee that you would *run* that version.
> > Again, the Cygwin version of bash will *not* look for
> > /usr/local/etc/profile.global -- that message comes from some
> On Thu, 20 Oct 2005, Jason Fritz wrote:
>
> I don't know much about the implementation of Cygwin bash,
> but perhaps it has a bug and it's not setting HOME like it
> should? I think from the info I posted above that it's
> clearly not working as intended.
Some more (possibly) interesting in
On Oct 20 06:17, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Corinna Vinschen on 10/19/2005 11:11 AM:
> >>utimes(dest,...); // at this point, timestamp is correct
> >>fchmod(dest_desc,...);
> >>close(dest_desc); // oops, timestamp changed
> >
> >
> > Ap
On Thu, 20 Oct 2005, Igor Pechtchanski wrote:
>
> Hmm, very weird. According to a couple of Google searches, the above
> looks like a message from UWin startup files -- Cygwin does
> *not* have a
> profile.global, and the Cygwin bash won't look for anything in
> /usr/local/etc by default. Do yo
Krzysztof Duleba wrote:
>
> After upgrading to 20051019, perl doesn't work as it used to in the
> windows shell.
20051020 looks better, thanks.
Krzysztof Duleba
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com
Hi everyone,
I posted this a few days ago with no responses. If anyone out there has
managed to get cygrunsrv to restart using the XP/2000 recovery I would be
really interested - I'm getting desperate! Details of my problem are
below...
cygrunsrv V1.10
Windows XP
I'm having real trouble getting
Hi,
In a previous message I reported that rxvt was converting Shift-h to
Ctrl-h. It was not so. The problem is due to a bug in rxvt.bat and to
the peculiar way rxvt handles the BackSpace key.
In rxvt without options the BackSpace key yields "^?" and Crtl-BackSpace
yields "^H". In the shell `stty -a
Christopher Faylor wrote:
On Thu, Oct 20, 2005 at 04:15:34PM +0200, Christoph Jeksa wrote:
Supposed, you have a file X.sh ( exactly in this spelling ). If you
enter:
vim x.sh ( also exactly in this spelling )
and write it back after any modification, the file will be renamed even
to x.sh.
On 10/20/05, Albert Lunde <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 19, 2005 at 03:27:40PM -0700, Brian Dessent wrote:
> > > No, it's a red herring. The host keys should be readable only by the
> > > process that runs sshd. This must be SYSTEM in order for impersonation
> > > to work. Thus they s
Glen Burson wrote:
[snip]
> I'm having real trouble getting my service to restart on failure, using the
> Windows service "Recovery" options. I have set: -
>
> First Failure "Restart the Service"
[snip]
> Windows logs in the Event Viewer that the service terminated (gracefully,
> error code 0) but
Christoph Jeksa wrote:
> the command-line completion doesn't work properly in a case-insensitive
> fashion regardless of the setting:
>
> set completion-ignore-case On
>
> in ~/.inputrc. That issue is every time reproducible on both 32 and
> 64-bit Windows systems.
You'll have to be more specif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Pyeron wrote:
> I am working with the Asterisk application, it uses "modules" these are
> .so files which are linked against the main executable.
>
> Asterisk will load a module, which may or may not make use of code
> exported by the main execu
On Thu, 20 Oct 2005, Yaakov S (Cygwin Ports) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Pyeron wrote:
I am working with the Asterisk application, it uses "modules" these are
.so files which are linked against the main executable.
Asterisk will load a module, which may or may n
I've been trying to get the connection multiplexing feature of openssh
to work with Cygwin without success.
I set "ControlPath /tmp/ssh_%h_%r" in ~/.ssh/config. Then I do
$ ssh -M -N -vvv host
which works fine, and there is a socket in /tmp:
$ ls -l /tmp/ssh*
srw--- 1 brian None 53 Oct 2
On Thu, 20 Oct 2005, Brian Dessent wrote:
> Érsek László wrote:
>
> > after grepping the cygwin mailing list and my up-to-date cygwin
> > installation for "nftw" and "fts_open", I thought that it could make sense
> > (and fun) to implement nftw().
>
> Unfortunately (or perhaps fortunately) the who
Paminu wrote:
"Christopher Faylor" <[EMAIL PROTECTED]> skrev i en
meddelelse ...
On Wed, Oct 19, 2005 at 04:38:43PM +0200, Paminu wrote:
I have a xfig file in:
c:\cygwin\home\test\test.fig
I can open this xfig file from the run menu like:
bash --login -e startxprog xfig c:/cygwin/home/test
I'm attempting to sync files over ssh from a Linux server to a cygwin
client. The command I issue is
rsync -avz -e ssh [EMAIL PROTECTED]:/remote_dir .
but the request hangs. I can ssh directrly to the server from the cygwin
shell. If I increase the logging level, I get:
$ rsync -az -e ssh
Alright, so the simplest solution was indeed to
switch to WinSCP client which does indeed preserve the
timestamp of the copied file correctly (and not a bad
GUI interface to boot). This resolved the
incompatibility between the -p switch from non-OpenSSH
clients and cygwin's OpenSSHD.
Thanks for
39 matches
Mail list logo
