-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, May 11, 2017 at 07:34:18AM -0500, Richard Owlett wrote:
[...] No clue about MySQL, sorry. > Somewhere I've notes directing output of a command to console and a > file simultaneously. Then I'll have a record of what does and > doesn't happen. Tried the 'script' command - output had too may > non-ASCII characters in output file. This is because script tries to keep everything, ANSI colouring and cursor movements included. If you just want to "see" what was going on, you may issue "soelim typescript" or similar. Or pass it through "less -R", the -R option meaning "go ahead and *interpret* the escape sequences, I know what I'm doing". Details in the man pages. If, OTOH, you want a plain text to store somewhere, you have to filter out the escape sequences, which is not as trivial as it sounds (how do you represent an interactive man page viewing as a "text"?). I'm sure there are tools to help you in that, but I can't offer any off the top of my head. If you want to get text in the first place, the command "tee" might be what you want (but then, if you're doing fancy things, it might be worse). I konw it's counterintuitive at first, but once you realize that "screen" as you see it is somehow a "richer" language than just a stream of text, the problem becomes clear: when you reduce "screen" to a stream of text, that's interpretation, and what you leave out and how becomes a matter of judgement. Cheers - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlkUZfsACgkQBcgs9XrR2kYtRwCaAmcQUL76j1OAAeH3RR8X3ewK OkcAn3f29HTtvKqkJbsHCS77LjPFglkT =DAus -----END PGP SIGNATURE-----
