From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Bug: gufw does not start
Date: Mon, 17 May 2021 04:46:47 +0200 [thread overview]
Message-ID: <20210517024647.WiUBaSANpOFsjh6VyIySiP2cK46gXdo7JthU6jOFOn0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30914@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 247 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/30914#issuecomment-841942472
Comment:
I don't think so, I needed `-E` due to display variables I think.
No idea what your error is about :/
next prev parent reply other threads:[~2021-05-17 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 12:08 [ISSUE] " el-christianito
2021-05-15 15:28 ` ericonr
2021-05-16 16:35 ` el-christianito
2021-05-17 2:46 ` ericonr [this message]
2021-05-17 2:47 ` ericonr
2021-05-18 6:50 ` el-christianito
2021-05-18 17:52 ` el-christianito
2021-05-18 17:52 ` [ISSUE] [CLOSED] " el-christianito
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=20210517024647.WiUBaSANpOFsjh6VyIySiP2cK46gXdo7JthU6jOFOn0@z \
--to=ericonr@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).