From: shevegen@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92533] [Ruby trunk Bug#15819] cannot read document of File::NULL with "ri File::NULL"
Date: Fri, 03 May 2019 09:04:37 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-77893.20190503090436.e633f3cc9cb4b283@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15819.20190503045006@ruby-lang.org
Issue #15819 has been updated by shevegen (Robert A. Heiler).
> IHMO, it's too difficult to guess proper command.
Agree - File::NULL works in e. g. irb too and should work for ri. I found rdoc/ri
a bit cumbersome to use API-wise; in one project, that displays rdoc documentation
for methods (a bit similar as what pry does), I use code such as this:
hash = RDoc::RI::Driver.process_args(arguments)
rdoc_driver = RDoc::RI::Driver.new(hash)
To process stuff. if it were up to me I would try to enhance rdoc in general to be
more "friendly" (simpler) API-wise to use for downstream ruby users in general, but
I digress from your issue, sorry.
----------------------------------------
Bug #15819: cannot read document of File::NULL with "ri File::NULL"
https://bugs.ruby-lang.org/issues/15819#change-77893
* Author: tad (Tadashi Saito)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2019-05-03 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15819.20190503045006@ruby-lang.org>
2019-05-03 4:50 ` [ruby-core:92531] [Ruby trunk Bug#15819] cannot read document of File::NULL with ri File::NULL tad.a.digger
2019-05-03 4:58 ` [ruby-core:92532] [Ruby trunk Bug#15819] cannot read document of File::NULL with "ri File::NULL" tad.a.digger
2019-05-03 9:04 ` shevegen [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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-77893.20190503090436.e633f3cc9cb4b283@ruby-lang.org \
--to=ruby-core@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 read-only IMAP folder(s) and NNTP newsgroup(s).