summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)Author
2019-08-30Fix keyword argument separation issues in libJeremy Evans
Mostly requires adding ** in either calls or method definitions. Notes: Merged: https://github.com/ruby/ruby/pull/2395
2019-08-30Revert "require 'pp' before use PP"Kazuhiro NISHIYAMA
of lib/bundler/vendor/molinillo/lib/molinillo/resolution.rb. This reverts commit 500149709b92ccb36396589a0c39afb3ff77bfb6 partially.
2019-08-30Removed debug printNobuyoshi Nakada
It seems to be fixed by b870ca58791e576f5dbb263f54ae433a7f6d65ee.
2019-08-30Add guard as same as `==`Kazuhiro NISHIYAMA
Try to fix failure at https://github.com/ruby/ruby/runs/207580232#step:10:382 ``` undefined method `name' for "Gemfile.lock":String /home/runner/work/ruby/ruby/lib/bundler/resolver/spec_group.rb:65:in `eql?' ```
2019-08-30lib/pp.rb: Use UnboundMethod#bind_call instead of .bind(obj).call(...)Yusuke Endoh
Related to [Feature #15955].
2019-08-30require 'pp' before use PPKazuhiro NISHIYAMA
`Kernel#pp` has wrapper, but `PP` does not. https://github.com/ruby/ruby/runs/207405029#step:10:141 `NameError: uninitialized constant Bundler::Molinillo::Resolver::Resolution::PP`
2019-08-29Check events that console window size changed on Windowsaycabta
2019-08-29Fix alignment of a SHORT variableaycabta
typedef struct _COORD { SHORT X; SHORT Y; // I wanted to take this... } COORD, *PCOORD; typedef struct _CONSOLE_SCREEN_BUFFER_INFO { COORD dwSize; COORD dwCursorPosition; // ...of this one WORD wAttributes; // But it's combined with first 2bytes of this SMALL_RECT srWindow; COORD dwMaximumWindowSize; } CONSOLE_SCREEN_BUFFER_INFO; If wAttributes has non-zero value, the code breaks.
2019-08-29CONSOLE_SCREEN_BUFFER_INFO is 22bytesaycabta
typedef struct _CONSOLE_SCREEN_BUFFER_INFO { COORD dwSize; // 4(SHORT X, Y) COORD dwCursorPosition; // 4 WORD wAttributes; // 2 SMALL_RECT srWindow; // 8(SHORT Left, Top, Right, Bottom) COORD dwMaximumWindowSize; // 4 } CONSOLE_SCREEN_BUFFER_INFO;
2019-08-29Add stub set_screen_size for other platformsaycabta
2019-08-29Support SIGWINCHaycabta
2019-08-28Remove jquery.js from file list of rdoc.gemspecaycabta
2019-08-28Adjusted indents and supplied last commasNobuyoshi Nakada
Fixed unmatched indent of the closing bracket for `:irb_current_working_workspace`, and adjusted following elements.
2019-08-28Remove debug print [ci skip]Kazuhiro NISHIYAMA
2019-08-28Remove jquery.jsaycabta
2019-08-28Version 6.2.0aycabta
2019-08-28Good bye jQueryaycabta
2019-08-27Remove duplicated delegationaycabta
2019-08-27Delegete an instance method to a class method correctlyaycabta
2019-08-27Save value to @ambiguous_width because of a accessoraycabta
2019-08-27The "private" doesn't make sence for class methods and a constantaycabta
2019-08-27Use preposing "private" to define methodsaycabta
2019-08-27Adjust method forwardings of Relineaycabta
2019-08-27Remove .freeze.manga_osyo
2019-08-27Fix `Reline::Windows`.manga_osyo
2019-08-27Refactoring Reline.manga_osyo
2019-08-27Remove test_mode in `lib/reline`.manga_osyo
2019-08-27Refactoring Reline accessor.manga_osyo
2019-08-27Handle binding.irb for frozen objects and BasicObjects using a delegateJeremy Evans
Fixes Ruby Bug 13264
2019-08-27Move private call without arguments inside methodJeremy Evans
This code did not have the desired effect. I'm not sure if irb_binding is supposed to be private or not. If not, the private call can just be removed.
2019-08-25lib/webrick.rb: use require_relative for webrick/utils.rbYusuke Endoh
`require "webrick/utils.rb"` should load `lib/webrick/utils.rb`, but on some CI machines, it wrongly loads `test/webrick/utils.rb`, which caused circular require warning: https://rubyci.org/logs/rubyci.s3.amazonaws.com/ubuntu/ruby-master/log/20190825T093007Z.log.html.gz ``` /data/chkbuild/tmp/build/20190825T093007Z/ruby/lib/rubygems/core_ext/kernel_require.rb:61: warning: /data/chkbuild/tmp/build/20190825T093007Z/ruby/lib/rubygems/core_ext/kernel_require.rb:61: warning: loading in progress, circular require considered harmful - /data/chkbuild/tmp/build/20190825T093007Z/ruby/lib/webrick.rb ```
2019-08-22Always check multiline terminationaycabta
2019-08-21Add abs to Matrix (#2199)Fernando Wolf Bona
2019-08-22IRB's multiline history is enable only when Reidline modeaycabta
2019-08-21The investigation is going on...Nobuyoshi Nakada
2019-08-21[bundler/bundler] Remove old rubies stuff no longer neededDavid Rodríguez
https://github.com/bundler/bundler/commit/36fb3287f4
2019-08-20Avoid creating Hash objects per each mon_synchronize call (#2393)Akira Matsuda
Notes: Merged-By: amatsuda <ronnie@dio.jp>
2019-08-20[rubygems/rubygems] Use `RbConfig::CONFIG['rubylibprefix']`Nobuyoshi Nakada
It is defined since ruby 1.9.2. https://github.com/rubygems/rubygems/commit/84981ca908
2019-08-20Fix some bundler specs (#2380)David Rodríguez
* These seem to consistenly pass already * Show actual command when running `make test-bundler` Current the setup command that installs the necessary gems for testing bundler was printed, but not the actual command that runs the tests. That was a bit confusing. * Borrow trick from setproctitle specs * A title that long doesn't get set sometimes No idea why, but the test doesn't need that the title is that long. * Fix most gem helper spec ruby-core failures * Fix the rest of the gem helper failures * Fix version spec by improving the assertion * Remove unnecessary `BUNDLE_RUBY` environment var We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name because bundler considers `BUNDLE_*` variables as settings. * Rename `BUNDLE_GEM` to `GEM_COMMAND` This is more descriptive I think, and also friendlier for bundler because `BUNDLE_` env variables are interpreted by bundler as settings, and this is not a bundler setting. This fixes one bundler spec failure in config specs against ruby-core. * Fix quality spec when run in core Use the proper path helper. * Fix dummy lib builder to never load default gems If a dummy library is named as a default gem, when requiring the library from its executable, the default gem would be loaded when running from core, because in core all default gems share path with bundler, and thus they are always in the $LOAD_PATH. We fix the issue by loading lib relatively inside dummy lib executables. * More exact assertions Sometimes I have the problem that I do some "print debugging" inside specs, and suddently the spec passes. This happens when the assertion is too relaxed, and the things I print make it match, specially when they are simple strings like "1.0" than can be easily be part of gem paths that I print for debugging. I fix this by making a more exact assertion. * Detect the correct shebang when ENV["RUBY"] is set * Relax assertion So that the spec passes even if another paths containing "ext" are in the load path. This works to fix a ruby-core issue, but it's a better assertion in general. We just want to know that the extension path was added. * Use folder structure independent path helper It should fix this spec for ruby-core. * Fix the last failing spec on ruby-core * Skip `bundle open <default_gem>` spec when no default gems
2019-08-20Treat two types "do" correctlyaycabta
A "do" what has followed a token what has EXPR_CMDARG is for a block, and in other cases "do" is for "while", "until" or "for".
2019-08-19Update the canonical repository urlHiroshi SHIBATA
2019-08-19Prefer Regexp#=~ to Regexp#match when the RHS may be nilNobuyoshi Nakada
2019-08-19lib/rdoc/markup/parser.rb: remove a unused variable initializationYusuke Endoh
2019-08-18[bundler/bundler] No need to activate the `fileutils` default gemDavid Rodríguez
The version we're vendoring actually relaxed this restriction back to 2.3.0+, so we can always use the vendored version. https://github.com/bundler/bundler/commit/d366cbfe5d
2019-08-18[bundler/bundler] Last relative requiresDavid Rodríguez
https://github.com/bundler/bundler/commit/fb587b9ebb
2019-08-18[bundler/bundler] Move local variable to only branch where it's usedDavid Rodríguez
https://github.com/bundler/bundler/commit/3995b3345d
2019-08-18[bundler/bundler] Fix open default gem errorZehan Zhao
https://github.com/bundler/bundler/commit/792d724752
2019-08-18[bundler/bundler] Fix `bundle doctor` commandDavid Rodríguez
Previously `bundle doctor` would fail on any bundle that does not include git gems or plugins. This is because the previously used `Bundler.home` does not exist unless the bundle includes git gems or plugins. For example, with `bundle config set path .bundle`, it points to which does not exist unless this kind of gems exist in the Gemfile. The name `Bundler.home` is really unfortunate, it should probably be have more descriptive name, and be private. But for now I just want to make `bundle doctor` usable. https://github.com/bundler/bundler/commit/5531a18c1e
2019-08-18[bundler/bundler] Bundler displays a duplicate gem entries warning even if ↵David Stosik
gems only appear once per group https://github.com/bundler/bundler/commit/d18a83109e
2019-08-18The "exe" dir doesn't exist in this repostiroyaycabta
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-27 06:29:21 +0000