Bug#532150: Bug#865792: reportbug: Allow an arbitrary MUA to be configured (patch)

2020-06-24 Thread Nis Martensen
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.

Bug#532150: Bug#865792: reportbug: Allow an arbitrary MUA to be configured (patch)

2020-06-23 Thread Nis Martensen
> 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

Bug#532150: Bug#865792: reportbug: Allow an arbitrary MUA to be configured (patch)

2020-06-22 Thread Dave Steele
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

Bug#532150: Bug#865792: reportbug: Allow an arbitrary MUA to be configured (patch)

2020-06-22 Thread Paul Wise
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

Bug#532150: Bug#865792: reportbug: Allow an arbitrary MUA to be configured (patch)

2020-06-22 Thread Nis Martensen
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