From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: [gnu.org #194297] Re: Emacs-devel list IS slow
Date: Tue, 01 Jun 2004 10:57:16 -0400 [thread overview]
Message-ID: <E1BVAhY-0006on-Fp@fencepost.gnu.org> (raw)
In-Reply-To: <87hdtwsocu.fsf@mail.jurta.org> (message from Juri Linkov on Mon, 31 May 2004 16:44:17 +0300)
Searching for "emacs" and not finding it is much better than if
you were searching for "emacs" and found vi instead. Unfortunately,
this is what Google does now. If you search for emacs by
http://www.google.com/search?q=best+emacs&cat=gwd%2FTop
then Google returns results with the first link pointing to Vi editor :-(
Is there any procedure for reporting such errors to Google?
(I have no idea.) If there is, could someone do it?
>> - A simple search for "emacs" on savannah.gnu.org no longer finds GNU Emacs
>>
>> http://savannah.gnu.org/search/?words=emacs&type_of_search=soft&Search=Search&exact=1
>
> This was a false alarm -- I see it now. Sorry for the noise.
>
> However, if I search for "GNU emacs", it doesn't show up.
I will report that to the Savannah people.
next prev parent reply other threads:[~2004-06-01 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rt-194297@gnu.org>
2004-05-29 17:49 ` [gnu.org #194297] Re: Emacs-devel list IS slow Paul Fisher via RT
2004-05-30 6:03 ` Eli Zaretskii
2004-05-30 23:05 ` Kim F. Storm
2004-05-30 23:12 ` Kim F. Storm
2004-05-31 13:44 ` Juri Linkov
2004-06-01 14:57 ` Richard Stallman [this message]
2004-06-01 16:40 ` Lawrence Mitchell
2004-06-01 20:57 ` Juri Linkov
2004-06-02 17:37 ` Richard Stallman
2004-05-30 5:02 ` eliz via RT
2004-05-30 23:07 ` (Kim F. Storm) via RT
2004-05-30 23:13 ` (Kim F. Storm) via RT
2004-05-30 23:31 ` Paul Fisher via RT
2004-05-31 6:40 ` Eli Zaretskii
2004-05-31 5:39 ` eliz via RT
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1BVAhY-0006on-Fp@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).