X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_RX X-Spam-Check-By: sourceware.org Received-SPF: pass (google.com: domain of d DOT sastre DOT medina AT gmail DOT com designates 10.180.104.65 as permitted sender) client-ip=10.180.104.65; Authentication-Results: mr.google.com; spf=pass (google.com: domain of d DOT sastre DOT medina AT gmail DOT com designates 10.180.104.65 as permitted sender) smtp.mail=d DOT sastre DOT medina AT gmail DOT com; dkim=pass header.i=d DOT sastre DOT medina AT gmail DOT com Date: Tue, 6 Mar 2012 20:46:22 +0100 From: David Sastre Medina To: cygwin AT cygwin DOT com Subject: Re: mintty scroll to bottom Message-ID: <20120306194622.GA6006@jethro.local.lan> References:

<20120302084105 DOT GA14404 AT calimero DOT vinschen DOT de> <20120304115048 DOT GB18852 AT calimero DOT vinschen DOT de> <4F54F70E DOT 7080504 AT cs DOT utoronto DOT ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 05, 2012 at 07:57:29PM +0100, Lemke, Michael SZ/HZA-ZSW wrote: > On March 05, 2012 6:26 PM Ryan Johnson wrote: > >On 05/03/2012 5:05 AM, Lemke, Michael SZ/HZA-ZSW wrote: > >> On March 04, 2012 12:51 PM, Corinna Vinschen wrote: > >>> On Mar 2 20:20, Andy Koppe wrote: > >>>> On 2 March 2012 08:41, Corinna Vinschen wrote: > >>>>> On Mar 1 20:43, Andy Koppe wrote: > >>>>>> On 29 February 2012 12:46, Lemke, Michael SZ/HZA-ZSW wrote: > >>>>>>> What is the mintty equivalent to rxvt/xterm's > >>>>>>> > >>>>>>> -si|+si > >>>>>>> Turn on/off scroll-to-bottom on TTY output inhibit; > >>>>>>> resource scrollTtyOutput has opposite effect. > >>>>>> There's no such option. Shift+End will get you back to the current > >>>>>> output after looking at something in the scrollback, as will any > >>>>>> keypress that sends something to the terminal. > >>>>> Any chance to implement this? Automatic scroll-to-bottom is a usef= ul > >>>>> feature, IMHO. > >>>> I disagree. The point of being able to scroll back to earlier output > >>>> is to read and perhaps copy something. When doing that, having the > >>>> scrollback jump back to the bottom without the user asking for it is > >>>> rather unhelpful. The Windows console does this, and I always found = it > >>>> really frustrating. > >>> THat's why this is an option in xterm. Every use has another idea how > >>> the terminal should behave in this regard, I guess. > >> I'd also appreciate very much implementing that option. mintty is > >> promoted here as a replacement for rxvt but obviously lacks a function= ality > >> I've come to depend on. My use case is a terminal window in which I d= on't > >> do much but where a lot of background jobs regularly produce output. > >> A quick glance at the window tells me the current status of those jobs. > >> Not with mintty anymore. Same with the classic use case tail -f logfi= le. > >What you describe above sounds more like mintty allowing a visible "end= =20 > >of output" to scroll off the bottom without following it, a behavior=20 > >I've never observed and which would arguably be a bug. >=20 > That's not what I said. >=20 > > > >When I fire up something that produces copious output (gcc bootstrap,=20 > >compile emacs, etc.) mintty scrolls to track end-of-output unless I=20 > >purposefully scroll upward=20 >=20 > Right, same here. Turning on scroll-to-bottom would change that. It > scrolls to bottom immediately. >=20 > >(in which case I'd prefer it to stay put long=20 > >enough to read/copy the text rather than immediately jumping me back to= =20 > >end-of-output).=20 >=20 > That depends on what I am doing in such a terminal. I might have a > tail -f /var/log/messages & in that session on a system with low=20 > syslog activity. I want to be notified immediately if there is=20 > output and don't mind being interrupted. >=20 > >Once the scrollbar is set back to bottom, it again=20 > >tracks end-of-output.=20 >=20 > Correct. And that's the step I want to skip. The si-option does > exactly that. >=20 > > > >Am I missing something? Or do your background jobs just produce output= =20 > >really infrequently compared to 'make all'? >=20 > In this case yes, but I also like scroll-to-bottom if there's more output. >=20 > >The latter is the only way I=20 > >can see "reading stuff from the past" and "scroll-to-bottom" coexisting= =20 > >peacefully=20 >=20 > They usually won't. That=E2=80=99s why this should be an option and not = the=20 > default. Most of the behaviour discussed in this thread can be achieved or emulated using screen (notification on activity, scroll and output logging at will, etc). Might be useful to take a look at it. --=20 Huella de clave primaria: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56 --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iF4EAREIAAYFAk9WaY4ACgkQ95urBFKZ7FZ8NwD+NPi2hMBKlL4KbnkZt0GyhdiX dG5UjEIKzpV7D3qLTAgA/Ai+725dfEHmJ11X9KhF70L69attBJ75ZVBJ9jIjTI3J =Gfyc -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V--