| Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/logger/commit/c4a4155ab7
|
|
Enable `-Werror=implicit-function-declaration` by default for
building C extensions for early failures.
|
|
- `www.ruby-lang.org` links to `./www.ruby-lang.org`
- `cgi['field_name']` links to `./'field_name'`
|
|
Properly set the name of `File::Constants`, which is the only name
with a namespace in `RDoc::KNOWN_CLASSES`, and fixes longstanding bug
that `File::Constants` becomes `File::File::Constants`.
When it is generated by `rb_file_const` in dir.c, `name` is set to the
qualified name as same as `full_name`, and generated in the normal way
in file.c later, already set `full_name` is cleared and `name` will be
constructed from the enclosing namespace and the `name`. It will
results in duplicated namespace, `File::File::Constants`.
https://github.com/ruby/rdoc/commit/3a8d6df562
|
|
https://github.com/rubygems/rubygems/commit/3e06a91435
|
|
Other code must not be between the doc and class definition.
https://github.com/rubygems/rubygems/commit/366784aae5
|
|
See
https://docs.github.com/es/actions/learn-github-actions/environment-variables#default-environment-variables.
So that we can show stats about it at https://ecosystem.rubytogether.org
https://github.com/rubygems/rubygems/commit/48d6dc68f8
|
|
If this is at the top level, it stops the documentation of the
entire module, but not only the part in this file.
https://github.com/rubygems/rubygems/commit/34e8c1ee06
|
|
The note
> Raises an ArgumentError if the given +orig+ is immutable, such as Symbol,
> Integer, or Float.
has not been true since #2313 (GH-2313, Feature #16035) when
@casperisfine enabled storing non-finalizable objects in the underlying
`ObjectSpace::WeakMap`.
On Ruby 2.7+, `WeakRef.new(1) + 1` works fine and the result is the
expected 2.
Notes:
Merged: https://github.com/ruby/ruby/pull/5657
|
|
|
|
https://github.com/ruby/rdoc/commit/6bb93001db
|
|
https://github.com/ruby/rdoc/commit/4c7c46fcc4
|
|
If this is at the top level, it stops the documentation of the
entire module, but not only the part in this file.
https://github.com/ruby/forwardable/commit/34cd2ac4a1
|
|
If this is at the top level, it stops the documentation of the
entire module, but not only the part in this file.
https://github.com/ruby/irb/commit/86c41b06ad
|
|
https://github.com/ruby/rdoc/commit/acb91ea74a
|
|
https://github.com/ruby/rdoc/commit/23e61a208e
|
|
|
|
This change makes the sidebar scrollable via `position: sticky` and `overflow: auto`;
See also <https://caniuse.com/?search=sticky>
https://github.com/ruby/rdoc/commit/4d52e24840
|
|
For example, consider the following markup:
C1#m(a, b)
Before this patch, it generated this HTML:
<p><a href=\"C1.html#method-i-m\"><code>C1#m</code></a>(a, b)</p>
Which places the method arguments outside of the link.
Now it generates this HTML:
<a href=\"C1.html#method-i-m\"><code>C1#m(a, b)</code></a>
https://github.com/ruby/rdoc/commit/05a2b2222b
|
|
is missing
When I run bundle install with BUNDLE_DEPLOYMENT=true in the environment
on a different platform than I usually do development, I get the
following output to the console (wrapped exactly as shown):
Your bundle only supports platforms ["x86_64-darwin-19"] but your local platform
is x86_64-linux. Add the current platform to the lockfile with `bundle lock
--add-platform x86_64-linux` and try again.
Because the way the message wraps, its not as simple as copying the
suggested command to the clipboard because it contains a newline:
$ bundle lock
Writing lockfile to [...]/Gemfile.lock
$ --add-platform x86_64-linux
Adding a newline right before the command forces the command in the
error message to be on the same line, which facilitates copy-pasting the
command in the message.
https://github.com/rubygems/rubygems/commit/4cf6989b11
|
|
(https://github.com/ruby/ostruct/pull/39)
This gem exposes no executables.
https://github.com/ruby/ostruct/commit/a1242f7ebe
|
|
https://github.com/ruby/ostruct/commit/322efd0e61
|
|
https://github.com/ruby/ostruct/commit/7258535073
|
|
Reduce the number of steps required to install a gem from two steps to one by using `bundle add`
https://github.com/rubygems/rubygems/commit/2c968420cd
|
|
consistent
Previously they had slightly different behavior when combined with
conservative updating flags.
The correct behavior is the `--update-strict` option, so `--script` now
does that, The `--update-strict` option is left there for now but I will
deprecate it later.
https://github.com/rubygems/rubygems/commit/ab42046229
|
|
https://github.com/ruby/cgi/commit/734dfdf1b4
|
|
https://github.com/ruby/rdoc/commit/135198a31c
|
|
https://github.com/ruby/securerandom/commit/62ca2828f3
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5606
|
|
The existing implementation, given the below .inputrc, erroneously
creates a "C-v" key binding:
set keymap emacs-ctlx
"\C-v": "[C-x C-v was pressed]"
This fixes it to instead create a "C-x C-v" keybinding.
https://github.com/ruby/reline/commit/719f52d231
|
|
RDoc is using only CGI.escape, escapeHTML, and unescape.
We don't have to load the whole source code of cgi gem.
https://github.com/ruby/rdoc/commit/d096222cc2
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5563
|
|
Random.urandom raises a RuntimeError if it is unavailable.
[Bug #13885]
Notes:
Merged: https://github.com/ruby/ruby/pull/5557
|
|
So that the generated `.rdoc_options` file is loadable.
https://github.com/ruby/rdoc/commit/6cf6e1647b
|
|
|
|
(https://github.com/ruby/rdoc/pull/821)
This patch makes sure we only load relative code. Hence when coding or
testing rdoc, we'll be sure to always be using the correct code.
Discussion started at https://github.com/ruby/rdoc/pull/817.
Signed-off-by: Ulysse Buonomo <buonomo.ulysse@gmail.com>
https://github.com/ruby/rdoc/commit/aa41bd48eb
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
look-ahead rule
This improves the performance in some cases.
`rdoc .../gems/sinatra-2.1.0/README.md` takes 10.5 sec. before this
change, and 7.1 sec. after this change.
`make rdoc` of ruby/ruby takes 19.3 sec. before this change, 18.1 sec.
after this change.
https://github.com/ruby/rdoc/commit/7cf8281e3e
|
|
https://github.com/rubygems/rubygems/commit/666f3cc724
|
|
sources
https://github.com/rubygems/rubygems/commit/9712262d90
|
|
|
|
https://github.com/ruby/ipaddr/commit/6edf6ee6c3
|
|
https://github.com/ruby/ipaddr/commit/77fe1fca0a
|
|
Before it would be left as an IPv6 mask causing `to_range` to fail.
```
>> IPAddr.new("::2").native.to_range
/opt/rubies/3.0.3/lib/ruby/3.0.0/ipaddr.rb:479:in `set': invalid address (IPAddr::InvalidAddressError)
```
https://github.com/ruby/ipaddr/commit/af485192f3
|
|
An almost universal convention for gems is to expose Namespace::VERSION
which makes it much easier when debugging etc.
https://github.com/ruby/ipaddr/commit/587ae6996e
|
|
https://github.com/rubygems/rubygems/commit/bc69d19097
|
|
https://github.com/ruby/rdoc/commit/45e33c4b85
|
|
https://github.com/ruby/rdoc/commit/63fac51198
|
|
https://github.com/ruby/rdoc/commit/69cafb213a
|