From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: myglc2@gmail.com, 29290@debbugs.gnu.org
Subject: bug#29290: 25.3; bug-gnu-emacs archive web search fails to find matching bugs
Date: Wed, 15 Nov 2017 19:44:44 +0200 [thread overview]
Message-ID: <83bmk3jv1v.fsf@gnu.org> (raw)
In-Reply-To: <87vaib2281.fsf@users.sourceforge.net> (message from Noam Postavsky on Wed, 15 Nov 2017 06:47:10 -0500)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Cc: myglc2 <myglc2@gmail.com>, 29290@debbugs.gnu.org
> Date: Wed, 15 Nov 2017 06:47:10 -0500
>
> >> #23576: Re: bug#23576: [documentation] =?utf-8?Q?=E2=80=98Using?= Emacs
> >
> > That's not "garbled", that's the RFC 2047 encoded subject line, as
> > originally produced by the MUA of the person who reported the bug.
>
> It's not very human friendly though. There's also some mojibake from
> the fancy quotes:
>
> one a unique “server nameâ€
Two more reasons not to use curly quotes in email, I guess.
> PS I would find that search much more usable if it coalesced matches to
> the same bug; as it is, you typically have to scroll past a lot of
> repeats for long bug threads.
You are assuming people look for bugs, but that doesn't have to be the
case. They could look for something mentioned tangentially, or just
in part of the bug discussion.
prev parent reply other threads:[~2017-11-15 17:44 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
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 [this message]
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=83bmk3jv1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29290@debbugs.gnu.org \
--cc=myglc2@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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.