directory_paradise 1.4.5 → 1.4.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 9a9d6aaf616b92f7e2fcdbe01335b59fb54a4c754e3bf208ee2ef42c9eff961c
4
- data.tar.gz: 487b2c07cc240cb7ef01bd5f05791f139763b8781cab95387d00f5002be3675d
3
+ metadata.gz: 9de1c871c7ae3a931631cec20714bdb1a4a9596aa0315a20f07050fe56088a5c
4
+ data.tar.gz: 1f3459eba6a305f936708488c955b2148ed80ade2fcf392254e9873637c579d7
5
5
  SHA512:
6
- metadata.gz: 337d80156b3150f15dd99ac6e1cabb3455c97b0ff23b47cfe28aeecd5f057594148640d5b59b7bd2bbdb079c0b4d268a5da51ffbc9c9a8c687b022cc69e82b39
7
- data.tar.gz: 496af2302209e8716c0512822fbf116ff068212c1638580cd8787e25a4754cea63a7209297c1510d2035f34faa689868c6fa2c1c3c8942672d606e27f4a4a0b0
6
+ metadata.gz: 97946fee54b5b09d32088603cb1749493e7f997f4ec1acaece6334f9c06a5d2d5600641903da9ad95fc189f910fb95a9930006fed39a8165402d89505dab045a
7
+ data.tar.gz: ae3f3a939732987b0a673c4a743911d5d79bb7fe70f1ef49fde084a3aa0368c74d81a8e16a337959ada5ff4184b1e7ea06a1f477eb4dca53772435fbd561888d
data/README.md CHANGED
@@ -5,7 +5,7 @@
5
5
  [![forthebadge](https://forthebadge.com/images/badges/made-with-ruby.svg)](https://www.ruby-lang.org/en/)
6
6
  [![Gem Version](https://badge.fury.io/rb/directory_paradise.svg)](https://badge.fury.io/rb/directory_paradise)
7
7
 
8
- This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">06.08.2022</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">00:57:31</span> o'clock.
8
+ This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">08.11.2023</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">23:22:08</span> o'clock.
9
9
 
10
10
  <img src="https://i.imgur.com/hbGDM7i.jpg">
11
11
 
@@ -194,35 +194,53 @@ more useful in general, feel free to drop me an email at any time, via:
194
194
  shevy@inbox.lt
195
195
 
196
196
  Before that email I used an email account at Google gmail, but in **2021** I
197
- decided to slowly abandon gmail for various reasons. In order to limit this
197
+ decided to slowly abandon gmail, for various reasons. In order to limit the
198
198
  explanation here, allow me to just briefly state that I do not feel as if I
199
- want to promote any Google service anymore, for various reasons.
200
-
201
- Do keep in mind that responding to emails may take some time, depending on
202
- the amount of work I may have at that moment.
203
-
204
- In 2022 rubygems.org decided to make 2FA mandatory for every gem owner:
205
- see https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html
206
-
207
- As I can not use 2FA, for reasons I will skip explaining here (see
208
- various github issue discussions in the past), this effectively means that
209
- Betty Li and others who run the show at rubygems.org will perma-ban me
210
- from using rubygems as a developer.
211
-
212
- As I disagree with that decision completely, this will mean that all my
213
- gems will be removed from rubygems.org prior to that sunset date, e. g.
214
- before they permanently lock me out from the code that I used
215
- to maintain. It is pointless to want to discuss this with them anymore -
216
- they have made up their minds and decided that you can only use
217
- the code if 2FA is in place, even though the code itself works just
218
- fine. If you don't use 2FA you are effectively locked out from your
219
- own code; I consider this a malicious attack. See also how they limited
220
- discussions to people with mandatory 2FA on the ruby-bugtracker, thus
221
- banning everyone permanently without 2FA:
222
-
223
- https://bugs.ruby-lang.org/issues/18800
224
-
225
- Guess it may indeed be time to finally abandon ruby - not because
226
- ruby is a bad language, but there are people now in charge who
227
- really should not be part of ruby in the first place.
199
+ want to promote any Google service anymore when the user becomes the end
200
+ product (such as via data collection by upstream services, including other
201
+ proxy-services). My feeling is that this is a hugely flawed business model
202
+ to begin with, and I no longer wish to support this in any way, even if
203
+ only indirectly so, such as by using services of companies that try to
204
+ promote this flawed model.
205
+
206
+ In regards to responding to emails: please keep in mind that responding
207
+ may take some time, depending on the amount of work I may have at that
208
+ moment. So it is not that emails are ignored; it is more that I have not
209
+ (yet) found the time to read and reply. This means there may be a delay
210
+ of days, weeks and in some instances also months. There is, unfortunately,
211
+ not much I can do when I need to prioritise my time investment, but I try
212
+ to consider <b>all</b> feedback as an opportunity to improve my projects
213
+ nonetheless.
214
+
215
+ In <b>2022</b> rubygems.org decided to make 2FA mandatory for every
216
+ gem owner eventually:
217
+
218
+ see
219
+ https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html
220
+
221
+ Mandatory 2FA will eventually be extended to all rubygems.org developers and
222
+ maintainers. As I can not use 2FA, for reasons I will skip explaining here,
223
+ this means that my projects will eventually be removed, as I no longer
224
+ have any control over my projects hosted on rubygems.org (because I
225
+ can not use 2FA).
226
+
227
+ At that point, I no longer have any control what is done to my projects
228
+ since whoever is controlling the gems ecosystem took away our control
229
+ here. I am not sure at which point ruby became corporate-controlled -
230
+ that was not the case several years ago, so something has
231
+ changed.
232
+
233
+ Ruby also only allows 2FA users to participate on the issue tracker these
234
+ days:
235
+
236
+ https://bugs.ruby-lang.org/issues/18800
237
+
238
+ But this has been reverted some months ago, so it is no longer applicable.
239
+ Suffice to say that I do not think that we should only be allowed to
240
+ interact on the world wide web when some 'authority' authenticated us,
241
+ such as via mandatory 2FA, so I hope this won't come back again.
242
+
243
+ Fighting spam is a noble goal, but when it also means you lock out
244
+ real human people then this is definitely NOT a good situation
245
+ to be had.
228
246
 
@@ -653,7 +653,7 @@ class Content < Base # === DirectoryParadise::Content
653
653
  end; end
654
654
 
655
655
  if __FILE__ == $PROGRAM_NAME
656
- require 'colours/autoinclude'
656
+ require 'colours/html_colours'
657
657
  _ = DirectoryParadise::Content.new(ARGV) # or DirectoryParadise::Content[]
658
658
  e rev+
659
659
  steelblue(_.n_entries?.to_s)+' entries were found in this directory.'
@@ -47,7 +47,7 @@ module DirectoryParadise
47
47
 
48
48
  class Report < Base # === DirectoryParadise::Report
49
49
 
50
- require 'colours'
50
+ require 'colours/html_colours'
51
51
  require 'directory_paradise/project/project.rb'
52
52
  require 'directory_paradise/content/content.rb'
53
53
  require 'directory_paradise/report/menu.rb'
@@ -1038,7 +1038,7 @@ class Report < Base # === DirectoryParadise::Report
1038
1038
  e
1039
1039
  e sfile(" #{yaml_file?}")
1040
1040
  e
1041
- e 'To get a listing of all defined colour-names, do this:'
1041
+ e "#{rev}To get a listing of all defined colour-names, do this:"
1042
1042
  e
1043
1043
  e " require 'colours'"
1044
1044
  e ' pp Colours.html_colours?'
@@ -1474,7 +1474,7 @@ class Report < Base # === DirectoryParadise::Report
1474
1474
  ssymlink(
1475
1475
  n_symlinks.to_s+' symlink'+symlink_string
1476
1476
  )+'.'
1477
- append("contains "+
1477
+ append("#{rev}contains "+
1478
1478
  n_files.to_s+' file'+file_string+
1479
1479
  ', '+
1480
1480
  n_directories.to_s+' director'+directory_string+
@@ -1805,20 +1805,17 @@ class Report < Base # === DirectoryParadise::Report
1805
1805
  _ = optional_hash_use_these_colours
1806
1806
  if use_colours?
1807
1807
  if _ # If the Hash is defined, enter here.
1808
- pp 111
1809
1808
  @internal_hash[:default_colour] = Colours.beautiful _['colour_for_normal']
1810
1809
  @internal_hash[:colour_for_files] = Colours.beautiful _['colour_for_files']
1811
1810
  @internal_hash[:colour_for_symlinks] = Colours.beautiful _['colour_for_symlinks']
1812
1811
  @internal_hash[:colour_for_directories] = Colours.beautiful _['colour_for_directories']
1813
1812
  else # Try to use Konsole after this point.
1814
1813
  if Object.const_defined? :Colours
1815
- pp 222
1816
1814
  @internal_hash[:default_colour] = Colours.restore? # Restore the default again.
1817
1815
  @internal_hash[:colour_for_files] = Colours.springgreen
1818
1816
  @internal_hash[:colour_for_symlinks] = Colours.slateblue
1819
1817
  @internal_hash[:colour_for_directories] = Colours.paleturquoise
1820
1818
  else # Else, use the default colours. They are defined in the module Colours.
1821
- pp 333
1822
1819
  @internal_hash[:default_colour] = Colours::WHITE
1823
1820
  @internal_hash[:colour_for_files] = Colours::GREEN
1824
1821
  @internal_hash[:colour_for_symlinks] = Colours::BLUE
@@ -9,11 +9,11 @@ class DirectoryParadise
9
9
  # ========================================================================= #
10
10
  # === VERSION
11
11
  # ========================================================================= #
12
- VERSION = '1.4.5'
12
+ VERSION = '1.4.6'
13
13
 
14
14
  # ========================================================================= #
15
15
  # === LAST_UPDATE
16
16
  # ========================================================================= #
17
- LAST_UPDATE = '06.08.2022'
17
+ LAST_UPDATE = '08.11.2023'
18
18
 
19
19
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: directory_paradise
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.4.5
4
+ version: 1.4.6
5
5
  platform: ruby
6
6
  authors:
7
7
  - Robert A. Heiler
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2022-08-06 00:00:00.000000000 Z
11
+ date: 2023-11-08 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: colours
@@ -86,14 +86,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
86
86
  requirements:
87
87
  - - ">="
88
88
  - !ruby/object:Gem::Version
89
- version: 2.5.8
89
+ version: 2.7.6
90
90
  required_rubygems_version: !ruby/object:Gem::Requirement
91
91
  requirements:
92
92
  - - ">="
93
93
  - !ruby/object:Gem::Version
94
- version: 3.3.18
94
+ version: 3.4.18
95
95
  requirements: []
96
- rubygems_version: 3.3.18
96
+ rubygems_version: 3.4.18
97
97
  signing_key:
98
98
  specification_version: 4
99
99
  summary: This class will display the content of a directory. It can also give back