Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/rdoc/commit/3b3a583580
|
|
https://github.com/ruby/rdoc/commit/333952a62d
|
|
https://github.com/ruby/rdoc/commit/d263a2c9c4
|
|
https://github.com/ruby/rdoc/commit/1318048877
|
|
https://github.com/ruby/rdoc/commit/b16d3f1727
|
|
https://github.com/ruby/rdoc/commit/0cb3df713b
|
|
(https://github.com/ruby/rdoc/pull/927)
Because it's syntax error.
https://github.com/ruby/rdoc/commit/993f2532ff
|
|
https://github.com/ruby/ruby/commit/e4e054e3ce40 used four footnotes
without blank lines. And the ChangeLog generated from that commit
resulted in ``undefined method `parts' for nil`` error.
For now, let a footnote terminated by the next footnote mark.
Also refined the error message when undefined footnote is used.
https://github.com/ruby/rdoc/commit/a7f290130b
|
|
https://github.com/ruby/rdoc/commit/75eee668a5
|
|
Reported at https://github.com/ruby/rdoc/pull/907#discussion_r932505816
https://github.com/ruby/rdoc/commit/86384ac7f9
|
|
deduplicate_call_seq has a bug that skips call-seq for methods where the
alias is a prefix of the method name. For example, if the alias name is
"each" and the current method name is "each_line", then
deduplicate_call_seq will skip all call-seq for "each_line" since it
will believe that it is for the alias.
https://github.com/ruby/rdoc/commit/1148988ccc
|
|
https://github.com/ruby/rdoc/commit/aaeb5ce1ce
|
|
https://github.com/ruby/rdoc/commit/9f47234e0e
|
|
https://github.com/ruby/rdoc/commit/87301da71b
|
|
https://github.com/ruby/rdoc/commit/854b370763
|
|
Initialization depending on VM is separated.
https://github.com/ruby/rdoc/commit/030d10fccd
|
|
Currently only literal `0` and `1` are accepted as `read`/`write`
flags.
This patch allows other boolean arguments, C macros (`FALSE`/`TRUE`),
Ruby `VALUE`s (`Qfalse`/`Qtrue`), and C99 `bool`s (`false`/`true`), as
well.
https://github.com/ruby/rdoc/commit/169dc02e3c
|
|
https://github.com/ruby/rdoc/commit/fec1ab2e41
|
|
https://github.com/ruby/rdoc/commit/83051403d6
|
|
https://github.com/ruby/rdoc/commit/ce63794fde
|
|
Protected characters with `PROTECT_ATTR` should not have special
roles.
https://github.com/ruby/rdoc/commit/c318af0ea2
|
|
As underscores are masked to "protect" from the conversion, consider
also `PROTECT_ATTR` as a word character.
https://github.com/ruby/rdoc/commit/db58bb5170
|
|
Only valid characters for URLs should be used for generating URLs.
A list of valid characters can be found in sections 2.2 and 2.3 of IETF
RFC 3986 (https://www.ietf.org/rfc/rfc3986.txt).
https://github.com/ruby/rdoc/commit/2bd8fcdd4f
|
|
https://github.com/ruby/rdoc/commit/f9f90ef2ff
|
|
https://github.com/ruby/rdoc/commit/b7b4cdab6c
|
|
https://github.com/ruby/rdoc/commit/c870284163
|
|
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/ruby/rdoc/commit/4c7c46fcc4
|
|
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
|
|
https://github.com/ruby/rdoc/commit/a93e1bcd68
|
|
So that the generated `.rdoc_options` file is loadable.
https://github.com/ruby/rdoc/commit/6cf6e1647b
|
|
https://github.com/ruby/rdoc/commit/8166b84cf3
|
|
(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>
|
|
https://github.com/ruby/rdoc/commit/63fac51198
|
|
https://github.com/ruby/rdoc/commit/69cafb213a
|
|
https://github.com/ruby/rdoc/commit/17c0da304d
|
|
https://github.com/ruby/rdoc/commit/b6c6d4f978
|
|
https://github.com/ruby/rdoc/commit/52c33157f1
|
|
Make operator methods, e.g., `Regexp#=~`, `Integer#<=>`, cross
reference targets.
https://github.com/ruby/rdoc/commit/5d332a4128
|
|
Currently only `rb_struct_define_without_accessor` is supported by
https://github.com/ruby/rdoc/pull/73. We should support other
three functions too.
https://github.com/ruby/rdoc/commit/d42288f06c
|
|
https://github.com/ruby/rdoc/commit/23747b4950
|
|
https://github.com/ruby/rdoc/commit/1e16284fe5
|
|
https://github.com/ruby/rdoc/commit/8386333323
|
|
This change fixes alias call-seq to return nil if the method's
call-seq does not specify the alias.
Previously, the alias's call-seq would be an empty string in this case
which broke darkfish rendering.
This change also backfills test coverage for 0ead786 which moved
call-seq deduplication into AnyMethod.
https://github.com/ruby/rdoc/commit/5ce2789b6f
|
|
See related commits:
- ebc66662 for #===
- 4943d208 for #[], #[]=, #<<, and #>>
https://github.com/ruby/rdoc/commit/8e47f7840a
|
|
https://github.com/ruby/rdoc/commit/45c92005fe
|
|
Previously, Parser::C comments all defaulted to "rdoc" format, even
when the user had set a different default with the `--markup=<choice>`
option.
https://github.com/ruby/rdoc/commit/4643b08a26
|
|
https://github.com/ruby/rdoc/commit/3b8334a796
|
|
Leaked file descriptor: TestRDocGeneratorDarkfish#test_template_stylesheets: 11 : #<File:./tmp20210913-30865-7c4ey8/hoge20210913-30865-evm2uo.css>
|
|
https://github.com/ruby/rdoc/commit/3bca7dc093
|