On 7/15/2010 8:17 PM, Monte Cabet wrote:
I always hear some applications thrown out there that you should have to
build software from source like gcc and vim, but is there a more
complete list of what is required? I built up somewhat of a list for
myself to track what I've installed, but there se
The cygwin package of nasm has been updated to version 2.08.02. This
is the latest stable upstream version available from http://nasm.us/
The Netwide Assembler, NASM, is an 80x86 and x86-64 assembler designed
for portability and modularity.
In addition to the upstream changes noted below,
I always hear some applications thrown out there that you should have to
build software from source like gcc and vim, but is there a more
complete list of what is required? I built up somewhat of a list for
myself to track what I've installed, but there seems to be a lot of
missing points. Some
>> I am using
>>
>> echo $'\e]4;3;255, 0, 0\a' # color3 for devices
>
> Have you tried using "echo -n"?
Don't get in the habit. Use printf(1) instead:
printf %s %'\e]4;3;255, 0, 0\a'
echo(1) is non-portable when it comes to options, and 'echo -n' will not
behave the same on all shells; you
On 7/15/2010 3:12 PM, DePriest, Jason R. wrote:
On Thu, Jul 15, 2010 at 10:44 AM, Ernest Mueller<> wrote:
Michael, did you ever find a fix for this? I had to give up on cygwin on
the Amazon 64-bit and instead cobbled together freesshd and random
freewares.
Larry or others - what's the "right
On Thu, Jul 15, 2010 at 10:44 AM, Ernest Mueller <> wrote:
> Michael, did you ever find a fix for this? I had to give up on cygwin on
> the Amazon 64-bit and instead cobbled together freesshd and random
> freewares.
>
> Larry or others - what's the "right way" to report this as a bug? I think
> w
On 7/15/2010 11:44 AM, Ernest Mueller wrote:
Michael, did you ever find a fix for this? I had to give up on cygwin on
the Amazon 64-bit and instead cobbled together freesshd and random
freewares.
Larry or others - what's the "right way" to report this as a bug? I think
working on newer 64-bit
On Thu, Jul 15, 2010 at 1:31 PM, Lukas Haase <> wrote:
> Hi,
>
> Is there any (working) way to change privileges in cygwin?
>
> Regards,
> Luke
>
>
Try this: http://www.cygwin.com/faq/faq.using.html#faq.using.su
It tells you to use s...@localhost but has a link to some mailing list
archives that
Hi,
Is there any (working) way to change privileges in cygwin?
Regards,
Luke
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simpl
On 7/15/2010 11:42 AM, Dave Korn wrote:
I guess the first thing I should do is get out a
more vanilla-flavoured 4.5.0 release.)
Err... 4.5.1? Does the ABI breakage between 4.5.0 and 4.5.1/4.6.0
mentioned wrt x86_64-mingw affect i386, or cygwin?
--
Chuck
--
Problem reports: http://cy
Michael, did you ever find a fix for this? I had to give up on cygwin on
the Amazon 64-bit and instead cobbled together freesshd and random
freewares.
Larry or others - what's the "right way" to report this as a bug? I think
working on newer 64-bit OSes is pretty important... And it should be
t
Is there a way of changing the default text colours
used by mintty for directories, links, executables, etc?
>> From man mintty: use
echo $'\e]4;3;255,255,0\a'
and similarly, in a script.
I am using
echo $'\e]4;3;255, 0, 0\a' # color3 for devices
echo $'\e]4;6;139, 69, 19\a' # color
On 7/15/2010 10:18 AM, Fergus wrote:
>>> Is there a way of changing the default text colours
>>> used by mintty for directories, links, executables, etc?
>
>> From man mintty: use
>> echo $'\e]4;3;255,255,0\a'
>> and similarly, in a script.
>
> I am using
>
> echo $'\e]4;3;255, 0, 0\a' # co
On 09/07/2010 17:51, Christopher Faylor wrote:
> Someone may be looking into this but if this is adding complication to the
> signal handler it is going to take some real convincing that it should go
> into the DLL.
:) Fortunately, it doesn't have to do that. All the magic takes place in
libgc
>> Is there a way of changing the default text colours
>> used by mintty for directories, links, executables, etc?
> From man mintty: use
> echo $'\e]4;3;255,255,0\a'
> and similarly, in a script.
I am using
echo $'\e]4;3;255, 0, 0\a' # color3 for devices
echo $'\e]4;6;139, 69, 19\a' # col
On 13/07/2010 19:48, Nellis, Kenneth wrote:
>> From: DePriest, Jason R.
>> On Tue, Jul 13, 2010 at 9:49 AM, Tekerman Romanov <> wrote:
>>> Hi, I'm not able to find e-mail where I could ask
>>> "Sourcemaster is also the place to send requests to be added to this
>> list."
>>> Who is this sourcemaste
On Mon, Jul 12, 2010 at 11:36:04AM -0500, James Cotton wrote:
>Hello, I've been trying to get the FreeRTOS Posix simulator to run on
>Cygwin and have run into a few bugs in the signal handling/pthread
>libraries and have isolated test cases
>
>Essentially sending a SIGUSR1 to a pthread causes a seg
On Thu, Jul 15, 2010 at 09:54:21AM +0200, Matthias Andree wrote:
>Am 15.07.2010, 07:49 Uhr, schrieb Christopher Faylor:
>
>> On Thu, Jul 15, 2010 at 01:44:19AM +0100, Cliff Hones wrote:
>>> When select() is used to test for input availability on the standard
>>> cygwin console in normal (cooked) mo
On Thu, Jul 15, 2010 at 01:45:43PM +0100, Cliff Hones wrote:
>Cliff Hones wrote:
>> I must look at the console source...
>
>And now I have, and I see that fhandler_console does its own line
>editing, so is perfectly aware of the input line state. So blocking as
>soon as any key is typed seems a sh
On Thu, Jul 15, 2010 at 12:25:09PM +0100, Andy Koppe wrote:
>On 15 July 2010 09:19, Corinna Vinschen wrote:
>>> Furthermore, there is a very long-standing issue with Cygwin pty devices:
>>> while Cygwin programs report true from isatty() when called on a Cygwin PTY,
>>> MSVCRT applications do *not*
On 7/8/2010 9:08 AM, Jacob Jacobson wrote:
I recently updated my Cygwin installation and now I get,
[~$:501] cd /c/home/bash: exclude: unbound variable
[~$:501]
when I hit TAB.
I have seen Eric's announcement & followed that.
>> A new release of bash-completion, 1.2-1, is now available for
On 15 July 2010 12:57, Cliff Hones wrote:
>> On Thu, Jul 15, 2010 at 01:44:19AM +0100, Cliff Hones wrote:
>>> When select() is used to test for input availability on the standard
>>> cygwin console in normal (cooked) mode, it indicates input is available
>>> as soon as any key is pressed. However,
Cliff Hones wrote:
> I must look at the console source...
And now I have, and I see that fhandler_console does its own
line editing, so is perfectly aware of the input line state.
So blocking as soon as any key is typed seems a shortcoming
of cygwin, not windows?
I see there may be a difficulty w
2010/7/13 Linda Walsh :
...
> Windows 7 Ultimate Ver 6.1 Build 7600
> Running under WOW64 on AMD64
> Path: .
> C:\sbin
> C:\usr\sbin
> C:\usr\local\sbin
> C:\Prog64\strawberry-perl\c\bin
> C:\prog64\strawberry-perl\perl\site\bin
> C:\prog64\strawberry-per
Christopher Faylor wrote:
> On Thu, Jul 15, 2010 at 01:44:19AM +0100, Cliff Hones wrote:
>> When select() is used to test for input availability on the standard
>> cygwin console in normal (cooked) mode, it indicates input is available
>> as soon as any key is pressed. However, a call to read(0,..
On 15 July 2010 09:19, Corinna Vinschen wrote:
>> Furthermore, there is a very long-standing issue with Cygwin pty devices:
>> while Cygwin programs report true from isatty() when called on a Cygwin PTY,
>> MSVCRT applications do *not*.
>
> Right.
>
>> [...]
>> However, due to the way the CRT works
On 7/15/10 1:19 AM, Corinna Vinschen wrote:
> Thanks for the hint. You *did* test that, did you?
Yep. I've been using this setup for a few days now and everything works.
[...]
> That sounds like an interesting idea. I'll play around with it as soon
> as I have a bit of spare time again. Unless
On Jul 14 15:38, Daniel Colascione wrote:
> This is from sigproc.cc:
>
> /* It appears that when running under WOW64 on Vista 64, the first DWORD
> value in the datastructure lpReserved2 is pointing to (msv_count in
> Cygwin), has to reflect the size of that datastructure as used in th
Am 15.07.2010, 07:49 Uhr, schrieb Christopher Faylor:
On Thu, Jul 15, 2010 at 01:44:19AM +0100, Cliff Hones wrote:
When select() is used to test for input availability on the standard
cygwin console in normal (cooked) mode, it indicates input is available
as soon as any key is pressed. However
29 matches
Mail list logo
