On 9. 4. 2015 11:27, Paul Moore wrote: > There's a further problem in that the "clear" command (invoked in > /etc/bash.bash_logout "to increase privacy", which hardly seems like a > crucial reason...)
It's useful for classical tty's on Linux. I can't think of a situation where it would be useful on Windows, partly due to the terminal handling issues mentioned below. > uses ANSI escape codes that aren't supported by > ConEmu (AFAICT, they aren't all valid according to the Wikipedia page > - CSI 3;J has no documented behaviour - but there's also a bug in how > CSI H CSI 2J is handled). From what I gathered from the ncurses source code, the escape sequences seem to be chosen according to TERM. Maybe you need to change/set it to something compatible with ConEmu. > Again, I don't see a way of disabling this behaviour, apart from (1) > removing (or making non-executable) the clear command, or (2) editing > /etc/bash.bash_logout. Any suggestions on the "right" way of handling > this? $ echo 'export SHLVL=0' > ~/bash.bash_logout Until proven otherwise, consider this a Horrible Hack(TM), but it should allow you to avoid changing system files. -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
