Starting from a Windows Command Prompt, and using a syntax recommended
from years ago I still start a bash shell with
start /wait bin\bash (i.e. not just bin\bash)
and a mintty shell with
start bin\mintty (i.e. not just bin\mintty)
and yet experiment shows that both simplified forms in brackets "wo
I bet Comodo is the golden tip. They have introduced whitelisting
without telling anyone, and I have had very strange behaviour (strange
until that whitelist explained it) too. Including that subshell thing.
They call it 'auto-containment'. Just disable that, and done.
Wouter
On 12 July 2017 at 00
> -Original Message-
> From: Thomas Wolff
> Sent: Tuesday, July 11, 2017 1:03 AM
>
> Am 11.07.2017 um 06:43 schrieb Jason Pyeron:
> > When launching C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico -
> > (from the start menu)
> >
> > And while in the terminal I hit Ctrl-Tab, the window be
This isn't _really_ a bug, more of an oddity. Calling mkdir(2) on an
existing directory will fail with EACCES instead of EEXIST if the
directory couldn't have been created in the first place. For example,
this is the typical situation for /cygdrive/c:
mkdir("/cygdrive/c", 0700);
// errno
On 2017-07-11 19:01, Christopher Wellons wrote:
/usr/include/cygwin/signal.h:328:34: error: unknown type name
‘siginfo_t’
void (*sa_sigaction) ( int, siginfo_t *, void * );
^
Since _POSIX_C_SOURCE < 199309L, siginfo_t isn't defined. However,
A two-line source file demonstrates this bug:
#define _POSIX_C_SOURCE 1
#include
Then when compiled:
$ gcc -c tmp.c
In file included from /usr/include/sys/signal.h:22:0,
from /usr/include/signal.h:6,
from tmp.c:2:
/usr/include/cygwin/signa
At 07/11/2017 at 15:12, Shakespearean monkeys
danced on Jürgen Wagner's keyboard and said:
...
Using backquotes instead of the command
substitution with $(...) does not change the
results. I could swear this did work in an
earlier version of Cygwin on my Windows 7 machine.
I tried this to s
On Tue, 11 Jul 2017 21:12:14, =?UTF-8?Q?J=c3=bcrgen_Wagner?= wrote:
2. Windows 10, Version 1703, Build 15063.413 on a Dell 64bit platform,
latest 64bit Cygwin (CYGWIN_NT-10.0, 2.8.1(0.312/5/3) 2017-07-03 14:11
x86_64 Cygwin) /bin/bash
$ value=3D"$( date | cat )"; echo "$? <$value>"
127 <>
For
And here another little detail: I installed Babun on the Windows 10 machine.
juergen@saraswati ~
$ value="$( date | cat )"; echo $? $value
0 Tue, Jul 11, 2017 10:24:02 PM
juergen@saraswati ~
$ echo $BASH_VERSION
4.3.33(1)-release
juergen@saraswati ~
$
It works.
The BASH_VERSION on the other Cy
Eliot Moss writes:
> I looked upstream, and at least some of the files I am concerned about
> are installed using "tar" piped to another "tar", with umask 022 set
> explicitly. I think the problem is that the source of this copying
> has 600 or 700 permissions. Not sure if *that* is an upstream p
Sorry, little omission: the first example under section 3 is not with
bash, it was done with dash.
smime.p7s
Description: S/MIME Cryptographic Signature
Hello,
this is my first posting here as I do not see any other hope of
getting this resolved. Research in mailing lists and other Cygwin users'
questions on various sites have not proven to be useful.
1. Ubuntu 4.4.0-71-generic x86_64, /bin/bash
$ value="$( date | cat )"; echo "$? <$value>"
0
On 7/11/2017 11:10 AM, Garber, Dave (GE Oil & Gas, Non-GE) wrote:
>
>
>> -Original Message-
>> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
>> Behalf Of jeff
>> Sent: Tuesday, July 11, 2017 1:56 PM
>> To: cygwin@cygwin.com
>> Subject: EXT: Re: problem with gnupg2 not
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of jeff
> Sent: Tuesday, July 11, 2017 1:56 PM
> To: cygwin@cygwin.com
> Subject: EXT: Re: problem with gnupg2 not prompting for passphrase
>
> On 7/11/2017 10:51 AM, Brian Inglis wrote:
> >
On 7/11/2017 10:51 AM, Brian Inglis wrote:
> On 2017-07-10 23:07, Thomas Wolff wrote:
>> Am 11.07.2017 um 00:38 schrieb jeff:
>>> On 7/10/2017 1:21 PM, Achim Gratz wrote:
jeff writes:
> jeff_xeon:/cygdrive/u:503: gpg2 --output fred.good --decrypt fred.gpg
> gpg: encrypted with 4096-bit
On 2017-07-10 23:07, Thomas Wolff wrote:
> Am 11.07.2017 um 00:38 schrieb jeff:
>> On 7/10/2017 1:21 PM, Achim Gratz wrote:
>>> jeff writes:
jeff_xeon:/cygdrive/u:503: gpg2 --output fred.good --decrypt fred.gpg
gpg: encrypted with 4096-bit RSA key, ID A3791E7DD935A424, created
2013-0
On 7/11/2017 8:34 AM, Eliot Moss wrote:
On 7/10/2017 10:33 PM, Brian Inglis wrote:
On 2017-07-10 20:00, Eliot Moss wrote:
Backup processes should run with SeBackupPrivilege.
Reasonable. CrashPlan runs using SYSTEM access. I
will try adding SYSTEM to the BackupOperators group,
which presumab
On 7/10/2017 2:00 PM, Kaz Kylheku wrote:
> On 10.07.2017 10:40, Nellis, Kenneth wrote:
>> For my personal use, I use gcc to generate binaries, but occasionally
>> I need
>> to make a binary available to someone who doesn't use Cygwin. For that
>> I use
>> Cygwin's x86_64-w64-mingw32-gcc.
>>
>> Afte
On 7/10/2017 1:40 PM, Nellis, Kenneth wrote:
> For my personal use, I use gcc to generate binaries, but occasionally I need
> to make a binary available to someone who doesn't use Cygwin. For that I use
> Cygwin's x86_64-w64-mingw32-gcc.
>
> After the fact, I would like to know whether the binar
From: Hans-Bernhard Bröker
> That's a bit too rough. Something like
>
> cygcheck ./foo.exe | grep cygwin1.dll
> orldd ./foo.exe | grep cygwin1.dll
>
> would be more precise.
Appreciate the improved tests. Thanx!
> > One of my wishes for Cygwin is for the "file" command to make the
>
On 7/10/2017 10:33 PM, Brian Inglis wrote:
On 2017-07-10 20:00, Eliot Moss wrote:
Backup processes should run with SeBackupPrivilege.
Reasonable. CrashPlan runs using SYSTEM access. I
will try adding SYSTEM to the BackupOperators group,
which presumably has SeBackupPrivilege (and
SeRestorePr
21 matches
Mail list logo
