Search Criteria
Package Details: logseq-desktop-bin 0.9.8-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/logseq-desktop-bin.git (read-only, click to copy) |
---|---|
Package Base: | logseq-desktop-bin |
Description: | A privacy-first, open-source platform for knowledge sharing and management. |
Upstream URL: | https://github.com/logseq/logseq |
Keywords: | clojure clojurescript git graph knowledge-base knowledge-graph local-first markdown org-mode |
Licenses: | AGPL3 |
Conflicts: | logseq-desktop, logseq-desktop-git |
Provides: | logseq-desktop |
Submitter: | xuanwo |
Maintainer: | xuanwo (Manjusaka) |
Last Packager: | xuanwo |
Votes: | 36 |
Popularity: | 3.28 |
First Submitted: | 2021-12-02 15:26 (UTC) |
Last Updated: | 2023-05-24 07:02 (UTC) |
Latest Comments
1 2 Next › Last »
MoritzWM commented on 2023-04-24 06:28 (UTC)
Regarding wayland support: I managed to natively run it in wayland (with title bar and fractional scaling support) by using the logseq-desktop-bin (not wayland-bin!) package and writing
into $XDG_CONFIG_HOME/logseq-flags.conf
genericity commented on 2023-04-15 05:34 (UTC)
The Exec= line in desktop file should be: Exec=/usr/bin/logseq %U instead of Exec=/usr/bin/logseq
In KDE, the latter causes "xdg-open logseq://..." to attempt to download the contents of "logseq://..." URL first, instead of passing it in cmdline as is.
All other x-scheme-handler desktop files seem to have this %U arg in Exec= line, so I guess it's required.
alxjsn commented on 2022-11-03 21:19 (UTC)
Another way to get logseq to open links is by appending the following line:
x-scheme-handler/logseq=logseq.desktop;
to: ~/.local/share/applications/mimeinfo.cache
ddavo commented on 2022-11-03 17:49 (UTC)
@douglarek
This is because logseq is not registered to open logseq:// links. In the meantime, you can copy the link it redirects you to, and paste it on the terminal
logseq <link>
douglarek commented on 2022-11-01 03:56 (UTC) (edited on 2022-11-01 03:56 (UTC) by douglarek)
Chrome in KDE plasma does not seem to login.
xuanwo commented on 2022-08-17 03:34 (UTC)
@CorrectRoadH Never mind, I just forgot.
CorrectRoadH commented on 2022-08-17 03:24 (UTC)
@xuanwo I'm sorry.My idea is that both logseq-desktop and logseq-desktop-bin are maintained by you, but the former has been updated and the latter has not. I thought it was a technical problem.Maybe the translation software translated my previous words too bluntly.
xuanwo commented on 2022-08-17 03:20 (UTC)
@CorrectRoadH Nice question that ruined my good mood of the day, thanks.
CorrectRoadH commented on 2022-08-16 02:32 (UTC)
Why hasn't logseq 0.8.0 been updated yet?
1 2 Next › Last »