ruby_learner 1.0.0

data/questions/random_check/section_2/.rspec

@@ -0,0 +1 @@
+--require spec_helper

data/questions/random_check/section_2/lib/answer.rb

@@ -0,0 +1,17 @@
+# -*- coding: utf-8 -*-
+# section_2/answer.rb
+
+puts "please input country"
+country = gets.chomp
+
+def agreement(country)
+  if country == 'japan'
+    return 'こんにちは'
+  elsif country == 'us'
+    return 'hello'
+  else
+    return '???'
+  end
+end
+
+# agreement(country)

data/questions/random_check/section_2/lib/sentence.org

@@ -0,0 +1,12 @@
+#+STARTUP: indent nolineimages
+# section_1/sentence.org
+
+* if文の使い方
+- 条件分岐の基本ですよー
+
+* 問題文
+- 条件分岐で挨拶を作れ
+- japan >>> こんにちは
+- us >>> hello
+- その他 >>> ???
+- agreement(country)を用いて

data/questions/random_check/section_2/lib/workplace.rb

@@ -0,0 +1,5 @@
+# section_1/workplacs.rb
+
+def agreement(country)
+
+end

data/questions/random_check/section_2/spec/.rspec

@@ -0,0 +1 @@
+--require spec_helper

data/questions/random_check/section_2/spec/spec_helper.rb

@@ -0,0 +1,100 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = "doc"
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

data/questions/random_check/section_2/spec/workplace_spec.rb

@@ -0,0 +1,11 @@
+# -*- coding: utf-8 -*-
+require 'workplace'
+require 'spec_helper'
+RSpec.describe "A agreement" do
+  it "given 'japan', return 'こんにちは'" do
+    expect(agreement('japan')).to eq('こんにちは')
+  end
+  it "given 'italy', return '???'" do
+    expect(agreement('italy')).to eq('???')
+  end
+end

data/questions/sequential_check/section_1/part_1/lib/answer.rb

@@ -0,0 +1,9 @@
+# 1.1-for_system.rb
+
+def for_system(aaa, bbb)
+  answer = 0
+  bbb.each do
+    answer += aaa
+  end
+  answer
+end

data/questions/sequential_check/section_1/part_1/lib/sentence.org

@@ -0,0 +1,9 @@
+#+STARTUP: indent nolineimages
+# section_1/sentence.org
+
+* for文の使い方
+- 繰り返しの基本ですよー
+
+* 問題文
+- 繰り返し処理を用いて足し算してよ
+- for_system(a, b)を用いて

data/questions/sequential_check/section_1/part_1/lib/workplace.rb

@@ -0,0 +1,5 @@
+# section_1/workplacs.rb
+
+def for_system(a, b)
+
+end

data/questions/sequential_check/section_1/part_1/spec/spec_helper.rb

@@ -0,0 +1,100 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = "doc"
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

data/questions/sequential_check/section_1/part_1/spec/workplace_spec.rb

@@ -0,0 +1,10 @@
+require 'workplace.rb'
+
+RSpec.describe "A loop" do
+  it "given 2 and 2, return 6" do
+    expect(for_system(2, 2)).to eq(6)
+  end
+  it "given 3 and 3, return 8" do
+    expect(for_system(3, 2)).to eq(9)
+  end
+end

data/questions/sequential_check/section_1/part_2/lib/answer.rb

@@ -0,0 +1,16 @@
+# 1.2-agreement.rb
+
+puts "please input country"
+country = gets.chomp
+
+def agreement(country)
+  if country == 'japan'
+    return 'こんにちは'
+  elsif country == 'us'
+    return 'hello'
+  else
+    return '???'
+  end
+end
+
+# agreement(country)

data/questions/sequential_check/section_1/part_2/lib/sentence.org

@@ -0,0 +1,12 @@
+#+STARTUP: indent nolineimages
+# section_1/sentence.org
+
+* if文の使い方
+- 条件分岐の基本ですよー
+
+* 問題文
+- 条件分岐で挨拶を作れ
+- japan >>> こんにちは
+- us >>> hello
+- その他 >>> ???
+- agreement(country)を用いて

data/questions/sequential_check/section_1/part_2/lib/workplace.rb

@@ -0,0 +1,5 @@
+# section_1/workplacs.rb
+
+def agreement(country)
+
+end

data/questions/sequential_check/section_1/part_2/spec/.rspec

@@ -0,0 +1 @@
+--require spec_helper

data/questions/sequential_check/section_1/part_2/spec/spec_helper.rb

@@ -0,0 +1,100 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = "doc"
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

data/questions/sequential_check/section_1/part_2/spec/workplace_spec.rb

@@ -0,0 +1,11 @@
+# -*- coding: utf-8 -*-
+require 'workplace'
+require 'spec_helper'
+RSpec.describe "A agreement" do
+  it "given 'japan', return 'こんにちは'" do
+    expect(agreement('japan')).to eq('こんにちは')
+  end
+  it "given 'italy', return '???'" do
+    expect(agreement('italy')).to eq('???')
+  end
+end

data/ruby_learner.gemspec

@@ -0,0 +1,41 @@
+
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "ruby_learner/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "ruby_learner"
+  spec.version       = RubyLearner::VERSION
+  spec.authors       = ["Takaki Otsu"]
+  spec.email         = [""]
+
+  spec.summary       = %q{This helps to learn Ruby}
+  spec.description   = %q{This gem can give you knowledge about Ruby}
+  spec.homepage      = ""
+  spec.license       = "MIT"
+
+  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
+  # to allow pushing to a single host or delete this section to allow pushing to any host.
+  # if spec.respond_to?(:metadata)
+  #   spec.metadata["allowed_push_host"] = "TODO: Set to 'http://mygemserver.com'"
+  # else
+  #   raise "RubyGems 2.0 or newer is required to protect against " \
+  #     "public gem pushes."
+  # end
+
+  spec.files         = `git ls-files -z`.split("\x0").reject do |f|
+    f.match(%r{^(test|spec|features)/})
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.16"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
+  spec.add_dependency "thor"
+  spec.add_dependency "colorize"
+  spec.add_dependency "minitest", "~> 5.10.3"
+  spec.add_dependency "diff-lcs"
+  spec.add_dependency "rubocop", "~> 0.55.0"
+end

data/takahashi/docs/README.org

@@ -0,0 +1,139 @@
+
+* 卒業研究
+
+** Thema
+ editor_learner を基にした Ruby 習熟プログラム ruby_learner(仮) 開発
+
+ CUI ベースで動作するプログラム ruby の基本的な動作、規則、記法などを習得
+
+** 研究方針？
+ editor_learner の目的は emacs 上でのtype操作の習熟
+ ruby_learner(仮)の目的は ruby の習熟->一週間でrubyが扱える！
+
+# 「ruby の習熟」の定義？
+# 何を以って「ruby を習得した」とみなす？
+
+ たのしいRuby第５版を’実行しながら’読み込み、思ったことを全て羅列
+
+
+
+** 評価形式
+# editor_learner は時間計測により習熟度を評価
+# ruby_learner(仮)の評価形式は？
+
+
+
+2018/7/25
+
+** 結局何をするのか
+
+Ruby習熟のための問題作成。
+
+問題形式
+
+・出題に対する回答となるプログラムの記述
+・
+
+*** 大津君との連携
+
+私のやること
+
+・Ruby習熟のための問題作成
+・出題システム構成
+
+大津君のやること
+
+・”問題”の添削システム構成
+・rspecのtestを作成（red-green-refactaringのred-greenの部分）
+・abc_size_check機能（green-refactaringの部分）の実装
+
+** ゼミ
+
+githubでRuby_learnerのプロジェクトを立ち上げ
+
+以後進捗等適宜
+
+丸写しのテキストではなく、
+レジュメにすること。じぶんの「独自の」まとめを書く
+
+org-html-themes
+
+
+Ruby勉強ドリルを作るんだよ
+
+
+
+** 
+コードはテスト
+
+
+ruby_learner 起動方法
+1. rake build
+2. rake install:local
+3. ruby_learner [COMMAND]
+
+
+** 8/1 ゼミ
+
+「たのしいRuby1章の内容を完璧にできるプログラムの完成」
+
+見栄えの良いドリル（見辛い参考書で勉強する奴はいない
+
+たのしいRUbyはなぜ見栄えがいいのか？
+（少なくとも自分は読んでそう感じたはずで、ならばその理由があるはず
+
+
+文章校正
+
+rubocop
+
+それができてから次のことー＞応用、発展の習熟
+
+
+言語の修得
+・テキスト
+・リファレンス・マニュアル
+ー文法、関数の使い方等（必要な時に参照
+・逆引き
+ー何かをしたいー＞どう書くか
+・問題集
+
+たのしいRuby第５版に、「Rake」「正規表現」を用いた応用が含まれるか？
+含まれていないなら、第３版２３章を参考にする
+
+
+** 8/4 
+
+-番号はたのしいRuby準拠の仮置きなので、あとで入れ替えます
+
+-8_1 8_2は2_1より前に持ってくるかも
+
+-2_1.rbのrubocopの添削について
+
+#+begin
+> rubocop answer/2_1.rb 
+Inspecting 1 file
+C
+
+Offenses:
+
+answer/2_1.rb:1:1: C: Style/Encoding: Unnecessary utf-8 encoding comment.
+# -*- coding: utf-8 -*-
+^^^^^^^^^^^^^^^^^^^^^^^
+
+1 file inspected, 1 offense detected
+#+end
+
+文字コードの記述、rubocopは必要無いと言うけどemacsだと勝手に記述されてしまう
+解答例のコードに日本語入れない方が良い？
+
+-4_1.rbと4_2.rbは順番入れ替えます
+
+-8_2.rb 計算するためにint型に変換する必要あったので、別に変数用意して出力
+
+-9_3.rb else使わないならif使わない方がいいって意味なんだろうけど、代わりに何使うのか分からない
+
+*** 他入れておきたい問題
+
+-ARGVで受け取った文字列を数値に変換して表示するプログラム
+-正規表現を上手い具合に問題に落とし込みたい