From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 80752 invoked by alias); 30 Nov 2015 15:44:55 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Received: (qmail 80743 invoked by uid 89); 30 Nov 2015 15:44:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_50,EXECUTABLE_URI,KAM_EXEURI,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: out4-smtp.messagingengine.com Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 30 Nov 2015 15:44:50 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id B7A0C206DC for ; Mon, 30 Nov 2015 10:44:47 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 30 Nov 2015 10:44:47 -0500 Received: from [192.168.1.102] (host86-141-129-50.range86-141.btcentralplus.com [86.141.129.50]) by mail.messagingengine.com (Postfix) with ESMTPA id 273E3C016F0; Mon, 30 Nov 2015 10:44:47 -0500 (EST) Subject: Re: Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why? To: cygwin-xfree@cygwin.com References: From: Jon Turney Reply-To: cygwin-xfree@cygwin.com Cc: ncokwqc02@sneakemail.com Message-ID: <565C6EE5.7070103@dronecode.org.uk> Date: Mon, 30 Nov 2015 15:44:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2015-11/txt/msg00002.txt.bz2 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 [1] a previous discussion of this problem. I've built an x86_64 run.exe with that patch applied and uploaded it at [2]. Perhaps you could try that and see if it improves things. [1] http://cygwin.com/ml/cygwin-xfree/2012-08/msg00000.html [2] 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/