It runs, but blinks.
There's a workaround: start MacVim, and uncheck Preferences -> Advanced -> Use
Core Text renderer
Then quit MacVim, and when you start it, it shouldn't blink anymore.
I gather that a better fix is pending upstream.
I assume you saw the link to the upstream issue about the core text problem
that I put in the ticket.
https://github.com/macvim-dev/macvim/issues/751
Ken
> On Oct 10, 2018, at 02:02, Richard L. Hamilton wrote:
>
> It runs, but blinks.
>
> There's a workaround: start MacVim, and uncheck Pref
Yes, that's where I saw the workaround. I gather a fix that doesn't need that
will be out probably in a few days.
> On Oct 10, 2018, at 09:11, Ken Cunningham
> wrote:
>
> I assume you saw the link to the upstream issue about the core text problem
> that I put in the ticket.
>
> https://git
on Mojave, with Xcode 10.0:
$ xephem
Warning: Fatal Error:
_XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL
[1]34379 segmentation fault xephem
Any troubleshooting advice is appreciated.
Thanks,
Kevin Horton
Hi,
I'm trying to figure out why port:kde4-workspace fails to build on 10.14, with
linker errors that suggest that the system clang has a subtle new and
incompatible symbol visibility policy. (https://trac.macports.org/ticket/57332).
Are there known issues with Qt4 and/or KDE4 software on Apple
The Qt4-provided native apps seem to work correctly with no display issues.
I have "my usual" ports that use Qt4 mostly working on 10.14: mostly GNU Radio
and related. These apps are using PyQt4 as the interface to Qt4. At least in my
testing, PyQt4 has some display glitches that make it challen
About the flashing you mention: is that related to the use of raster mode
rendering, like KDE4 apps also do?
I've no idea. I just got to this point today LOL ... barely enough time to
debug other issues right now with my work load! - MLD
On Wed, Oct 10, 2018, at 4:55 PM, René J.V. Bertin wrote:
> About the flashing you mention: is that related to the use of raster
> mode rendering, like KDE4 apps also
On Oct 10, 2018, at 09:55, Kevin Horton wrote:
> on Mojave, with Xcode 10.0:
>
> $ xephem
> Warning: Fatal Error:
> _XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL
> [1]34379 segmentation fault xephem
>
> Any troubleshooting advice is appreciated.
Sounds li
To me it sounds almost like back when xorg-libXt needed to be linked with a
-flat-namespace option if one was going to use openmotif with it. But as I
recall, the current version of open motif isn't supposed to need that anymore
But it could still be a building or linking issue, something to d
I wonder if the flashing isn't a rendering issue similar to what MacVim is
having, where the behavior of a legacy rendering technique changed?
> On Oct 10, 2018, at 14:57, Michael Dickens wrote:
>
> The Qt4-provided native apps seem to work correctly with no display issues.
>
> I have "my usua
On Oct 10, 2018, at 3:36 PM, Ryan Schmidt wrote:
>
>
>
> On Oct 10, 2018, at 09:55, Kevin Horton wrote:
>
>> on Mojave, with Xcode 10.0:
>>
>> $ xephem
>> Warning: Fatal Error:
>> _XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL
>> [1]34379 segmentation fault
Hi René,
Long time no see.
> On 11 Oct 2018, at 5:10 am, René J.V. Bertin wrote:
> I'm trying to figure out why port:kde4-workspace fails to build on 10.14,
> with linker errors that suggest that the system clang has a subtle new and
> incompatible symbol visibility policy.
> (https://trac.ma
libkdegames doesn't build yet, due to some changes in build procedures
apparently; there is a ticket, and hopefully there will shortly be a proper
fix. Having said that, with a jury-rigged way around that (not correct, but it
works), all the KDE4 games would build. But they have display issues
14 matches
Mail list logo
