roebe 0.5.191 → 0.6.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a131bfe77e783074db388059a14ea1d5037e8d4c17902023575f1c56c33e13dc
-  data.tar.gz: aa0e3baec297cc14136f29f35f9231af91731f7f629702c8dfc3d266e46fadce
+  metadata.gz: 34c4a26f5398c7f87161b0277adbab0453229262790bad3057efd370de501144
+  data.tar.gz: bded795ea514ac1d525ec28c8dcb68f4b5dc1fc996d02526bbccf3a3eb702161
 SHA512:
-  metadata.gz: e1d7fc582dc0543e5136d803f8f8b43c5b8b6fbf036fa7c14ba2ec4fb51bd5558f19ab42ba52cf98f67c576499fe3d28e78eecc7c0bab46df08310f8adcbb11e
-  data.tar.gz: 22de8a6e62bb77fab48cad54b76d7b7417e65fa7077eae864605514c906c6f3cbd84581246fbf3ba86336265dc7a038ad0847ecc49fd5ea0f271d5da547de0af
+  metadata.gz: 67d16f6eabc5801c459f503feda415b098ad7cf68d8b3ac10f7113182a748ea05c01263c5002fa2b1ee6ce41a149d70669086b179c2dc0656fb640026a64f83e
+  data.tar.gz: 6412467df95da8c46101b046df6784b390f66dcbc1d9483e91a46e2c7cdd3b41dd949201aa017bb8ec4f41fa7a011f39654a77ce5d33dce72a745d8b2ec3000d

data/README.md

@@ -2,7 +2,7 @@
 [![forthebadge](https://forthebadge.com/images/badges/made-with-ruby.svg)](https://www.ruby-lang.org/en/)
 [![Gem Version](https://badge.fury.io/rb/roebe.svg)](https://badge.fury.io/rb/roebe)
 
-This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">31.01.2024</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">00:15:47</span> o'clock.
+This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">17.04.2024</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">20:42:27</span> o'clock.
 
 ## Introducing the Roebe project
 
@@ -50,41 +50,92 @@ project, called open, via the Open namespace, so that I can do:
     Open.in_browser(remote_URL_here)
     Open.in_editor('/tmp/foobar.md')
 
-Additionally, the Roebe project may serve as **an entry point to other
-gems**, thus tapping into the larger ruby gem ecosystem as a whole. This
+Additionally, the Roebe project may serve as <b>an entry point to other
+gems</b>, thus tapping into the larger ruby gem ecosystem as a whole. This
 is an important **side-goal** for this project, as it is, to word this
 differently, my main "jumping point" for ruby these days. If I need 
 specialized functionality, I tend to write some ruby code, put it into
 the roebe project, and then move on from there.
 
+## Policy in effect in regards to the roebe project
+
+The roebe-project is adjusted to my own use cases. This also means that
+other users of this gem may not find the project all that terribly
+useful, which is understandable.
+
+Yet, at the same time, this gem is also my most popular gem. I am not
+sure why that is the case, but perhaps other users found some of the
+code or content in this gem useful.
+
+Either way, no matter as to the underlying reason for this, I thought
+about how to make the roebe-gem more useful to other people. So, in
+April 2024 I decided to add a policy-directive to this gem, so that
+other users of this gem may understand how they could benefit from
+the project, as well as - even more importantly - <b>how to
+adjust the project to their own use cases</b>.
+
+I will try to adjust the code so that people can overrule behaviour
+that they may want to have via the commandline. Furthermore, hardcoded
+paths should be avoided, if possible; at the least some flexibility
+should be kept in mind with regard to the roebe-gem, where methods
+should be usable by other users, aiming to adjust the behaviour of
+the classes to their use cases.
+
+Let me try to explain the above rationale with a specific example -
+this may make it easier to understand the changed approach I will
+use past April 2024.
+
+In the past I had a GUI application called <b>contacts</b>. This
+file, unsurprisingly, contained contacts-information I would use.
+This information I kept in a spearate .yml file which I did not
+publish - after all that information is not useful to anyone else,
+but simply refers to my own use case here, and my own contacts
+file.
+
+But, for other people, they may want to use their own .yml file.
+So I needed to change the code to allow custom loading of 
+.yml files in general. I also decided to add support for a
+special ENV variable, so that people can simply use that
+variable to override any other value in the contacts.rb file.
+
+The file contacts.rb also comes with GUI code - the old 
+ruby-gtk3 code, libui-code as well as jruby-SWING bindings.
+
+Starting the gtk3 bindings, for instance, can be done via:
+
+   contacts --gtk3
+
+The long-term goal is to extend this to many more .rb files
+in the roebe project, when it makes sense to offer a GUI.
+
 ## General remarks about the Layout and Structure of the roebe project
 
-The **roebe-project** is fairly large. Most code can be found within
-the **classes/** subdirectory of the <b>roebe</b> gem, as well as the
-**toplevel_methods/** subdirectory of the <b>roebe</b> gem - so,
-**roebe/classes/** and **roebe/toplevel_methods/** are the two
+The <b>roebe-project</b> is fairly large. Most code can be found within
+the <b>classes/</b> subdirectory of the <b>roebe</b> gem, as well as the
+<b>toplevel_methods/</b> subdirectory of the <b>roebe</b> gem - so,
+<b>roebe/classes/</b> and <b>roebe/toplevel_methods/</b> are the two
 primary subdirectories of this gem.
 
-Following that, a few classes will be described **below this section**
-in this document (**README.md**) - but keep in mind that this is <b>not</b>
+Following that, a few classes will be described <b>below this section</b>
+in this document (<b>README.md</b>) - but keep in mind that this is <b>not</b>
 a "complete" documentation of all the available classes that are
 distributed in this gem. Only some of these classes
-will be described in this file here (**README.md**).
+will be described in this file here (<b>README.md</b>).
 
-**Before running any of the code, I recommend to you to have a
+<b>Before running any of the code, I recommend to you to have a
 look at the source code of the corresponding .rb file - that way
 you may be able to judge whether the functionality is desired
-by you or whether it may need any modifications.**
+by you or whether it may need any modifications.</b>
 
 Keep in mind that the functionality defaults to my own use case,
-which **may easily differ from your use case**. Some of these
+which <b>may easily differ from your use case</b>. Some of these
 classes have not been updated in years, so again: have a look
-at the source code before running **any** of these classes, in
+at the source code before running <b>any</b> of these classes, in
 particular for larger classes or classes that remove files or
-directories (you can grep for **delete** and **remove** to 
+directories (you can grep for <b>delete</b> and <b>remove</b> to 
 find these).
 
-Presently the **roebe-project** has only a **very few external
+Presently the <b>roebe-project</b> has only a **very few external
 dependencies** - but in theory, all external dependencies could be
 removed altogether. I like to make use of some external code,
 though, which is why most .rb files within this project require 
@@ -5752,6 +5803,18 @@ have to install the emoji_paradise gem, via:
 
     gem install emoji_paradise
 
+## Roebe.actions()
+
+Roebe.actions() was added in March 2024. The idea is that for every
+important (major) activity, related to the roebe gem, we bundle
+this through the method Roebe.actions().
+
+This thus constitutes a generic entry point, which in turn can then
+be used towards other entry points of other gems, without needing
+to require any specific .rb file or know the class-names of such
+files, as-is. We thus gain a <b>lot</b> more flexibility that
+way.
+
 ## Useful links, blogs, articles about the Ruby programming language
 
 This subsection contains some links that may possibly be useful to you when
@@ -5840,29 +5903,14 @@ gem owner eventually:
 see
 https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html
 
-Mandatory 2FA will eventually be extended to all rubygems.org developers and
-maintainers. As I can not use 2FA, for reasons I will skip explaining here,
-this means that my projects will eventually be removed, as I no longer
-have any control over my projects hosted on rubygems.org (because I
-can not use 2FA).
-
-At that point, I no longer have any control what is done to my projects
-since whoever is controlling the gems ecosystem took away our control
-here. I am not sure at which point ruby became corporate-controlled -
-that was not the case several years ago, so something has
-changed.
-
-Ruby also only allows 2FA users to participate on the issue tracker these
-days:
-
-  https://bugs.ruby-lang.org/issues/18800
-
-But this has been reverted some months ago, so it is no longer applicable.
-Suffice to say that I do not think that we should only be allowed to
-interact on the world wide web when some 'authority' authenticated us,
-such as via mandatory 2FA, so I hope this won't come back again.
-
-Fighting spam is a noble goal, but when it also means you lock out
-real human people then this is definitely NOT a good situation
-to be had.
+However had, that has been reverted again, so I decided to shorten
+this paragraph. Mandatory 2FA may exclude users who do not have a 
+smartphone device or other means to 'identify'. I do not feel it is
+a fair assumption by others to be made that non-identified people may
+not contribute code, which is why I reject it. Mandatory 2FA would mean
+an end to all my projects on rubygems.org, so let's hope it will never
+happen. (Keep in mind that I refer to mandatory 2FA; I have no qualms
+for people who use 2FA on their own, but this carrot-and-stick strategy
+by those who control the rubygems infrastructure is a very bad one to
+pursue.
 

data/bin/create_my_directories

@@ -2,6 +2,6 @@
 # Encoding: UTF-8
 # frozen_string_literal: true
 # =========================================================================== #
-require 'roebe/classes/create_my_directories.rb'
+require 'roebe/actions/actions.rb'
 
-Roebe::CreateMyDirectories.new(ARGV)
+Roebe.actions(:CreateMyDirectories, ARGV)

data/bin/{ruby_dhcpcd → dhcpcd_wrapper}

@@ -2,6 +2,6 @@
 # Encoding: UTF-8
 # frozen_string_literal: true
 # =========================================================================== #
-require 'roebe/classes/dhcpcd/dhcpcd.rb'
+require 'roebe/classes/dhcpcd/dhcpcd_wrapper.rb'
 
 Roebe.dhcpcd(ARGV)

data/bin/start_lighty

@@ -2,6 +2,6 @@
 # Encoding: UTF-8
 # frozen_string_literal: true
 # =========================================================================== #
-require 'roebe/toplevel_methods/lighttpd.rb'
+require 'roebe/requires/require_lighttpd.rb'
 
 Roebe.start_lighttpd

data/doc/README.gen

@@ -46,41 +46,92 @@ project, called open, via the Open namespace, so that I can do:
     Open.in_browser(remote_URL_here)
     Open.in_editor('/tmp/foobar.md')
 
-Additionally, the Roebe project may serve as **an entry point to other
-gems**, thus tapping into the larger ruby gem ecosystem as a whole. This
+Additionally, the Roebe project may serve as <b>an entry point to other
+gems</b>, thus tapping into the larger ruby gem ecosystem as a whole. This
 is an important **side-goal** for this project, as it is, to word this
 differently, my main "jumping point" for ruby these days. If I need 
 specialized functionality, I tend to write some ruby code, put it into
 the roebe project, and then move on from there.
 
+## Policy in effect in regards to the roebe project
+
+The roebe-project is adjusted to my own use cases. This also means that
+other users of this gem may not find the project all that terribly
+useful, which is understandable.
+
+Yet, at the same time, this gem is also my most popular gem. I am not
+sure why that is the case, but perhaps other users found some of the
+code or content in this gem useful.
+
+Either way, no matter as to the underlying reason for this, I thought
+about how to make the roebe-gem more useful to other people. So, in
+April 2024 I decided to add a policy-directive to this gem, so that
+other users of this gem may understand how they could benefit from
+the project, as well as - even more importantly - <b>how to
+adjust the project to their own use cases</b>.
+
+I will try to adjust the code so that people can overrule behaviour
+that they may want to have via the commandline. Furthermore, hardcoded
+paths should be avoided, if possible; at the least some flexibility
+should be kept in mind with regard to the roebe-gem, where methods
+should be usable by other users, aiming to adjust the behaviour of
+the classes to their use cases.
+
+Let me try to explain the above rationale with a specific example -
+this may make it easier to understand the changed approach I will
+use past April 2024.
+
+In the past I had a GUI application called <b>contacts</b>. This
+file, unsurprisingly, contained contacts-information I would use.
+This information I kept in a spearate .yml file which I did not
+publish - after all that information is not useful to anyone else,
+but simply refers to my own use case here, and my own contacts
+file.
+
+But, for other people, they may want to use their own .yml file.
+So I needed to change the code to allow custom loading of 
+.yml files in general. I also decided to add support for a
+special ENV variable, so that people can simply use that
+variable to override any other value in the contacts.rb file.
+
+The file contacts.rb also comes with GUI code - the old 
+ruby-gtk3 code, libui-code as well as jruby-SWING bindings.
+
+Starting the gtk3 bindings, for instance, can be done via:
+
+   contacts --gtk3
+
+The long-term goal is to extend this to many more .rb files
+in the roebe project, when it makes sense to offer a GUI.
+
 ## General remarks about the Layout and Structure of the roebe project
 
-The **roebe-project** is fairly large. Most code can be found within
-the **classes/** subdirectory of the <b>roebe</b> gem, as well as the
-**toplevel_methods/** subdirectory of the <b>roebe</b> gem - so,
-**roebe/classes/** and **roebe/toplevel_methods/** are the two
+The <b>roebe-project</b> is fairly large. Most code can be found within
+the <b>classes/</b> subdirectory of the <b>roebe</b> gem, as well as the
+<b>toplevel_methods/</b> subdirectory of the <b>roebe</b> gem - so,
+<b>roebe/classes/</b> and <b>roebe/toplevel_methods/</b> are the two
 primary subdirectories of this gem.
 
-Following that, a few classes will be described **below this section**
-in this document (**README.md**) - but keep in mind that this is <b>not</b>
+Following that, a few classes will be described <b>below this section</b>
+in this document (<b>README.md</b>) - but keep in mind that this is <b>not</b>
 a "complete" documentation of all the available classes that are
 distributed in this gem. Only some of these classes
-will be described in this file here (**README.md**).
+will be described in this file here (<b>README.md</b>).
 
-**Before running any of the code, I recommend to you to have a
+<b>Before running any of the code, I recommend to you to have a
 look at the source code of the corresponding .rb file - that way
 you may be able to judge whether the functionality is desired
-by you or whether it may need any modifications.**
+by you or whether it may need any modifications.</b>
 
 Keep in mind that the functionality defaults to my own use case,
-which **may easily differ from your use case**. Some of these
+which <b>may easily differ from your use case</b>. Some of these
 classes have not been updated in years, so again: have a look
-at the source code before running **any** of these classes, in
+at the source code before running <b>any</b> of these classes, in
 particular for larger classes or classes that remove files or
-directories (you can grep for **delete** and **remove** to 
+directories (you can grep for <b>delete</b> and <b>remove</b> to 
 find these).
 
-Presently the **roebe-project** has only a **very few external
+Presently the <b>roebe-project</b> has only a **very few external
 dependencies** - but in theory, all external dependencies could be
 removed altogether. I like to make use of some external code,
 though, which is why most .rb files within this project require 
@@ -5748,6 +5799,18 @@ have to install the emoji_paradise gem, via:
 
     gem install emoji_paradise
 
+## Roebe.actions()
+
+Roebe.actions() was added in March 2024. The idea is that for every
+important (major) activity, related to the roebe gem, we bundle
+this through the method Roebe.actions().
+
+This thus constitutes a generic entry point, which in turn can then
+be used towards other entry points of other gems, without needing
+to require any specific .rb file or know the class-names of such
+files, as-is. We thus gain a <b>lot</b> more flexibility that
+way.
+
 ## Useful links, blogs, articles about the Ruby programming language
 
 This subsection contains some links that may possibly be useful to you when

data/doc/core/array.md

@@ -1,3 +1,27 @@
+## How can we check whether something is included in an array or not? (inarray, is in array, in_array)
+
+    a = [ "a", "b", "c" ] #
+    a.include?("b") # true
+
+  If you want to do this for an object called x and the array y
+
+    y.member?(x)
+
+## I am used to perl's qw(). How to make this in ruby? Is there a shortcut for creating arrays? (quoted words)
+
+    x = %w(63 362 63632 dog cat)
+
+  The lowercased %w extracts space-separated tokens into array elements.
+
+  The uppercased %W does double-quoted string subtiutions, which is
+  useful if you want to use variables.
+
+  Examples for %W:
+
+    x = %W( one two -#{Time.now}-)
+    x = %W( one #two three #{Time.now} ) # => ["one", "#two", "three", "2024-02-25 02:46:21 +0000"]
+
+
 ## Create an Array with 5 random numbers:
 
     Array.new(5) { rand(10) }
@@ -602,29 +626,6 @@
       (1..5000).select {|i| i % 3 == 0 } # Wählt 3,6,9,12
       etc.. aus
 
-## How can I check whether something is included in 
-      an array or not? (inarray, is in array, in_array)
-      a = [ "a", "b", "c" ] #
-      a.include?("b") # true
-
-    If you want to do this for an object called x and the array y
-
-      y.member?(x)
-
-      frage("I am used to perl's qw(). How to make this in ruby? Is
-      there a shortcut for creating arrays? (quoted words)")+
-      x = %w(63 362 63632 dog cat)
-
-    The lowercased %w extracts space-separated 
-      tokens into array elements.
-
-     The uppercased %W does double-quoted string subtiutions. 
-      Useful if you want to use variables.
-
-    Beispiel für %W:
-
-    x=%W(  one two -#{Time.now}-)
-
 ## Wie suche ich nach einem String in einem Array?','grep
       array = ["one","two","three","four"]
       array.grep("three")

data/doc/core/gem_and_gemspec.md

@@ -373,22 +373,23 @@
       include Gem::Text
       levenshtein_distance 'shevy', 'chevy' # => 1
 
-      # ===================================================================== #
-      # === How to compare two program versions with one another
-      # ===================================================================== #
-## Wie kann ich verschiedene Versionen 
-      miteinander vergleichen?
-      Gem::Version.new('0.4.1') > Gem::Version.new('0.10.1')
 
-      Um den <b>dependency check</b> zu ignorieren (force install) 
-      geht dies hier (bzw <b>gemif</b>):
+## How to compare two program versions with one another
+
+  Use:
 
-      gem install -f lalala
+    Gem::Version.new('0.4.1') > Gem::Version.new('0.10.1')
+
+  Um den <b>dependency check</b> zu ignorieren (force install) 
+  geht dies hier (bzw <b>gemif</b>):
+
+    gem install -f lalala
 
 ## Kann ich es vermeiden, .gemrc zu laden?
-      Ja. Verwende:
 
-      --config-file
+  Yes. Make use of:
+
+    --config-file
 
 ## Wie erhalte ich das Bindir Verzeichnis von Gem?
 

data/doc/core/hash.md

@@ -1,3 +1,9 @@
+## How to transform every key in a Hash?
+
+  hash = { name: 'Rob', age: '28' }
+  hash.transform_keys { |entry| entry.to_s.upcase } # => { "NAME" => "Rob", "AGE" => "28" }
+  hash.transform_keys! { |entry| entry.to_s.upcase } # => { "NAME" => "Rob", "AGE" => "28" }
+
 ## How can we convert an Array into a Hash, in Ruby? (array2hash)
 
     j = Hash[*array] # => {"a"=>"b", "c"=>"d", "e"=>"Jkl"}

data/doc/core/misc.md

@@ -1,3 +1,26 @@
+## How can we read data from a .rb file without ruby evaluating this data?
+
+  Make use of:
+
+    p DATA.read
+    __END__
+
+  DATA.read liest die Information ein, die nach __END__ geschrieben 
+  ist. Man kann dies sogar verwenden um Configurations-Dateien in 
+  einer .rb Datei zu speichern.
+
+  Die Konstante <b>DATA</b> ist verfügbar sobald die __END__
+  Direktive in einer .rb Datei drinnen steht. Alles was dieser 
+  __END__ Direktive folgt ist dann Inhalt von DATA.
+
+  DATA ist leider nur für $0 verfügbar.
+
+  DATA ist ein File Objekt. Man kann daher auch <b>DATA.pos</b>
+  verwenden.
+
+  Man kann mittels <b>__END__</b> auch direkt YAML Code in
+  ein .rb <b>Skript</b> einfügen.
+
 ## How do we find out how many arguments a method will accept? (alos known as arity)
 
   This is possible via the <b>.arity</b> method.
@@ -1150,26 +1173,6 @@
 
     d.send(:attr=, 99) # macht das selbe wie oben, nur verboser.
 
-## Wie lese ich Daten von einer .rb Datei ohne das Ruby
-      diese Daten interpretiert?','__END__
-    p DATA.read
-    __END__
-
-    DATA.read liest die Information ein, die nach __END__ geschrieben 
-      ist. Man kann dies sogar verwenden um Configurations-Dateien in 
-      einer .rb Datei zu speichern.
-
-      anm('Die Konstante <b>DATA</b> ist verfügbar sobald die __END__ 
-      Direktive in einer .rb Datei drinnen steht. Alles was dieser 
-      __END__ Direktive folgt ist dann Inhalt von DATA.
-      anm('DATA ist leider nur für $0 verfügbar.
-
-      anm('DATA ist ein File Objekt. Man kann daher auch <b>DATA.pos</b>
-      verwenden.
-
-    Man kann mittels <b>__END__</b> auch direkt YAML Code in
-      ein .rb <b>Skript</b> einfügen.
-
 ## Wie erhalte ich das Default External Ruby Encoding via
       Commandline?
       ruby -e 'p Encoding.default_external'

data/doc/core/regex.md

@@ -397,7 +397,7 @@ https://github.com/perlpilot/perl6-docs/blob/master/intro/p6-regex-intro.pod
 
     '$1
 
-  bzw in Verbindung mit <b>.gsub</b>
+  or alternative, in conjunction with <b>.gsub</b>
 
      line = "Tennis/Soccer/Balls"
     "  line.gsub!(%r{Tennis/Soccer/(.+?)}, '\\1') 

data/doc/core/stderr.md

@@ -1,3 +1,19 @@
 ## How to redirect $stderr in ruby?
 
   $stderr.reopen("err.txt", "w")
+
+## How can we silence $stderr in ruby but then restore it again?
+
+Use something like:
+
+  @original_stderr = $stderr.clone
+  STDERR.puts('Hello, from STDERR') # this will go to standard error
+  $stderr.reopen('/dev/null', 'w')
+  STDERR.puts('Hello, from STDERR') # this will go to standard error
+  result = `tmux -V `
+  pp result
+  pp 'OK'
+  $stderr.reopen(@original_stderr)
+  result = `tmux -V `
+  pp result
+  pp 'OK'

data/doc/deprecations/deprecations.md

@@ -9,7 +9,8 @@ Roebe::Shell instance then you should simply use
 Roebe::Shell.home_directory? instead.
 
 On the 30.05.2023, the old NAMESPACE constant of the Roebe::Shell
-was removed - it was no longer needed.
+was removed - it was no longer needed, as the method .infer_the_namespace()
+takes care of that nowadays.
 
 On the 30.05.2023 the constant FILE_DIAMONDRC was removed. Use
 a separate method call if you need to obtain the path to the

data/doc/statistics/statistics.md

@@ -94,5 +94,6 @@ Total gems (ideally store it at the end of the month):
   Total gems 172,440 (Jul 2022), Total users 169,484 # ← 14.07.2022
   Total gems 174,304 (Dec 2022), Total users 172,523 # ← 04.12.2022
   Total gems 178,865 (Nov 2023), Total users 183,129 # ← 16.11.2023
+  Total gems 179,738 (Feb 2024), Total users 186,502 # ← 02.02.2024
 
 # https://rubygems.org/stats

data/lib/roebe/actions/actions.rb

@@ -0,0 +1,80 @@
+#!/usr/bin/ruby -w
+# Encoding: UTF-8
+# frozen_string_literal: true
+# =========================================================================== #
+# === Roebe::Actions
+# =========================================================================== #
+# require 'roebe/actions/actions.rb'
+# dataset = Roebe.actions(:contacts_dataset)
+# Roebe.actions(ARGV)
+# =========================================================================== #
+module Roebe
+
+  require 'roebe/constants/roebe.rb'
+
+  # ========================================================================= #
+  # === Roebe.actions                               (action tag, actions tag)
+  # ========================================================================= #
+  def self.actions(
+      action_that_is_desired = nil,
+      optional_argument1     = ARGV, # This is typically the main input to this method.
+      options_hash           = {},
+      &block
+    )
+    # ======================================================================= #
+    # First this method will handle Arrays:
+    # ======================================================================= #
+    if action_that_is_desired.is_a? Array
+      action_that_is_desired.each {|this_action|
+        Roebe.actions(
+          this_action,
+          optional_argument1,
+          options_hash,
+          &block
+        )
+      }
+    else
+      _ = optional_argument1 # Easier "pointer" here.
+      case action_that_is_desired # (case tag)
+      # ======================================================================= #
+      # === :make_gem
+      #
+      # Usage example:
+      #
+      #   dataset = Roebe.actions(:make_gem)
+      #
+      # ======================================================================= #
+      when :make_gem,
+           :MakeGem
+        require 'roebe/classes/make_gem.rb'
+        Roebe.make_gem(_, &block)
+      # ======================================================================= #
+      # === :contacts_dataset
+      #
+      # Usage example:
+      #
+      #   dataset = Roebe.actions(:contacts)
+      #
+      # ======================================================================= #
+      when :contacts_dataset,
+           :ContactsDataset,
+           :contacts
+        require 'yaml'
+        this_file = Roebe.file_contacts
+        return YAML.load_file(this_file)
+      # ======================================================================= #
+      # === :create_my_directories
+      # ======================================================================= #
+      when :create_my_directories,
+           :CreateMyDirectories
+        require 'roebe/classes/create_my_directories.rb'
+        Roebe::CreateMyDirectories.new(_, &block)
+      end
+    end
+  end; self.instance_eval { alias action actions } # === Roebe.action
+
+end
+
+if __FILE__ == $PROGRAM_NAME
+  Roebe.actions(ARGV)
+end # roebe_actions