On 2016年03月09日 16時31分, Maxwell Anselm wrote:
On Tue, Mar 8, 2016 at 3:57 AM, Garmine 42 wrote:
You need to enable unicode in xterm - i.e. use uxterm instead of xterm.
I already have unicode enabled in xterm. And Braille does show up if I
switch to the default bitmap font, but for whatever re
On Tue, Mar 8, 2016 at 3:57 AM, Garmine 42 wrote:
>
> On 8 March 2016 at 03:49, Maxwell Anselm wrote:
> > I had the same issue in xterm. Changing fonts didn't fix it, but switching
> > to urxvt (with the same font) did. It seems like there's something screwy
> > with xterm's unicode support.
> >
On 8 March 2016 at 03:49, Maxwell Anselm wrote:
> I had the same issue in xterm. Changing fonts didn't fix it, but switching
> to urxvt (with the same font) did. It seems like there's something screwy
> with xterm's unicode support.
>
> On Mon, Mar 7, 2016 at 12:12 AM, Grady Martin
> wrote:
>
>>
I had the same issue in xterm. Changing fonts didn't fix it, but switching
to urxvt (with the same font) did. It seems like there's something screwy
with xterm's unicode support.
On Mon, Mar 7, 2016 at 12:12 AM, Grady Martin
wrote:
> On 2016年02月17日 00時06分, Garmine 42 wrote:
>
>> It was indeed a
On 2016年02月17日 00時06分, Garmine 42 wrote:
It was indeed a font issue, the one I used did not contain the braille
characters. Because the same problem existed on my gettys I thought it
was an encoding issue or something else. Using terminus font at the
moment (as suggested) and it works perfectly f
On 16 February 2016 at 22:46, Christian Hesse wrote:
> Garmine 42 on Tue, 2016/02/16 18:33:
>> Hi!
>>
>> Since the update to 2.0 the usage graphs use nonexisting fonts - both
>> TTY and uxterm show the "empty box" unicode character instead of the
>> fonts shown on htop 2.0 screenshots.
>>
>> I di
Garmine 42 on Tue, 2016/02/16 18:33:
> Hi!
>
> Since the update to 2.0 the usage graphs use nonexisting fonts - both
> TTY and uxterm show the "empty box" unicode character instead of the
> fonts shown on htop 2.0 screenshots.
>
> I did not find any missing dependency for htop on my system.
>
>
On Tue, 16 Feb 2016 18:40:30 +0100, Nicolas F. wrote:
>Might be a locale issue as opposed to a font issue. That being said,
>works fine here.
Oops, I missed the OP's "empty box" information.
The OP likely expects what we get using utf8, but even iso88591 shows a
tree, it's just not using "├─", bu
* Garmine 42 [16/02/2016 18:35:23] wrote:
> Hi!
>
> Since the update to 2.0 the usage graphs use nonexisting fonts - both
> TTY and uxterm show the "empty box" unicode character instead of the
> fonts shown on htop 2.0 screenshots.
>
> I did not find any missing dependency for htop on my system.
>
Tue, 16 Feb 2016 18:48:22 +0100
Ralf Mardorf :
> What is the "usage graph"? Do you mean the "tree view"? If so try
> pushing F5.
F2, -> (choose a meter in one of the columns), hit SPACE (F4 in htop 1.x)
--byte
pgpOqsHjl4K2r.pgp
Description: Digitale Signatur von OpenPGP
On Tue, 16 Feb 2016 18:33:57 +0100, Garmine 42 wrote:
>Since the update to 2.0 the usage graphs use nonexisting fonts
What is the "usage graph"? Do you mean the "tree view"? If so try
pushing F5.
Might be a locale issue as opposed to a font issue. That being said,
works fine here.
$ locale
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.U
Hi!
Since the update to 2.0 the usage graphs use nonexisting fonts - both
TTY and uxterm show the "empty box" unicode character instead of the
fonts shown on htop 2.0 screenshots.
I did not find any missing dependency for htop on my system.
Do anyone else have this issue?
Any ideas? Shall I ins
13 matches
Mail list logo
