Paul is right, custom mua support outside xdg is not really needed at all.
xdg-email works just fine in a text-only environment, and these users can
simply specify their preferred mailer(s) in the MAILER env var.
> Dave Steele hat am 22.06.2020 20:29 geschrieben:
>
> If I can interpret, it sounds like there are two options on the table -
> something looking like
> https://salsa.debian.org/reportbug-team/reportbug/-/merge_requests/24,
> or a reportbug-ng port. The MR needs, at a minimum, elimination
On Mon, Jun 22, 2020 at 9:27 AM Paul Wise wrote:
>
> On Mon, 2020-06-22 at 12:31 +0200, Nis Martensen wrote:
>
> > The current MUA support in reportbug has two main limitations:
>
> Just importing the MUA handling from reportbug-ng would solve most of
> these, including the gmail case. Preferably
On Mon, 2020-06-22 at 12:31 +0200, Nis Martensen wrote:
> The current MUA support in reportbug has two main limitations:
Just importing the MUA handling from reportbug-ng would solve most of
these, including the gmail case. Preferably the MUA handling
from reportbug-ng and reportbug should be
David Steele wrote:
> chaica wrote:
> > Allowing custom muas outside supported muas exclude the possibility to give
> > feedback to the user about what happened *after* reportbug gave the bug
> > report to the mua. How can reportbug know if your script/custom software is
> > available on your
Hey David,
On Sat, Jun 24, 2017 at 4:15 PM David Steele wrote:
> The "mua" option allowed a custom mua command to be defined, but it
> was only permitted for the list of 5 supported muas. This patch allows
> an arbitrary mua command string to be defined.
>
> The defined mua is set to default,
Package: reportbug
Version: 7.1.7
Severity: normal
Tags: patch
Dear Maintainer,
The "mua" option allowed a custom mua command to be defined, but it
was only permitted for the list of 5 supported muas. This patch allows
an arbitrary mua command string to be defined.
The defined mua is set to
7 matches
Mail list logo
