<div class="gmail_quote">On Thu, Jul 30, 2009 at 5:15 PM, Chess Griffin <span dir="ltr"><<a href="mailto:chess.griffin@gmail.com">chess.griffin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
TBH, I'm not sure we necessarily need to try to solve all of these<br>
problems in sbopkg. If the GNU Screen extra characters issue bothers<br>
someone, they could work around it by putting something like the<br>
following untested kludge in their .bashrc:<br>
<br>
case "$TERM" in<br>
screen*) alias sbopkg="TERM=xterm-color sbopkg" ;;<br>
esac</blockquote><div><br>True. Maybe we should simply document the issue somewhere.<br>However, the current workaround is problematic on -current, so it should be removed. While at it, if the export hack works, we can simply put it in.<br>
The next time a terminal issue arises, we scrap the whole idea of working around terminal issues and start documenting the known problems.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
However, the signal handling issue might be a different animal that<br>
cannot easily be worked around like that. I just have not looked at<br>
it yet.</blockquote><div><br>This is far outside the sbopkg scope, though.<br clear="all"></div></div><br>-- <br>Mauro Giachero<br>