X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
X-Scan-Server: spamd03.cc.umr.edu
X-Scan-Recipient: outbound@msx.umr.edu
X-Spam-Virus: No
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: problem with xemacs 21.4.20
Date: Sun, 9 Sep 2007 23:13:22 -0500
Message-ID: <E00BDCF423F2D740B41DE19E7ACC40B5015EE59F@UMR-CMAIL3.umr.edu>
In-Reply-To: <E00BDCF423F2D740B41DE19E7ACC40B5015EE59D@UMR-CMAIL3.umr.edu>
References: <E00BDCF423F2D740B41DE19E7ACC40B5015EE59D@UMR-CMAIL3.umr.edu>
From: "Weigert, Thomas" <weigert@umr.edu>
To: "Weigert, Thomas" <weigert@umr.edu>, <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l8A4DkHr005566

Sorry, I found a workaround to my question. There is an option --hide to
cygstart that avoids that shell window.

So I created a shortcut that invokes xemacs via cygstart --hide, as in
C:\cygwin\bin\bash.exe --login -c 'cygstart --hide /c/cygwin/bin/xemacs'

Cheers, Th.

> -----Original Message-----
> From: Weigert, Thomas
> Sent: Sunday, September 09, 2007 10:44 PM
> To: 'cygwin@cygwin.com'
> Cc: Weigert, Thomas
> Subject: problem with xemacs 21.4.20
> 
> Up to now I had been using xemacs-21.4.13. That release had a big
> advantage over the current release:
> 
> When starting xemacs by double clicking the executable it used to
start up
> without leaving a shell window behind. But 21.4.20 opens up a shell
window
> and then starts up xemacs from there, leaving the shell window open,
> cluttering the desktop and the taskbar. However, this shell window is
not
> usable, as xemacs is not running in the background there and cannot be
> sent to the background. This also happens when using cygstart to fire
up
> xemacs.
> 
> Any suggestions of not having that window around would be greatly
> appreciated.
> 
> Thanks, Th.

--
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/


