DirTagger 2.0.4 → 2.0.5
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.
- data/bin/dir_tagger +1 -1
- data/lib/dir_tagger.rb +1 -1
- metadata +43 -25
data/bin/dir_tagger
CHANGED
data/lib/dir_tagger.rb
CHANGED
|
@@ -130,7 +130,7 @@ module DirTagger # :nodoc:
|
|
|
130
130
|
end).parse(argv)
|
|
131
131
|
|
|
132
132
|
# Preparing for the running environment
|
|
133
|
-
@profile = Pathname.new(
|
|
133
|
+
@profile = Pathname.new(File.expand_path('~')).join(Profile_Name) # profile path
|
|
134
134
|
@dir_taggers = DirTaggers.new
|
|
135
135
|
# Run actions
|
|
136
136
|
if options.actions.empty?
|
metadata
CHANGED
|
@@ -1,52 +1,70 @@
|
|
|
1
|
-
--- !ruby/object:Gem::Specification
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: DirTagger
|
|
3
|
-
version: !ruby/object:Gem::Version
|
|
4
|
-
|
|
3
|
+
version: !ruby/object:Gem::Version
|
|
4
|
+
hash: 5
|
|
5
5
|
prerelease:
|
|
6
|
+
segments:
|
|
7
|
+
- 2
|
|
8
|
+
- 0
|
|
9
|
+
- 5
|
|
10
|
+
version: 2.0.5
|
|
6
11
|
platform: ruby
|
|
7
|
-
authors:
|
|
12
|
+
authors:
|
|
8
13
|
- Van Hu
|
|
9
14
|
autorequire:
|
|
10
15
|
bindir: bin
|
|
11
16
|
cert_chain: []
|
|
12
|
-
|
|
17
|
+
|
|
18
|
+
date: 2012-08-22 00:00:00 +08:00
|
|
19
|
+
default_executable:
|
|
13
20
|
dependencies: []
|
|
14
|
-
description: ! 'A gem saving some frequent used paths and keeping them at hand, both
|
|
15
|
-
in a very ease and comportable way. The concept is to give your directory a tag,
|
|
16
|
-
and then store it in ''~/.tag_dir_profile''. After that, you can retrieve the path
|
|
17
|
-
of the directory by a shell command with the tag as parameter.
|
|
18
21
|
|
|
19
|
-
|
|
22
|
+
description: |-
|
|
23
|
+
A gem saving some frequent used paths and keeping them at hand, both in a very ease and comportable way. The concept is to give your directory a tag, and then store it in '~/.tag_dir_profile'. After that, you can retrieve the path of the directory by a shell command with the tag as parameter.
|
|
24
|
+
Usage is here: https://github.com/bom-d-van/dir_tagger
|
|
20
25
|
email: bom.d.van@gmail.com
|
|
21
|
-
executables:
|
|
26
|
+
executables:
|
|
22
27
|
- dir_tagger
|
|
23
28
|
extensions: []
|
|
29
|
+
|
|
24
30
|
extra_rdoc_files: []
|
|
25
|
-
|
|
31
|
+
|
|
32
|
+
files:
|
|
26
33
|
- lib/dir_tagger.rb
|
|
27
34
|
- bin/dir_tagger
|
|
35
|
+
has_rdoc: true
|
|
28
36
|
homepage: https://github.com/bom-d-van/dir_tagger
|
|
29
37
|
licenses: []
|
|
38
|
+
|
|
30
39
|
post_install_message:
|
|
31
40
|
rdoc_options: []
|
|
32
|
-
|
|
41
|
+
|
|
42
|
+
require_paths:
|
|
33
43
|
- lib
|
|
34
|
-
required_ruby_version: !ruby/object:Gem::Requirement
|
|
44
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
|
35
45
|
none: false
|
|
36
|
-
requirements:
|
|
37
|
-
- -
|
|
38
|
-
- !ruby/object:Gem::Version
|
|
39
|
-
|
|
40
|
-
|
|
46
|
+
requirements:
|
|
47
|
+
- - ">="
|
|
48
|
+
- !ruby/object:Gem::Version
|
|
49
|
+
hash: 3
|
|
50
|
+
segments:
|
|
51
|
+
- 0
|
|
52
|
+
version: "0"
|
|
53
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
|
41
54
|
none: false
|
|
42
|
-
requirements:
|
|
43
|
-
- -
|
|
44
|
-
- !ruby/object:Gem::Version
|
|
45
|
-
|
|
55
|
+
requirements:
|
|
56
|
+
- - ">="
|
|
57
|
+
- !ruby/object:Gem::Version
|
|
58
|
+
hash: 3
|
|
59
|
+
segments:
|
|
60
|
+
- 0
|
|
61
|
+
version: "0"
|
|
46
62
|
requirements: []
|
|
63
|
+
|
|
47
64
|
rubyforge_project:
|
|
48
|
-
rubygems_version: 1.
|
|
65
|
+
rubygems_version: 1.5.3
|
|
49
66
|
signing_key:
|
|
50
67
|
specification_version: 3
|
|
51
|
-
summary:
|
|
68
|
+
summary: "*nix system file system helper"
|
|
52
69
|
test_files: []
|
|
70
|
+
|