public inbox for email@example.com help / color / mirror / Atom feed
From: Jon Turney <firstname.lastname@example.org> To: email@example.com Cc: firstname.lastname@example.org Subject: Re: Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why? Date: Mon, 30 Nov 2015 15:44:00 -0000 [thread overview] Message-ID: <565C6EE5.email@example.com> (raw) In-Reply-To: <loom.20151129T035407firstname.lastname@example.org> On 29/11/2015 02:56, John J Ottusch wrote: > I use CYGWIN a lot with 64-bit Windows 7 and have been transitioning > from 32-bit CYGWIN to 64-bit CYGWIN primarily in hopes of avoiding > repeated STATUS_ACCESS_VIOLATION errors. > > If I could set up 64-bit CYGWIN (= C64) to behave exactly the same way > as my 32-bit CYGWIN (= C32) set up I would, but the applications don't > match up exactly and they don't behave exactly the same way. > > One difference I notice is that opening a urxvt in C64 creates a > separate button associated with the Cygwin/X server process in the > taskbar, whereas opening an rxvt in C32 does not. (rxvt is not available > as a C64 application, but I would expect urxvt to operate similarly). In Yes, please use rxvt-unicode (urxvt). rxvt has been dead upstream for a decade. > both cases an icon for the Cygwin/X server process shows up in the > notification area. > > Both are started from a Windows shortcut: > > C32 target: > C:\win32app\cygwin\bin\run.exe C:\win32app\cygwin\rxvtermX.bat > > C64 target: > C:\win64app\cygwin\bin\run.exe C:\win64app\cygwin\urxvtermX.bat > > The batch files that run are similar. Both start 'XWin' if it is not > already running, then run 'rxvt/urxvt'. > [...] > I prefer NOT to have the taskbar button for the Cygwin/X server process > show up. Having an icon show up in the notification area is cleaner. > > Why are they behaving differently? Is there a way to make the urxvt > version (C64) behave like the rxvt version (C32)? I think this is not a problem with the X server, but with the Cygwin run utility, which is supposed to run the .bat file with a hidden console. See  a previous discussion of this problem. I've built an x86_64 run.exe with that patch applied and uploaded it at . Perhaps you could try that and see if it improves things.  http://cygwin.com/ml/cygwin-xfree/2012-08/msg00000.html  ftp://cygwin.com/pub/cygwinx/x86_64/run.exe -- 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-11-30 15:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-11-29 6:00 John J Ottusch 2015-11-30 15:44 ` Jon Turney [this message] 2015-12-02 0:17 John J Ottusch 2015-12-03 13:47 ` Jon Turney 2015-12-10 0:03 John J Ottusch
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=565C6EE5.email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /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).