[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay on macOS due

From: Andrew Janke
Subject: [Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay on macOS due to default Monaco font
Date: Thu, 21 Mar 2019 20:17:08 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.75 Safari/537.36

Follow-up Comment #8, bug #55958 (project octave):

Well: file #46607 – I did the naive thing and just changed the font face and
size in that `#ifdef Q_OS_MAC` section, and it had no apparent effect. When I
deleted ~/.config/octave and fired up ./run-octave from the build directory,
it still used Monaco 10 as the default font for the Command Window and

Maybe it's getting those defaults from somewhere else, and this section just
applies to the defaults for the embedded qterminal widget object, which are
themselves immediately overriden by the application-level preferences, which
get their defaults from some other location.

> if we ever do try to reconcile with that, maybe we could try to link with
qtermwidget as a library?

That might make sense. On macOS, it's not hard to install; I've already got a
Homebrew formula for it –
– and it's available as a package in Debian –
– and Ubuntu – https://packages.ubuntu.com/source/xenial/qtermwidget. So
taking it as a library instead of bundled source sounds maybe feasible to me.
It's just a question of whether the recent distro releases have picked up a
new-and-good-enough version of QTermWidget for your purposes.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]