Ok. I wasn't sure as the behavior changed. It worked in 1.9.5 and then
stopped working when I moved to 2.5.x. I'm not sure if it matters to you, but
doing some bisecting it looks like the behavior changed between 2.2.0 and 2.3.0:
-
[/cygdrive/d/projects]
$ git --versio
On Dec 1 19:27, nu774 wrote:
> After upgrading to Windows 10 TH2 (ver 1511, build 10586), any attempt
> to launch a cygwin64 process from 32bit native app (for example,
> C:\windows\syswow64\cmd.exe) *always* results in a fork error.
>
> To be precise, I can execute 64bit bash.exe from 32bit cmd.
On Sun, Nov 22, 2015 at 11:30:27PM +, boulderfans wrote:
> [/cygdrive/d/projects]
> $ git --git-dir=d:/projects/git-git/.git config alias.foo ls-files
> error: Unable to open tempfile:
> /cygdrive/d/projects/d:/projects/git-git/.git/config.lock
> error: could not lock config file d:/projects/g
On 12/3/2015 12:56 PM, René Berber wrote:
> But I don't know what to make of this: Version 10.0 (build 10240),
> perhaps the "1511" is the last 4 digits.
Never-mind, Windows update just installed "version 1511, 10586".
--
René Berber
--
Problem reports: http://cygwin.com/problems.html
Am 01.12.2015 um 15:01 schrieb Corinna Vinschen:
...
If that only happens w/ 64 bit Cygwin started from a 32 bit parent, then
there's some foul-up in the WOW64 layer in terms of starting 64 bit
processes, perhaps. Sigh, it's a rather unexpected change after it
worked fine for so long :(
For ref
On 12/3/2015 2:13 AM, David Macek wrote:
> I've always used the trusty `winver` for version info.
Thanks.
But I don't know what to make of this: Version 10.0 (build 10240),
perhaps the "1511" is the last 4 digits.
--
René Berber
--
Problem reports: http://cygwin.com/problems.html
FAQ:
This seems to be a consistent bug. How do I file it?
> Am Sonntag, 22. November 2015 20:17 CET, Thomas Wolff schrieb:
>
> > > I found a consistent bug that happens every time:
> > > ...
> > > - Press Ctrl+S to stop the output in the terminal
> > >
> > > Bug #1: It's not possible to unfreeze the
On 12/3/2015 4:35 AM, Matthew Eichler wrote:
I'm getting a core dump from the latest Emacs 24.5.2 when I run the
'list-packages function (package manager for sites like ELPA and MELPA
http://ergoemacs.org/emacs/emacs_package_system.html)
It works fine for me. Please give a complete recipe for
Hello.
I try find 'float:left;display: block;height: 24px;line-height:
1.2em;position: relative;text-align: center;white-space: nowrap;width:
80px;' in path 'c:\Sources\inside\Модули интерфейса\Активные продажи\'
grep -rn 'float:left;display: block;height: 24px;line-height:
1.2em;position: relati
On Dec 3 00:00, Corinna Vinschen wrote:
> On Dec 2 16:43, René Berber wrote:
> > On 12/2/2015 4:15 PM, Corinna Vinschen wrote:
> >
> > > Along these lines, is anybody here still running a 64 bit Windows 10
> > > which has *NOT* been updated to 1511? If so, I just need the output
> > > of a call
I'm getting a core dump from the latest Emacs 24.5.2 when I run the
'list-packages function (package manager for sites like ELPA and MELPA
http://ergoemacs.org/emacs/emacs_package_system.html)
I think the offending code is here:
/usr/share/emacs/24.5/lisp/emacs-lisp/package.el.gz
/usr/share/emacs/
On Thu, Nov 26, 2015 at 09:18:52AM -0500, Eliot Moss wrote:
> On 11/26/2015 8:24 AM, Lester Anderson wrote:
> >Hello,
> >
> >I can use a script like:
> >
> >#!/bin/bash
> >x=3.7
> ># pass variable x to awk via -v (var=value)
> >awk -v x=$x 'BEGIN { printf "%3.0f\n", x }'
> >#
> >
> >which returns t
On 3. 12. 2015 0:00, Corinna Vinschen wrote:
> On Dec 2 16:43, René Berber wrote:
>> I don't know were you can see the specific Windows version, but AFAIK it
>> hasn't been updated recently (the System Info only shows "Windows 10
>> Pro", 64-bit).
>
> That's oh so funny: The good old system info
13 matches
Mail list logo
