Jason Heeris

> ...? But in that case you need to have invoked them using --target in the first place, which means you already know what the triple is. Just from experience...

> Cargo needs to search for other Cargo.toml files to discover if it is part of a workspace. I don't think that is something that can be changed, I guess...

@epage - you mean, literally the empty section `[workspace]`?

I had this exact problem because I entered `~/Code/p3-gitlab-svn/bin/python` in my project settings. Anaconda would see that as different to `/home/heerij/Code/p3-gitlab-svn/bin/python` and keep killing and restarting the interpreter. But... it...

`Into` might be better, because then callers can still just pass a `Duration` if they want a timeout. See eg. [Calloop's `run()` method](https://github.com/Smithay/calloop/blob/master/src/loop_logic.rs#L424).

Your schema seems to indicate that this setting exists, and should at least be accessible via the Dconf editor. However, when I browse to your extension's settings, I see: 

Workaround: ``` gsettings --schemadir .local/share/gnome-shell/extensions/[email protected]@gmail.com/schemas/ set org.gnome.shell.extensions.unlockDialogBackground picture-options 'wallpaper' ```

> You need to use extension settings ui to change background at once, then you can see it in Dconf. I had used the settings UI to change the background...

*no option for picture mode, I mean.

> Why don't you use UI to change background? I did. There is no option for picture mode though, and Dconf doesn't know it should be there.