From: "masterleep2 (Bill Lipa) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "masterleep2 (Bill Lipa)" <noreply@ruby-lang.org>
Subject: [ruby-core:119121] [Ruby master Bug#20722] curious search result order on docs.ruby-lang.org
Date: Wed, 11 Sep 2024 05:07:40 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20722.20240911050748.52581@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20722.20240911050748.52581@ruby-lang.org>
Issue #20722 has been reported by masterleep2 (Bill Lipa).
----------------------------------------
Bug #20722: curious search result order on docs.ruby-lang.org
https://bugs.ruby-lang.org/issues/20722
* Author: masterleep2 (Bill Lipa)
* Status: Open
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
If you search for "String" on https://docs.ruby-lang.org/en/3.3/ the first four results returned are obscure:
1. Gem::SafeMarshal::Elements::String
2. Prism::StringFlags
3. Prism::StringNode
4. Reline::Terminfo::StringWithTiparm
5. String
Would it be possible to change it so that if one types an exact class name, the class of that name is first on the list? This would make it easier to use the search feature. More generally, the prioritization of these results is surprising.
Not sure if this is the right place to report a doc website issue. Apologies if not.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2024-09-11 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 5:07 masterleep2 (Bill Lipa) via ruby-core [this message]
2024-09-11 19:03 ` [ruby-core:119127] " p8 (Petrik de Heus) via ruby-core
2024-11-01 17:25 ` [ruby-core:119679] " masterleep2 (Bill Lipa) via ruby-core
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=redmine.issue-20722.20240911050748.52581@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@ruby-lang.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.
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 NNTP newsgroup(s).