On Tue, Dec 23, 2014 at 11:44 AM, Rich Felker <dal...@libc.org> wrote: > On Tue, Dec 23, 2014 at 10:23:43AM -0600, Rob Landley wrote: >> >> >> On 12/22/2014 11:37 PM, Rich Felker wrote: >> > On Mon, Dec 22, 2014 at 10:21:26PM -0600, Rob Landley wrote: >> >> If "less" is a priority, that actually helps prioritize the rest of >> >> them. Once I've written the basic "navigate a line" infrastructure (with >> >> querying screen size via ansi probe fallback, and reassembling escape >> >> sequences that got decoupled going over serial line; I fixed both of >> >> these in busybox several years ago), then stacking them isn't quite as >> >> big a deal. >> > >> > I hope you'll have an option just to rely on TIOCGWINSZ. The escapes >> > that cause the terminal to "echo back" a response are considered a >> > security misdesign by some people (myself included) and they're also >> > problematic from the standpoint that you don't know if they'll be >> > supported and that you can't distinguish between a terminal that >> > doesn't support them and one which is just slow to respond. I realize >> > you don't have any other option on serial terminals, but thankfully >> > lots of us don't have to deal with serial terminals. >> >> Lots of us _do_ have to deal with serial terminals. > > Yes, I know. > >> If you export $ROWS and $COLUMNS it'll do that instead of probe, and I >> can add a compile-time config symbol to switch it off if you care that much. > > Exporting ROWS and COLUMNS precludes runtime size changes though. The > correct way to handle size is TIOCGWINSZ. Perhaps you could use > TIOCGWINSZ for device numbers that indicate virtual terminal or pty > and only fall back to the ugly methods for serial ports?
annoyingly, adb (Android Debug Bridge) doesn't currently pass window size changes through, so until someone fixes that Android users count as serial port users too :-( >> >> I do follow a security researcher on twitter (@0xabad1dea) and for a >> >> while she had as her handle: >> >> >> >> echo -e "Melissa \xe2\x80\xae ασσιλέΜ \xe2\x80\xed" >> >> >> >> So it would be nice to get the reversal codes to work. But given that >> >> xfce's terminal doesn't handle it either... >> >> >> >> (Dalias wrote a terminal that probably does. I should compile/install >> >> that and try it out...) >> > >> > Mine doesn't. Bidirectional text is the main (only?) multilingual >> > feature uuterm is missing. >> >> Even for just "more", the fontmetrics of combining characters is... fun. >> >> I _mostly_ punt this to the display layer, but this piece of >> infrastructure probably should care. > > Programs writing to a terminal have no need to care specially about > RTL characters; it's all in the presentation layer. On the other hand > they _might_ need to know about RTL/LTR overrides (but probably not) > and they probably need to know about bidi _nesting_ (if you care to > support that, but it's probably useless). > > Rich > _______________________________________________ > Toybox mailing list > Toybox@lists.landley.net > http://lists.landley.net/listinfo.cgi/toybox-landley.net -- Elliott Hughes - http://who/enh - http://jessies.org/~enh/ Java i18n/JNI/NIO, or bionic questions? Mail me/drop by/add me as a reviewer. _______________________________________________ Toybox mailing list Toybox@lists.landley.net http://lists.landley.net/listinfo.cgi/toybox-landley.net
