diff options
author | Victor Shepelev <[email protected]> | 2023-12-09 06:54:33 +0200 |
---|---|---|
committer | GitHub <[email protected]> | 2023-12-09 13:54:33 +0900 |
commit | 07734b51c66756c4a7a512ebb4736763542d99f3 (patch) | |
tree | 3f60a9035ba9ee2538ef5d6eb7f40ac232c67261 /error.c | |
parent | 1cbe114d1cf57dc47b4bbc6780f424647dd906d9 (diff) |
[DOC] Small fixes for documentation rendering
Mostly just fixing RDoc's incorrect treatment of `+`
Diffstat (limited to 'error.c')
-rw-r--r-- | error.c | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -291,11 +291,11 @@ rb_warning_s_warn(int argc, VALUE *argv, VALUE mod) * * Changing the behavior of Warning.warn is useful to customize how warnings are * handled by Ruby, for instance by filtering some warnings, and/or outputting - * warnings somewhere other than $stderr. + * warnings somewhere other than <tt>$stderr</tt>. * * If you want to change the behavior of Warning.warn you should use - * +Warning.extend(MyNewModuleWithWarnMethod)+ and you can use `super` - * to get the default behavior of printing the warning to $stderr. + * <tt>Warning.extend(MyNewModuleWithWarnMethod)</tt> and you can use +super+ + * to get the default behavior of printing the warning to <tt>$stderr</tt>. * * Example: * module MyWarningFilter @@ -312,7 +312,7 @@ rb_warning_s_warn(int argc, VALUE *argv, VALUE mod) * You should never redefine Warning#warn (the instance method), as that will * then no longer provide a way to use the default behavior. * - * The +warning+ gem provides convenient ways to customize Warning.warn. + * The warning[https://rubygems.org/gems/warning] gem provides convenient ways to customize Warning.warn. */ static VALUE |