hanging in kdialog

2017-07-30 Thread Jos van den Oever
Hi all, KDialog can get stuck waiting for some dbus reply in certain setups. Here is a short command-line that demonstrates this. docker run -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -ti --rm kdeneon/plasma:dev-unstable kdialog --msgbox 'wait for it' This runs kdialog in a docker en

Re: hanging in kdialog

2017-08-03 Thread Jos van den Oever
vice-by-name I realize that the current behavior comes from the desire to have no naked notifications when plasma starts. Perhaps it is better to move the dbus registration of org.freedesktop.Notifications forward instead of relying on a binary like plasma_waitforname. Cheers, Jos > >

Re: hanging in kdialog

2017-08-03 Thread Jos van den Oever
-running-time-out-causes-thunar-to-hang Cheers, Jos Op maandag 31 juli 2017 08:55:11 CEST schreef Jos van den Oever: > Op zondag 30 juli 2017 10:25:39 CEST schreef u: > > There's a review requests from me on KNotification that fixes this. > > Which one is that? I know dvratil su

Re: KDE Review: Rust Qt Binding Generator

2017-09-04 Thread Jos van den Oever
Op maandag 4 september 2017 07:46:28 CEST schreef Kevin Ottens: > On Sunday, 3 September 2017 18:14:49 CEST Jos van den Oever wrote: > > [...] > > The idea of this binding generator is that you write each part in the most > > appropriate language. Rust bindings for Qt are

Re: KDE Review: Rust Qt Binding Generator

2017-09-10 Thread Jos van den Oever
Op maandag 4 september 2017 07:46:28 CEST schreef u: > Are you contributing to it as well? (I started patching it locally but still > need to clean up my work for upstream contribution) I wrote a small Hello World application just now, but it's quite hard. The most important things needed to writ

Re: KDE Review: Rust Qt Binding Generator

2017-09-10 Thread Jos van den Oever
/? id=ddab2e57f65534a0c9766914fb85a90bfe1d24cc Op zondag 3 september 2017 18:14:49 CEST schreef Jos van den Oever: > Dear KDE-ers, > > A new project is up for review: Rust Qt Binding Generator. > > The project is a command-line executable that creates Rust code and Qt code > from a binding description in JSON. >

Re: CI system maintainability

2019-04-05 Thread Jos van den Oever
On Thursday, March 28, 2019 7:40:09 AM CEST Ben Cooksley wrote: > At this point given the amount of effort required to maintain a CI > system vs. the amount of care actually being given by some developers > (who are ignoring it's failure emails) it becomes questionable whether > the effort is worth

Re: Gitlab Turn-off Issues

2020-07-08 Thread Jos van den Oever
On dinsdag 30 juni 2020 14:06:47 CEST Ben Cooksley wrote: > As an interim measure, I have implemented a banner shown only on New > Issue pages. That's very clear. ⤳Jos signature.asc Description: This is a digitally signed message part.

Re: Changing Original Library API when writing Wrappers

2022-01-31 Thread Jos van den Oever
A small explanation for people that wonder why converting from the Rust type std::path::Path to std::string::String can fail. std::string::String is always UTF-8, but std::path::Path is not because not all filesystems encode paths in UTF-8 [0]. In Qt, QString is (possibly invalid) utf16. Openin