Hi,
(This is the same reply I sent when Robert emailed cygwin-xfree rather
than cygwin.)
On Tue, Jul 21, 2015 at 11:13 PM, Robert McBroom wrote:
>
> Having problems with the X interface in Windows 10 (currently build 10240).
> /bin/startxwin fails with the symptoms in the attached file xwin.txt.
Having problems with the X interface in Windows 10 (currently build
10240). /bin/startxwin fails with the symptoms in the attached file
xwin.txt. The output from cygcheck -cv is also attached. What am I missing?
$ startxwin
Could not load crashreporter dll
Welcome to the XWin X Server
Vendor
On Tue, Jul 21, 2015 at 11:29:33PM +0200, Marco Atzeri wrote:
> On 7/20/2015 1:27 PM, Adam Dinwoodie wrote:
> >On Mon, Jul 20, 2015 at 12:03:34PM +0200, Marco Atzeri wrote:
> >>On 7/20/2015 11:48 AM, Corinna Vinschen wrote:
> >>>Here's the problem from https://cygwin.com/cygwin-pkg-maint:
> >>>
> >
>> You are the expert on mintty now ... I only observed a "pattern":
> let's say maintainer... expert on terminal issues maybe, but not on
> Windows API and specifics of POSIX process control...
Language, language, Henri!
Hi Thomas,
1. Re. "You are the expert on mintty now ..."
First of all, my
On 7/20/2015 1:27 PM, Adam Dinwoodie wrote:
On Mon, Jul 20, 2015 at 12:03:34PM +0200, Marco Atzeri wrote:
On 7/20/2015 11:48 AM, Corinna Vinschen wrote:
Here's the problem from https://cygwin.com/cygwin-pkg-maint:
cvs ORPHANED (Charles Wilson)
Anybody will
Greetings, Jarek!
>>> So why are they not needed as your comment doesn't really explain that
>> Read 1.7.35 changelog.
>> In short, username resolution was completely reworked, thanks to Corinna, and
>> Cygwin now directly address domain controllers for it.
> OK so it addresses DCs to check some s
On 20/07/15 20:14, Mouse wrote:
The question does not specify a jurisdiction; that XWin is not a
relevant trademark in the USA does not mean it's not elsewhere. (While
I'm not aware of any where it is, I haven't gone looking.
I did a quick search, and turned up one trademark of Xwin [1] (note
On 21.07.2015 10:45, Houder wrote:
The trick is to make mintty NOT interact with a cons.
Not sure in what way mintty would "interact" with the console here.
Hi Thomas,
You are the expert on mintty now ... I only observed a "pattern":
let's say maintainer... expert on terminal issues maybe, but
On Jul 21 11:12, Ian Lambert wrote:
> On July 20, 2015 11:29:49 AM EDT, Corinna Vinschen
> wrote:
> >
> >Does your stuff still work as with 2.1.0? No regression?
>
>
> I have a simple bash script to open 3 xterms. Now $ xterm gives
>
> xterm: Xt error: Can't open display: local host:0.0
On July 21, 2015 11:12:08 AM EDT, Ian Lambert wrote:
>On July 20, 2015 11:29:49 AM EDT, Corinna Vinschen
> wrote:
>>
>>Does your stuff still work as with 2.1.0? No regression?
>
>
>I have a simple bash script to open 3 xterms. Now $ xterm gives
>
>xterm: Xt error: Can't open display: local host:0
On July 20, 2015 11:29:49 AM EDT, Corinna Vinschen
wrote:
>
>Does your stuff still work as with 2.1.0? No regression?
I have a simple bash script to open 3 xterms. Now $ xterm gives
xterm: Xt error: Can't open display: local host:0.0
So, now I have to use the toolbar 4 times, versus 1 recent
> This is the correct place to report such issues.
Good; always nice to get confirmation I guessed right. :-)
>> In FAQ item 1.9, [...]
>> Surely those list addresses shouldn't _all_ be the same...?
> This piece of text obviously doesn't make much sense after the
> search-and-replace which happen
On 2015-07-21 02:25, Andrey Repin wrote:
Greetings, Jarek!
Hey Andrey.
So why are they not needed as your comment doesn't really explain that
Read 1.7.35 changelog.
In short, username resolution was completely reworked, thanks to Corinna, and
Cygwin now directly address domain controllers fo
On 20/07/2015 20:14, Mouse wrote:
I happened to be looking at
http://x.cygwin.com/docs/faq/cygwin-x-faq.html and I noticed some
oddities which might call for fixing. This is the only place I could
find for reporting such issues, though of course it's entirely possible
This is the correct place
On 7/18/2015 11:38 PM, JonY wrote:
On 7/18/2015 03:14, Ken Brown wrote:
JonY,
Could we get an update of w32api-headers? There's a bug in shlobj.h, as
illustrated by the following:
$ cat test.c
#include
$ gcc -c test.c
In file included from test.c:1:0:
/usr/include/w32api/shlobj.h:37:3: erro
>> The trick is to make mintty NOT interact with a cons.
> Not sure in what way mintty would "interact" with the console here.
Hi Thomas,
You are the expert on mintty now ... I only observed a "pattern":
- when 'ps ax' shows that mintty is "connected" to a 'cons', SIGINT is ignored
- when 'ps
16 matches
Mail list logo
