Apparently with explicit sync it is now not possible to attach a
temporary buffer to a surface that also has an OpenGL context. So we
first attach the temporary buffer, and only after we are done waiting
for window creation do we attach the OpenGL context to the window
surface.
Fixes#7767 (maybe, not installing sway-git to check)
This matches the docs for the goto_tab action and there is no reason not
to have this. For backwards compat 0 and -1 both go to the first previously
active tab as before. However -2 goes to the second previously active
tab, -3 to the third and so on.
Looks like a bug in Py_BuildValue for s# values on that platform. Workaround by
constructing the string directly and passing to to Py_BuildValue.
Fixes#7734
Catalina is actually already EOL as of July 2022 but we dont need
anything from newer releases that isn't detected at runtime. Going to
Catalina allows us to use a better format for the generated DMG (UMNO
instead of ULFO which compresses better).
For some reason destroying the shadow surfaces causes mutter to render one of them at its old relative position. So workaround by not destroying the surfaces, modern mutter anyway seems to hide them when the window is docked.
Fixes#7701
Prevents users from having to install their own NERD font. System fonts
are still used preferentially on Linux but on macOS the builtin one is
used preferentially. Cant find any CoreText API to change this.
Still has to be implemented on macOS. And need to add code to the build
system to bundle the font when building.
The problem was caused by CoreText falling back to the glyph for the
ASCII hyphen U+00AD when the font does not contain a glyph for U+2010.
However, HarfBuzz does not do this automatic fallback (see
https://github.com/harfbuzz/harfbuzz/issues/517). This leads to the
character not being rendered.
To fix this we specialize HarfBuzz glyph lookup for this character
to follow CoreText. HarfBuzz should really do this automatically when
the hb_font is based on a CTFontRef, but I dont have the time/energy to
argue with its maintainers. Note that HarfBuzz already does this
automatic fallback for U+2011.
Hopefully, there aren't many more such special cases in CoreText.
Fixes#7525
