X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: rvxt-20050409-1 console problem Date: Mon, 15 May 2006 12:40:45 -0400 Message-ID: From: "Harig, Mark" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k4FGgPl7014455 Shouldn't the console-hiding code be unnecessary? Here is a simple approach that I have been using (and have written to this list previously) which makes it possible to start rxvt without resorting to starting a console first: 1. Using MS Windows Explorer, locate the 'rxvt' binary in your Cygwin directory tree, for example, at c:\cygwin\bin. 2. Right-click on the 'rxvt.exe' icon and select 'Create Shortcut' from the menu. 3. Right-click on the 'Shortcut to rxvt.exe' icon and select 'Properties' from the menu. 4. In the 'Target' field, type the options that you want to specify for 'rxvt' during startup. For example, C:\cygwin\bin\rxvt.exe -e /bin/bash --login -i tells rxvt to run 'bash' as the shell, and tells bash to run as a login shell. 5. If desired, drag&drop the shortcut icon to your taskbar. Click on the icon to start 'rxvt' without using a console. Am I missing something, or is there still another reason to include the console-hiding code? -----Original Message----- From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Igor Peshansky Sent: Monday, May 15, 2006 10:47 AM To: cygwin AT cygwin DOT com Subject: rvxt-20050409-1 console problem Hi, After installing rxvt-20050409-1, starting rxvt from a console bash hides that console. To reproduce: start a console bash, type "rxvt" or "rxvt &" (either way), observe that the bash window goes away (the process is still running, though). I don't think the cygcheck output is relevant, since this looks like an rxvt problem (caused by the new code to hide the console). Chuck, if you can't reproduce this, please let me know and I'll provide more details. Igor -- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/