From: Eli Zaretskii <eliz@gnu.org>
To: myglc2 <myglc2@gmail.com>
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 17:18:39 +0200 [thread overview]
Message-ID: <837euslwhc.fsf@gnu.org> (raw)
In-Reply-To: <86h8txpy47.fsf@gmail.com> (message from myglc2 on Mon, 13 Nov 2017 18:17:28 -0500)
> 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.
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 you are advised to try the above
search engine before concluding that a bug for some issue doesn't
exist.
next prev parent reply other threads:[~2017-11-14 15:18 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 [this message]
2017-11-14 17:42 ` myglc2
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=837euslwhc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29290@debbugs.gnu.org \
--cc=myglc2@gmail.com \
/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.