Age | Commit message (Collapse) | Author |
|
Notes:
Merged-By: peterzhu2118 <peter@peterzhu.ca>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/7979
|
|
- Update mailing lists domain
- Use 'join' instead of an alias 'subscribe'.
- Command should be in subject instead of body.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/7462
|
|
versions of Ruby packages
|
|
|
|
|
|
|
|
|
|
|
|
`IRB_USE_AUTOCOMPLETE=false`
(https://github.com/ruby/irb/pull/469)
* Allow using IRB_USE_AUTOCOMPLETE=false to disable autocompletion
Currently, the only 2 ways to disable autocompletion are:
1. Create `.irbrc` and set `IRB.conf[:USE_AUTOCOMPLETE] = false`
2. Add the `--noautocomplete` flag when using the `irb` executable
Both of them are less convenient than setting a env var and are
lesser known to devs.
And given the number of problems the autocompletion has (see #445), I
think we should allow disabling it with a simple `IRB_USE_AUTOCOMPLETE=false`.
* Mention some env var configs in the README
|
|
sync_default_gems.rb sometimes syncs too much.
|
|
* Add edit command
* Make find_source a public singleton method
* Add document for the edit command
* Make find_end private
* Remove duplicated private
https://github.com/ruby/irb/commit/4321674aa7
Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>
|
|
(https://github.com/ruby/irb/pull/451)
* Document a full list of commands
* Document debug as well
* Make it less duplicated
|
|
|
|
This link is broken.
Notes:
Merged: https://github.com/ruby/ruby/pull/5989
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5904
|
|
co-authored-by: Peter Zhu <peter@peterzhu.ca>
co-authored-by: Stan Lo <stan001212@gmail.com>
Notes:
Merged: https://github.com/ruby/ruby/pull/5899
|
|
|
|
- Spaces before and after blocks.
- Single spaces after sentences everywhere
Signed-off-by: Tim Smith <tsmith@mondoo.com>
Notes:
Merged: https://github.com/ruby/ruby/pull/5816
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5806
|
|
It is disabled for the throughput of CI for now.
Notes:
Merged: https://github.com/ruby/ruby/pull/5243
|
|
Follow up for 6bca410ae8b16238d02c868ce8fa1af13a5c4460
[ci skip]
Notes:
Merged: https://github.com/ruby/ruby/pull/5215
|
|
This may break linking on GitHub, but it's more important for the
links to work in the documentation generated by rdoc.
Fixes [Bug #14743]
Notes:
Merged: https://github.com/ruby/ruby/pull/4958
|
|
|
|
|
|
reflect its current condition
|
|
|
|
|
|
|
|
|
|
|
|
Adding YJIT logo with a link to https://yjit.org
|
|
This change fixes some cases where YJIT fails to fire tracing events.
Most of the situations YJIT did not handle correctly involves enabling
tracing while running inside generated code.
A new operation to invalidate all generated code is added, which uses
patching to make generated code exit at the next VM instruction
boundary. A new routine called `jit_prepare_routine_call()` is
introduced to facilitate this and should be used when generating code
that could allocate, or could otherwise use `RB_VM_LOCK_ENTER()`.
The `c_return` event is fired in the middle of an instruction as opposed
to at an instruction boundary, so it requires special handling. C method
call return points are patched to go to a fucntion which does everything
the interpreter does, including firing the `c_return` event. The
generated code for C method calls normally does not fire the event.
Invalided code should not change after patching so the exits are not
clobbered. A new variable is introduced to track the region of code that
should not change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Yes, it's all very confusing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|