public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: 6kbnowe02@sneakemail.com Subject: Re: Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why? Date: Thu, 03 Dec 2015 13:47:00 -0000 [thread overview] Message-ID: <566047F1.30805@dronecode.org.uk> (raw) In-Reply-To: <loom.20151202T011129-634@post.gmane.org> On 02/12/2015 00:16, John J Ottusch wrote: > Makes sense that it could be run.exe behavior. > > However, the version of run.exe from [2] (which is 220K in size vs. 68K > for the original version ?!?) does not seem to do anything. Running it > from a CMD window with urxvtermX.bat as the argument does not produce an > error message, a urxvt term, nothing. It's larger because it doesn't have debug information stripped. > BTW, I made an effort to give both versions of run.exe (I renamed the > new one runX.exe) the same ownership and permissions, but to no avail. > > Am I missing something essential? Just chmod +x should be sufficient. I've probably done something wrong, although I have re-tested this run.exe and it seems to work for me. Perhaps you could try 'strace ./run XWin', that might shed some light on what's going wrong? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
next prev parent reply other threads:[~2015-12-03 13:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-02 0:17 John J Ottusch 2015-12-03 13:47 ` Jon Turney [this message] -- strict thread matches above, loose matches on Subject: below -- 2015-12-10 0:03 John J Ottusch 2015-11-29 6:00 John J Ottusch 2015-11-30 15:44 ` Jon Turney
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=566047F1.30805@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=6kbnowe02@sneakemail.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: linkBe 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).