[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55958] [octave forge] (symbolic) Incorrect sy
From: |
Andrew Janke |
Subject: |
[Octave-bug-tracker] [bug #55958] [octave forge] (symbolic) Incorrect symbolic dispay |
Date: |
Thu, 21 Mar 2019 18:01:00 -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 #6, bug #55958 (project octave):
Heh. I've already talked upstream into switching to Menlo:
https://github.com/lxqt/qtermwidget/pull/259/files. I'll ask them about 12
point, too.
Upstream for the qterminal widget has diverged *significantly* from what we
have in Octave. Support for the embedded widget is now the QTermWidget project
- https://github.com/lxqt/qtermwidget - and qterminal is a client project of
it that uses QTermWidget to build a standalone terminal emulator app. So we
cannot import upstream code directly, and we're diverged enough we may as well
make small changes in our fork as suits us.
My recommendation is just to replace that "Monaco"/11 point under Q_OS_MAC
with "Menlo"/12 point. I'd go so far as to patch that change into the upcoming
Octave.app 5.1.0 release.
There have been a lot of changes (and ostensibly improvements) since Octave
forked qterminal, but macOS support there has lagged recently. I'm currently
working with the QTermWidget/QTerminal folks to get macOS support back up to
speed. (All of which I'm doing because I want to fix bug #55913.) (I know I'm
harping on Mac stuff, but that is a supported Octave platform, right?) After
that's working, maybe we can consider doing a re-import from upstream.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55958>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay, anonymous, 2019/03/19
- [Octave-bug-tracker] [bug #55958] [octave forge] (symbolic) Incorrect symbolic dispay, Mike Miller, 2019/03/20
- [Octave-bug-tracker] [bug #55958] [octave forge] (symbolic) Incorrect symbolic dispay, Z. M., 2019/03/20
- [Octave-bug-tracker] [bug #55958] [octave forge] (symbolic) Incorrect symbolic dispay, Mike Miller, 2019/03/21
- [Octave-bug-tracker] [bug #55958] [octave forge] (symbolic) Incorrect symbolic dispay, Andrew Janke, 2019/03/21
- [Octave-bug-tracker] [bug #55958] [octave forge] (symbolic) Incorrect symbolic dispay, Mike Miller, 2019/03/21
- [Octave-bug-tracker] [bug #55958] [octave forge] (symbolic) Incorrect symbolic dispay,
Andrew Janke <=
- [Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay on macOS due to default Monaco font, Mike Miller, 2019/03/21
- [Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay on macOS due to default Monaco font, Andrew Janke, 2019/03/21
- [Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay on macOS due to default Monaco font, Andrew Janke, 2019/03/21
- [Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay on macOS due to default Monaco font, Andrew Janke, 2019/03/21
- [Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay on macOS due to default Monaco font, Mike Miller, 2019/03/22
- [Octave-bug-tracker] [bug #55958] Incorrect symbolic dispay on macOS due to default Monaco font, Torsten Lilge, 2019/03/23