Startup notification doesn't work in recent versions of Kitty:
> Traceback (most recent call last):
> File "/nix/store/3a3b0xd952gp8jw70k5kh3a4zhgzf0p7-kitty-0.12.3/bin/../lib/kitty/kitty/utils.py", line 216, in init_startup_notification
> return init_startup_notification_x11(window_handle, startup_id)
> File "/nix/store/3a3b0xd952gp8jw70k5kh3a4zhgzf0p7-kitty-0.12.3/bin/../lib/kitty/kitty/utils.py", line 201, in init_startup_notification_x11
> return init_x11_startup_notification(display, window_handle, sid)
> OSError: Failed to load libstartup-notification-1.so with error: libstartup-notification-1.so: cannot open shared object file: No such file or directory
Apparently dispatching of startup notification has been moved to a C
binding in kitty 0.6.0 [1] so the substituion had to be modified to reflect
that. Without this fix Kitty still works except that window managers
which depend on startup notifications to be fired (e.g. Awesome)
cannot apply special placement rules.
The substitution mechanism is also changed to use a patch file to detect
this kind of mistakes in the future.
[1]: https://github.com/kovidgoyal/kitty/commit/b08f4ab5937199187581aa20e3a7aba7b2a34ac6
* flatbuffers: 1.8.0 -> 1.10.0
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/flatbuffers/versions
* flatbuffers: fix build on Darwin and enable checks
Bazel BUILD file is conflicting with build directory on case-insensitive FS
+ checkPhase now runs "make test"
With the current plugin configuration I get the following error when
opening a C/C++ file in ViM:
```
"main.cpp" 246L, 7522C
Loading libclang failed, completion won't be available. Are you sure '/nix/store/jdz3pbl853dw6k0qg54ifd5fplkq7xl8-cla
ng-3.9.1/lib/libclang.so' contains libclang?
```
Some software that depends on libtensorflow (e.g. the Tensorflow Rust
bindings) expect tensorflow.pc to be available. This change adds a
pkgconfig file.
Much improved build with support for GUI libraries and FUEL, the emacs
development environment.
Also directs the work vocabulary to point to /var/lib/factor as a machine-local
writable location. So, scaffolding should work as intended, now.
Vaskó László