public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jay Goldman <JayGoldman@crd.com>
To: "cygwin-xfree@cygwin.com" <cygwin-xfree@cygwin.com>
Subject: RE: X Server no longer launches urxvtc-X
Date: Fri, 20 Aug 2010 17:56:00 -0000	[thread overview]
Message-ID: <8483108B583CFC4FAEFEE85B95CF015C2EECAB2F84@MAIL4.crd.com> (raw)
In-Reply-To: <4C6E9714.40409@cwilson.fastmail.fm>

Chuck - thanks for the reply. This is what I had concluded but it's nice to get some confirmation.
For the next few days I can live with 'manually' starting urxvtc-X via individual batch files.

Thanks,
Jay

-----Original Message-----
From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Charles Wilson
Sent: Friday, August 20, 2010 10:54 AM
To: cygwin-xfree@cygwin.com
Subject: Re: X Server no longer launches urxvtc-X

On 8/20/2010 10:48 AM, Jay Goldman wrote:
> I have the following menu items in my .XWinrc:
>         Black EXEC  "/bin/urxvtc-X -fg green -bg black   -cr dodgerblue -g 80x40 -e /bin/bash -l -I"
>         dodger EXEC  "urxvtc-X -fg white -bg dodgerblue   -cr blue -g 80x42 -e /bin/bash -l -I"
>
> Which have been working for months .
>
> Today I upgraded my cygwin install and all my menu items like the above no longer work.
> (as noted above I've tried both simply urxvtc-X and /bin/urxvtc-X
> If, however, I open up a command window using rxvt and then enter the above
> Line (by copy and paste) it works fine.

My first guess was that the urxvt daemon (urxvtd-X) was not running, so 
the client failed. But if you can launch the client using some 
incantation, then that means the daemon is running.

>
> Note, menu items like:
>                  Xterm exec "xterm"
> Work correctly,
> While menu items such as:
>                  Notepad exec "notepad"
> Do not.

Ah. Here's the clue: launching a native win32 program fails.  I bet this 
is related to the change in cygwin-1.7.6 where the cygwin "current 
working directory" and the win32 CWD are no longer automatically kept in 
sync (there are good reasons for this new behavior).

This change has caused a number of problems, and it is not yet clear how 
they will be resolved.  Stay tuned to the main cygwin list -- and 
meanwhile, revert to cygwin-1.7.5.

--
Chuck

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2010-08-20 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 14:54 Jay Goldman
2010-08-20 15:05 ` Charles Wilson
2010-08-20 17:56   ` Jay Goldman [this message]
2010-08-20 18:14   ` Corinna Vinschen
2010-08-20 19:07     ` Jay Goldman
     [not found]       ` <20100820190626.GH11340@calimero.vinschen.de>
2010-08-23 16:03         ` Jay Goldman
     [not found] <AANLkTindvuHq21A1sy3a=Ex14970xhFwHXoe_4rLXMui@mail.gmail.com>
2010-08-26 13:57 ` Jay Goldman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8483108B583CFC4FAEFEE85B95CF015C2EECAB2F84@MAIL4.crd.com \
    --to=jaygoldman@crd.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).