Liam Hupfer
Liam Hupfer
Based on the recent feedback I think we can close this and revisit it if anyone pipes up with steps to reproduce, thanks all
> It's weird that it uses secret-tool instead of using the libsecret API, which would doubtlessly be faster than starting a new process. I did a quick web search and...
> Since Resources uses a binary (also built against glibc) that is spawned outside Flatpak's sandbox to gather process information, it won't work on non-glibc distros. Worth noting this also...
Indeed, this is a result of completion style configuration.
Seems many are encountering the issue, particularly Flatpak users (me too). Instead of commenting, consider adding your đź‘Ť to the [issue](https://github.com/nextcloud/desktop/issues/5466) so it shows up higher on [the issue board...
Initial sync worked immediately after deleting and restoring the account from the client, but the problem returned after exiting and relaunching the client. The CLI options for logging didn’t seem...
``` oama: authorizeEmail: Unknown "Error in $: Failed reading: not a valid json value" CallStack (from HasCallStack): error, called at lib/OAMa/Authorization.hs:491:25 in oama-0.19.0-KcEsBcgBT2n4YdjWjbjUky:OAMa.Authorization ``` The README documents `--device` but I...
IMO, if you are linking to a heading, it’s relevant enough to be its own node in the graph. But this seems like it shouldn’t be difficult to support. Re:...
Great point. With future links in mind, I think case insensitive roam: link resolution should be the default (and not even exposed as an option, since I don’t think allowing...
Will need an `expand-file-name` somewhere, plus a test, ideally. Or updating the docstring to mention that `expand-file-name` should be used, but probably better to follow Postel’s law