Hi,
On Fri, Jun 27, 2014 at 04:54:08PM -0500, Eric Pruitt wrote:
> I noticed that in st, combined Unicode characters don't seem to be
> preserved in memory. For example, if I run "printf 'AB\xcd\x9dCDE\n'" in
> a Xterm then select the resulting line, I the clipboard data includes
> the Unicode seq
I noticed that in st, combined Unicode characters don't seem to be
preserved in memory. For example, if I run "printf 'AB\xcd\x9dCDE\n'" in
a Xterm then select the resulting line, I the clipboard data includes
the Unicode sequence:
~% echo $TERM
xterm-256color
~% printf 'AB\xcd\x9dCDE\
Hello,
Sylvain wrote:
> As I was asked off-list, please, keep this thread shut down.
I think these are appropriate:
http://38.media.tumblr.com/tumblr_m51pu9IEYc1qzm5y8o14_r1_250.gif
http://38.media.tumblr.com/tumblr_m51pu9IEYc1qzm5y8o1_250.gif
yours,
Bobby
On Thu, Jun 26, 2014 at 06:01:08PM -0300, Amadeus Folego wrote:
> Hadrian,
>
> please do not tell that you represent everyone, you don't. Also what you
> just said is like your opinion, man.
Indeed.
As I was asked off-list, please, keep this thread shut down.
Thank you.
There were a few occurrences of strcmp and strlen being called on Glyph.c[],
which is not always null-terminated (this actually depends on the last values in
the buffer s in ttyread()). This patch replace all the calls to strcmp with a
test on c[0] directly or a call to tlinelen, and the one to str
