Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Flatpak] Add link to adding RPC for Flatpak Discord client #45

Closed
ethanholz opened this issue Nov 12, 2021 · 2 comments
Closed

[Flatpak] Add link to adding RPC for Flatpak Discord client #45

ethanholz opened this issue Nov 12, 2021 · 2 comments

Comments

@ethanholz
Copy link

Please add the following to link to the README or Flatpak to show how to enable RPC for a Flatpak of Discord. I recognize that people can just find this but it would be helpful to have it for new users. Please view the following for more information for this flatpak: https://github.com/flathub/com.discordapp.Discord/wiki/Rich-Precense-(discord-rpc).
@andweeb
Copy link
Owner

andweeb commented Nov 14, 2021

Hi @ethanholz good call!

I've added the link to the flatpak instructions to the README and also generalized it a bit for folks that may be using snap or others. Thanks!

@jiriks74
Copy link

It's now fixed in #129 - you don't need to do some workaround anymore as long as it gets merged.
Before it does you can checkout the pull request.

jiriks74 referenced this issue in jiriks74/presence.nvim Dec 5, 2023
@jiriks74
[#45] Project rewrite
7ffa91e 
https://openproject.stefka.eu/work_packages/45
jiriks74 added a commit to Lamby777/presence.nvim that referenced this issue Apr 17, 2024
@jiriks74
feat(docs): Update README to have the new location of assets (andweeb#45
442e322 
)

[69] Make workflow compatible with medium act images

https://openproject.stefka.eu/work_packages/69
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ethanholz @andweeb @jiriks74