X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <31b7d2790710091359m5f4941bue28217d51cb48504@mail.gmail.com> Date: Tue, 9 Oct 2007 15:59:25 -0500 From: "DePriest, Jason R." To: cygwin AT cygwin DOT com Subject: Re: Links and O/S shell In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 10/9/07, Joel Rubin wrote: > I ran links from cmd, started to download a file in the background and > ran an O/S shell. Later, when I could see that the download was long > finished, I exited the O/S shell and, instead of returning to links, > the whole console box disappeared, leaving the ghost of links and the > cmd session which had started it running without any visible console. > I cannot recreate this. If, from within links, I request an 'OS shell' and later exit that shell, links is still running and I can just 'q' to exit it. I tried this from a Windows cmd.exe prompt using \cygwin\bin\links.exe and also from within an rxvt (no X) bash prompt. Both times, links spawned a cmd.exe prompt that worked as expected when I exited it. You could provide the information requested by > Problem reports: http://cygwin.com/problems.html -Jason -- 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/