From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Searching bugs before filing new ones (was: Re: bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column)
Date: Thu, 18 Nov 2010 08:48:18 +0100 [thread overview]
Message-ID: <201011180848.18858.tassilo@member.fsf.org> (raw)
In-Reply-To: <l9y68r68lz.fsf@fencepost.gnu.org>
On Wednesday 17 November 2010 20:41:28 Glenn Morris wrote:
Hi Glenn,
> May I suggest searching for subject keywords before filing a bug? Or
> looking at the N newest bugs.
Yes, you may, but as long as checking related/duplicate bugs is not a
part of the usual bug filing procedure (aka M-x report-emacs-bug), it
won't have an effect, I guess.
It would be great if M-x report-emacs-bug would query for "Bug keywords"
first (e.g., tty cursor column), then somehow query the bug database and
show a buffer with possibly related bug subjects including links to the
bugtracker. Then a user should be able to either say "nope, I have a
different bug" and file a new one, or attach to one of the listed bugs.
I don't know if debbugs has some interface for querying the database, or
a better output format than the result html page. But even that doesn't
look awfully hard to parse to rip out the link to the bug and its
subject...
Bye,
Tassilo
next prev parent reply other threads:[~2010-11-18 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 10:59 bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column Gregor Zattler
2010-11-17 12:17 ` Eli Zaretskii
2010-11-17 16:35 ` Gregor Zattler
2010-11-17 19:28 ` Eli Zaretskii
2010-11-17 19:41 ` Glenn Morris
2010-11-18 7:48 ` Tassilo Horn [this message]
2010-11-18 8:19 ` Searching bugs before filing new ones Glenn Morris
2010-11-18 10:14 ` Searching bugs before filing new ones (was: Re: bug#7419: 24.0.50; emacs -Q -nw positions cursor in empty lines on the second column) Eli Zaretskii
2010-11-18 16:40 ` Andrew W. Nosenko
2010-11-18 18:19 ` Stephen J. Turnbull
2010-11-18 21:22 ` Searching bugs before filing new ones Glenn Morris
2010-11-18 22:20 ` Stefan Monnier
2010-11-19 11:51 ` tomas
2010-11-19 20:29 ` Glenn Morris
2010-11-21 20:10 ` tomas
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=201011180848.18858.tassilo@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.