* [ruby-core:119121] [Ruby master Bug#20722] curious search result order on docs.ruby-lang.org
@ 2024-09-11 5:07 masterleep2 (Bill Lipa) via ruby-core
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
0 siblings, 2 replies; 3+ messages in thread
From: masterleep2 (Bill Lipa) via ruby-core @ 2024-09-11 5:07 UTC (permalink / raw)
To: ruby-core; +Cc: masterleep2 (Bill Lipa)
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/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ruby-core:119127] [Ruby master Bug#20722] curious search result order on docs.ruby-lang.org
2024-09-11 5:07 [ruby-core:119121] [Ruby master Bug#20722] curious search result order on docs.ruby-lang.org masterleep2 (Bill Lipa) via ruby-core
@ 2024-09-11 19:03 ` p8 (Petrik de Heus) via ruby-core
2024-11-01 17:25 ` [ruby-core:119679] " masterleep2 (Bill Lipa) via ruby-core
1 sibling, 0 replies; 3+ messages in thread
From: p8 (Petrik de Heus) via ruby-core @ 2024-09-11 19:03 UTC (permalink / raw)
To: ruby-core; +Cc: p8 (Petrik de Heus)
Issue #20722 has been updated by p8 (Petrik de Heus).
You might have more luck reporting this at the RDoc repository:
https://github.com/ruby/rdoc
----------------------------------------
Bug #20722: curious search result order on docs.ruby-lang.org
https://bugs.ruby-lang.org/issues/20722#change-109720
* 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/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ruby-core:119679] [Ruby master Bug#20722] curious search result order on docs.ruby-lang.org
2024-09-11 5:07 [ruby-core:119121] [Ruby master Bug#20722] curious search result order on docs.ruby-lang.org masterleep2 (Bill Lipa) via ruby-core
2024-09-11 19:03 ` [ruby-core:119127] " p8 (Petrik de Heus) via ruby-core
@ 2024-11-01 17:25 ` masterleep2 (Bill Lipa) via ruby-core
1 sibling, 0 replies; 3+ messages in thread
From: masterleep2 (Bill Lipa) via ruby-core @ 2024-11-01 17:25 UTC (permalink / raw)
To: ruby-core; +Cc: masterleep2 (Bill Lipa)
Issue #20722 has been updated by masterleep2 (Bill Lipa).
I have reported it here:
https://github.com/ruby/rdoc/issues/1194
This one can probably be closed.
----------------------------------------
Bug #20722: curious search result order on docs.ruby-lang.org
https://bugs.ruby-lang.org/issues/20722#change-110339
* 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/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-11-01 17:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-09-11 5:07 [ruby-core:119121] [Ruby master Bug#20722] curious search result order on docs.ruby-lang.org masterleep2 (Bill Lipa) via ruby-core
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
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).