Comrades:
I recently moved to Quebec and now need accents and all that fun
stuff. I also recently moved off the xft branch of st and to the
standing tip, and I've noticed that I can't for the life of me get
diacriticals to display. They display fine in dwm and dmenu, urxvt,
and xft version of st
Morning Peter,
st-0.2.1 works fine for simple diacritics (such as those in your
email signature), at least with font:
-*-terminus-medium-r-*-*-*-220-*-*-*-*-iso10646-*
I'd guess it's the default x / st font settings working against you.
I know that isn't much of an answer.
Why have you moved off
Yo Nick:
I moved because I wanted to catch the action in tip -- last change in
xft was 7 months ago via me. My font line in config.h is precisely
what you have. I'm a little confused why broken default X font stuff
(if that's the case) would be the culprit here and yet cause no
headaches in dwm.
To confirm, I just tried st tip (main branch), and the diacritics from
this email displayed without issue.
Hopefully somebody with more skill than being able to type "works
for me" may be able to help you.
Nick
I should add that when I launch st I get:
peterjh@trilx220 st $ st
erresc: unknown csi ESC[?17;0;64c
2012/9/17 Nick :
> To confirm, I just tried st tip (main branch), and the diacritics from
> this email displayed without issue.
>
> Hopefully somebody with more skill than being able to type "wo
On Mon, Sep 17, 2012 at 11:17:54AM -0400, Peter Hartman wrote:
> I should add that when I launch st I get:
>
> peterjh@trilx220 st $ st
> erresc: unknown csi ESC[?17;0;64c
I don't. Did you do make install, or the tic command it would run,
with st.info?
Yes, and ls -la ~/.termcap/s/ has st and st-256colors, as it should
(and I nuked the old ones).
2012/9/17 Nick :
> On Mon, Sep 17, 2012 at 11:17:54AM -0400, Peter Hartman wrote:
>> I should add that when I launch st I get:
>>
>> peterjh@trilx220 st $ st
>> erresc: unknown csi ESC[?17;0;64c
>
> I
I use also the tip and I can use diacritics (I usually have to write a lot
of them in spanish). The font I use is
-*-terminus-medium-r-*-*-*-160-72-72-*-80-*-*. Could you use the -f option
and sent the session to us?.
> peterjh@trilx220 st $ st
> erresc: unknown csi ESC[?17;0;64c
st doesn't implement this sequence, so it is a bit strange that you receive
always this sequence only for starting it. Can you say me what value do you
have in TERM?.
Some new patches for st.
>From 17025c9ab88bb8560bac3896c2384ad060c6e8d9 Mon Sep 17 00:00:00 2001
From: "Roberto E. Vargas Caballero"
Date: Mon, 17 Sep 2012 19:03:35 +0200
Subject: Add xcalloc wrapper
malloc and realloc are called through xmalloc and xrealloc, so calloc should
be called through xc
TERM inside st = "st-256color"
TERM outside st (i.e. in urxvt where I launch it) is = "screen"
xlsfonts indicates terminus is there, etc.
xset q also indicates it is there.
Here's the st -f output:
http://sprunge.us/IfXW
2012/9/17 Roberto E. Vargas Caballero :
>> peterjh@trilx220 st $ st
>> erre
> http://sprunge.us/IfXW
Note the first "command" I type in that is é
--
sic dicit magister P
Université du Québec à Montréal / Loyola University Chicago
http://individual.utoronto.ca/peterjh
gpg 1024D/ED6EF59B (7D1A 522F D08E 30F6 FA42 B269 B860 352B ED6E F59B)
gpg --keyserver pgp.mit.edu --rec
2012/9/17 Peter Hartman :
>> http://sprunge.us/IfXW
> Note the first "command" I type in that is é
peterjh@trilx220 st $ locale
LANG=fr_FR@euro
LC_CTYPE="fr_FR"
LC_NUMERIC="fr_FR"
LC_TIME="fr_FR"
LC_COLLATE="fr_FR"
LC_MONETARY="fr_FR"
LC_MESSAGES="fr_FR"
LC_PAPER="fr_FR"
LC_NAME="fr_FR"
LC_ADDRES
> TERM inside st = "st-256color"
Can you send the output of 'infocmp st-256color'?
> Here's the st -f output:
> http://sprunge.us/IfXW
Uhmmm, but in this file there isn't any diacritic :S. I need some of them in
order to try see where can be the problem.
On Mon, Sep 17, 2012 at 02:37:44PM -0400, Peter Hartman wrote:
> > http://sprunge.us/IfXW
> Note the first "command" I type in that is é
Interesting, because I can't see the 'è' in the file, so it is not a problem
of the fonts. I don't know why but st if doing something strange with the
character
> Change all those little LC_ and LANG vars over now convinces st to behave.
The problem seems that st suppouse the input keyboard is a utf8 device, and
in the case you use a non utf8 locale it detects non ascii characters as
first byte of a multibyte utf8 character (if you have good luck, because
16 matches
Mail list logo
