all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29290@debbugs.gnu.org
Subject: bug#29290: 25.3; bug-gnu-emacs archive web search fails to find matching bugs
Date: Tue, 14 Nov 2017 12:42:36 -0500	[thread overview]
Message-ID: <86d14kpxir.fsf@gmail.com> (raw)
In-Reply-To: <837euslwhc.fsf@gnu.org>


On 11/14/2017 at 15:18 Eli Zaretskii writes:

>> From: myglc2 <myglc2@gmail.com>
>> Date: Mon, 13 Nov 2017 18:17:28 -0500
>>
>> To see an example, search bug-gnu-emacs for 'server-name', e.g.,
>>
>> http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=server-name&submit=Search%21&idxname=bug-gnu-emacs&max=20&result=normal&sort=score
>>
>> This gives 20 hits non of which is ...
>>
>> https://debbugs.gnu.org/23576
>> [documentation] ‘Using Emacs as a Server’: ‘M-x set-variable RET
>> server-name RET foo RET’

> My suggestion is to use the search engine of the bug tracker, at
>
>   https://debbugs.gnu.org/cgi/search.cgi
>
> It is more sophisticated and does find the above bug report.

I tried the link above. It takes an unnatural amount of effort to find
the bug between the garbled titles and summary lines.

> The reasons why the mailman search didn't find the report could be a
> few.  One of them could be the way the Subject line was formatted
> (download the bug report in mbox format and see for yourself).  Or it
> could be some other snafu.

But aren't you alarmed it works so poorly?

> But you are advised to try the above
> search engine before concluding that a bug for some issue doesn't
> exist.

Sorry, I didn't see that. Where is this advised?

'M-x report-emacs-bug' mentions debbugs.gnu.org but does not provide any
specific advice.

The first google hit for "emacs bug" is https://debbugs.gnu.org

So, OK, both put you on debbugs.gnu.org. Now if you search the page for
"emacs" ...

... the first hit is the aforementioned mailman search ;-(

... the second hit is

https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs;max-bugs=100;base-order=1;bug-rev=1

... which I can't get to find the bug ;-(

So, bottom line,

1) if you _don't want_ people to go to mailman search please _remove the
   1st link_ on debbugs.gnu.org

2) if you want people to go to the search link you gave me, please _edit
   the 2nd link_ debbugs.gnu.org

3) If you want average users to use
   https://debbugs.gnu.org/cgi/search.cgi to pre-chew bug reports please
   to improve its usability.





  reply	other threads:[~2017-11-14 17:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RT-Ticket-1252961@rt.gnu.org>
2017-11-13 23:17 ` bug#29290: 25.3; bug-gnu-emacs archive web search fails to find matching bugs myglc2
2017-11-13 23:45   ` Glenn Morris
2017-11-14  0:12     ` myglc2
2017-11-14 21:15       ` Bob Proulx
2017-11-14 22:02         ` Ian Kelling
2017-11-14 22:30           ` Glenn Morris
2017-11-30 17:15       ` bug#29290: [gnu.org #1252961] " Ian Kelling via RT
2017-11-14 15:18   ` Eli Zaretskii
2017-11-14 17:42     ` myglc2 [this message]
2017-11-14 18:53       ` Eli Zaretskii
2017-11-14 20:41         ` myglc2
2017-11-15  3:34           ` Eli Zaretskii
2017-11-15 11:47             ` Noam Postavsky
2017-11-15 17:44               ` Eli Zaretskii

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=86d14kpxir.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=29290@debbugs.gnu.org \
    --cc=eliz@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.