From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Discord should use system-wide electron
Date: Wed, 05 Apr 2023 06:44:53 +0200 [thread overview]
Message-ID: <20230405044453.0wb8wwnfOiZWLpyIkZZZLnMvO4apaL0KSB2HKaadV3Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43280@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/issues/43280#issuecomment-1496910438
Comment:
> It seems like as of right now Discord does not respect ~/.config/electron-flags.conf
Are you using the latest version of the discord package? It has electron 22 which would be able to read the file. Also maybe try renaming it to `electron22-flags.conf`, it appears that some builds only look for the file matching their version.
Replacing the electron they ship might not be viable, since discord maintains a [set of patches](https://github.com/electron/electron/compare/22-x-y...discord:electron:22-x-y) on top of plain electron.
Those patches also don't seem to contain anything that would disable the conf file.
next prev parent reply other threads:[~2023-04-05 4:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 3:42 [ISSUE] " JuniorSuperTux
2023-04-05 4:44 ` 0x5c [this message]
2023-04-05 7:01 ` JuniorSuperTux
2023-04-05 8:22 ` classabbyamp
2023-04-05 12:20 ` JuniorSuperTux
2023-04-05 12:21 ` JuniorSuperTux
2023-04-06 3:55 ` 0x5c
2023-04-06 11:54 ` JuniorSuperTux
2023-04-09 14:12 ` JuniorSuperTux
2023-04-10 14:20 ` JuniorSuperTux
2023-04-10 14:24 ` JuniorSuperTux
2023-04-10 15:40 ` Discord does not respect electron-flags.conf paper42
2023-04-11 5:31 ` [ISSUE] [CLOSED] " classabbyamp
2023-04-11 5:31 ` classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230405044453.0wb8wwnfOiZWLpyIkZZZLnMvO4apaL0KSB2HKaadV3Y@z \
--to=0x5c@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).