I had issues building Ruby as I was using git 2.30.
The error was:
> file2lastrev.rb: git rev-parse failed error: could not expand
> include path '~/.gitcinclude'
The default system git config includes paths making use of `$HOME`,
but that env variable gets removed when building: 7070b1b196/tool/lib/vcs.rb (L546-L547)
It works with git `>= 2.32` thanks to the `GIT_CONFIG_SYSTEM`
feature which gets set to a Null IO in order to override
the system gitconfig. 7070b1b196/tool/lib/vcs.rb (L549)
Lots of documentation examples still use encoding APIs with encoding names
rather than encoding constants. I think it would be preferable to direct
users toward constants as it can help with auto-completion, static analysis
and such.
* Migrate standard library doc page to markdown
* Improve libraries listing and link to source code
* Fix grammar and improve phrasing
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
The inspect format was intentionally changed as an outcome of
[Bug #20433] [ruby-core:118668], but some documentation update
was missing, as [Bug #20962] pointed out. Update some output
examples that clearly use Hash#inspect.
* Add back summary table for pack/unpack directives
* This concise summary is very helpful e.g. to find the right Integer
directive, and is much better at getting an overview than very long text.
* From https://github.com/ruby/ruby/pull/6567
* I merged the tables for Array#pack and String#unpack,
there were almost the same except for String and Misc. directives.
* Tune up the tabular data and moves it to the top.
Co-authored-by: Burdette Lamar <BurdetteLamar@Yahoo.com>
Co-authored-by: Stan Lo <stan001212@gmail.com>
* Clarify “Building Ruby” docs
* Fix test examples to work from `build` dir
* Clarify “Testing Ruby” examples with real examples
All the commands should run correctly by default, without the user needing to modify them. This builds confidence that the relative paths are working correct from within the `build` directory.
Also, let’s use a consistent example throughout, for greater clarity.
* Improve examples to use `-v` flag in-context
This shows the correct way to combine `-v` with another parameter, e.g. a specific file to test.
* Other readability improvements
* Clarify `make` implementation support
* Fix WASM bullet/code indentation
* Use `console` code highlighting where appropriate
… which handles the prefix `$` correctly.
* Migrate feature proposal template to MarkDown
* Set language on code blocks
This reverts commit 743a31d639d4c96827b1b17f59c829c1ec31abc3,
"[ruby/date] [DOC] Make document coverage 100%". This file is only
for rdoc coverage in the date gem, and useless when the built-in Time
is documented.
