Hello Phillip,<br><br><div class="gmail_quote">On Tue, Feb 17, 2009 at 1:53 AM, Phillip Warner <span dir="ltr"><<a href="mailto:phillip.c.warner@gmail.com">phillip.c.warner@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;">
<br>
The code does not work well for me. Instead it actually creates a<br>
memory sink hole and the excessive grepping hogs the CPU (bogging down<br>
my poor PII). </blockquote><div><br>Do you mean that what is in SVN is worse than the wrapper?<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;">
I recommend taking it out of SVN.</blockquote><div><br>Will do, if we don't get to a better solution.<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;">
Perhaps instead a trap can be used to manually call a refresh. The<br>
user presses CTRL+l (lower 'L) and the screen refreshes then.</blockquote><div><br>I'd prefer to work a while on something not trashing the program usability before...<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As an alternative, a wrapper could be written for all of the dialog<br>
commands. That way the code can still be clean, but the wrapper will<br>
manually cause a refresh.</blockquote><div><br>Let's try some alternatives before such an invasive change.<br>Does the situation improve if you apply the attached patch?<br><br><span class="HcCDpe">On Mon, Feb 16, 2009 at 9:40 PM</span>, Phillip Warner <span dir="ltr"><<a href="mailto:phillip.c.warner@gmail.com">phillip.c.warner@gmail.com</a>></span> wrote:<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
I have not gotten a chance to try this out yet, but after looking at
the patch I'd suggest a minor change. Right now the function is only
called if Term="rxvt", but what about rxvt-unicode or screen? </blockquote><div><br>I can match "^rxvt.*", for sure.<br>Have you had any problem on $TERM==screen? We don't want the workaround enabled on good configurations.<br>
</div><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">Instead
of checking for TERM, I suggest that you simply have a switch to
activate the function. That way the admin can decide on the fly
without having to modify the script itself.</blockquote><div><br>I don't agree here, at least not as our first attempt (maybe as a fallback). I'd prefer sbopkg to work right out of the box without requiring the admin to enable strange workarounds.<br>
</div> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
--phillip<br>
</blockquote></div><br>Thank you for your feedback<br>-- <br>Mauro Giachero<br><br>
--~--~---------~--~----~------------~-------~--~----~<br>
You received this message because you are subscribed to the Google Groups "sbopkg-discuss" group. <br> To post to this group, send email to sbopkg-discuss@googlegroups.com <br> To unsubscribe from this group, send email to sbopkg-discuss+unsubscribe@googlegroups.com <br> For more options, visit this group at http://groups.google.com/group/sbopkg-discuss?hl=en<br>
-~----------~----~----~----~------~----~------~--~---<br>
<br>