Your message dated Tue, 16 Aug 2011 01:45:45 +0200
with message-id
<CAPdtAj1SBQs=iegxsqqrr-_ux2tfft5ki6gbbkc1tjb0dts...@mail.gmail.com>
and subject line Re: Bug#620928: reportbug: Please provide an option to not
prompt for a subject
has caused the Debian Bug report #620928,
regarding reportbug: Please provide an option to not prompt for a subject
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
620928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620928
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 5.0
Severity: wishlist
I'd much rather edit the mail subject in my editor, rather than in a
prompt provided by reportbug. (This holds particularly true when using
--mutt.) Thus, I'd like an option to disable the prompt for a subject.
If set, reportbug should still automatically set the subject for
replies, or prefix the filename or package name for new bugs, but should
not prompt for a subject.
- Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages reportbug depends on:
ii apt 0.8.13.1 Advanced front-end for dpkg
ii python 2.6.6-12 interactive high-level object-orie
ii python-reportbug 5.0 Python modules for interacting wit
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn debconf-utils <none> (no description available)
ii debsums 2.0.48+nmu3 tool for verification of installed
pn dlocate <none> (no description available)
ii emacs23-bin-common 23.2+1-7 The GNU Emacs editor's shared, arc
ii file 5.04-5 Determines file type using "magic"
ii gnupg 1.4.11-3 GNU privacy guard - a free PGP rep
pn postfix | exim4 | mail-trans <none> (no description available)
ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge
pn python-gtkspell <none> (no description available)
pn python-urwid <none> (no description available)
pn python-vte <none> (no description available)
ii xdg-utils 1.1.0~rc1-2 desktop integration utilities from
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 620928 +wontfix
thanks
Hi John,
On Thu, May 12, 2011 at 05:03, Josh Triplett <[email protected]> wrote:
> On Wed, May 11, 2011 at 10:31:46PM +0200, Sandro Tosi wrote:
>> On Tue, Apr 5, 2011 at 06:16, Josh Triplett <[email protected]> wrote:
>> > I'd much rather edit the mail subject in my editor, rather than in a
>> > prompt provided by reportbug. (This holds particularly true when using
>> > --mutt.)
>>
>> Could you please explain what's the difference between setting the
>> subject in mutt than at a prompt by reportbug. As of now, your
>> justifications are weak, so before closing the bug I'd like to be more
>> sure about your usecase.
>
> I have mutt configured to not prompt for a subject or any other headers;
> it just drops me directly into an editor, and includes the mail headers
> in the editor, so I can edit the subject along with the mail. ("set
> autoedit=yes" and "set edit_headers=yes"). If I could configure
> reportbug to skip the prompt for a Subject, and just silently fire up
> mutt with the default subject or subject prefix ("Re: $existing_subject"
> or "$package_name: ") then I'd end up directly in vim, editing the bug
> with the default subject already present and editable.
>
> Right now, I frequently end up just typing "foo" at the reportbug
> subject prompt, so that I can get to my editor, write the report, and
> come up with an appropriate subject after writing some or all of the
> body of the report. :)
I can see your workflow, but to please you there's a high risk of a
falback of a lot of bug reports without a subject. I'd have to reject
this feature.
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
