Quoth Roberto E. Vargas Caballero:
> > Because if so, there are many many cases where there is no
> > precombined version in unicode, so you have to use the combining
> > characters.
>
> Yeah, of course, there are a lot of them. The point here is if these
> cases are common or not. All the chara
> Because if so, there are many many cases where there is no
> precombined version in unicode, so you have to use the combining
> characters.
Yeah, of course, there are a lot of them. The point here is if these
cases are common or not. All the characters that I use can be written
with unicode ch
Quoth Roberto E. Vargas Caballero:
> As far as I know, this should be the correct behaviour, but I am not sure
> about if we need to add this feature, because if you can use the unicode
> character instead of the unicode sequence.
Are you talking about precombined characters vs combining sequence
> > Urxvt's behaviour is also the same as Xterm with an added bonus: it
> > actually renders the combined Unicode sequence where as on Xterm and st,
As far as I know, this should be the correct behaviour, but I am not sure
about if we need to add this feature, because if you can use the unicode
ch
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\
