From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 44691 invoked by alias); 29 Nov 2015 06:00:21 -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 37574 invoked by uid 89); 29 Nov 2015 06:00:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.7 required=5.0 tests=BAYES_50,DATE_IN_PAST_03_06,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: plane.gmane.org Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Sun, 29 Nov 2015 06:00:12 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1a2v1n-0003ZS-Ji for cygwin-xfree@cygwin.com; Sun, 29 Nov 2015 07:00:03 +0100 Received: from 66-214-91-193.dhcp.malb.ca.charter.com ([66.214.91.193]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 29 Nov 2015 07:00:03 +0100 Received: from ncokwqc02 by 66-214-91-193.dhcp.malb.ca.charter.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 29 Nov 2015 07:00:03 +0100 To: cygwin-xfree@cygwin.com From: John J Ottusch Subject: Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why? Date: Sun, 29 Nov 2015 06:00:00 -0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00001.txt.bz2 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 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'. Contents of 'rxvterm.bat' (C32): ================================= @echo off C: chdir C:\win32app\cygwin\bin ps -ef | grep /usr/bin/XWin > nul if ERRORLEVEL 1 ( start /DC:\win32app\cygwin\bin /B XWin -multiwindow ) set DISPLAY=localhost:0.0 rxvt -fn 10x20 -sl 10000 +sr -fg yellow -bg navyblue -title "RXVTerm w/X" -e /usr/bin/bash --login -i Contents of 'urxvterm.bat' (C64): ================================= @echo off C: chdir C:\win64app\cygwin\bin ps -ef | grep /usr/bin/XWin > nul if ERRORLEVEL 1 ( start /DC:\win64app\cygwin\bin /B XWin -multiwindow ) set DISPLAY=localhost:0.0 urxvt -fn 10x20 -sl 10000 +sr -fg yellow -bg navyblue -title "URXVTerm w/X" -e /usr/bin/bash --login -i 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)? John Ottusch -- 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/