On Wed, Sep 05, 2012 at 10:49:47PM +0200, Romain Francoise wrote: > Nicholas Marriott <nicholas.marri...@gmail.com> writes: > > > Sorry I didn't really give you many clear clues here - we actually need > > to make it pass some code through so the final write is done with the > > charset bit set. How about something like the diff below? > > Ah yes, very nice. It takes care of the acsc and utf-8 modes in one go. > I have two questions, though: > 1) if the tty doesn't have acsc or utf-8, it will use the ascii fallbacks > which are both '+' rather than '|' and '\'. Not sure if that matters.
I don't think it matters. > 2) is this special value (0x1) generally safe in all encodings (it's okay > for ascii, iso-8859 and utf-8, not sure if we care about others)? AFAIK no encoding messes with the control characters. UTF-8 isn't supported for window titles and whatnot anyway although it would be nice if it was eventually. > > > Although I am a little inclined to instead add #[acs] #[noacs] and make > > it use screen_write_cnputs so people can use #[format] stuff which might > > be nice for choose-list. Wouldn't be so nice if you have a window called > > #[foo] though... so maybe not. > > I guess it would be possible to escape the opening bracket where it's not > wanted and teach _cnputs() to unescape or interpret the format as > necessary? Yes this could work but then format_* would need to know to escape the strings it inserts. Would be a bit of a fiddle to get right probably. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
