-----BEGIN PGP SIGNED MESSAGE-----
On 07.09.2012 14:48, Srb, Michal wrote:
> Hi all,
> I can't find any resources about this even though I am sure this is
> dead simple and noobish.
> The "less" command doesn't clear its output after exiting. In fact,
> it leaves all read output in the buffer. In other environments,
> this is sometimes caused by the -X option, which I don't have set.
> I sense this might have to do with MinGW itself? I am using the Git
> Bash package, is this different in normal MinGW (i.e. can the shell
> remove stuff from the buffer?). Is there any way to fix this
> behaviour (so that after exiting, the command that issued less will
> be the only thing left)?
If you're using a mingw-git called "msysgit", check your /etc/profile,
look for LESS
If you're using my mingw32-git package, look in
Otherwise i have no idea where this is defined.
Anyway, it's a "LESS" environment variable, with options for less.
Usually it's "-FRSX", and that option set is quite nice, IMO.
> I am also encountering the issue, for example, that if I scroll
> less output up and then exit, the caret stays on the line that now
> is at the bottom of the screen, so I am "typing over" old lines of
> the buffer. This means I have to make sure I haven't scrolled up
> before exiting. This is different behavior as well to invoking less
> -X in normal terminal.
Yeah, it's been bothering me as well. I'll try to play with LESS
options sometimes, maybe one of them has this side-effect.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
-----END PGP SIGNATURE-----