viewmd 0.1.0 → 0.2.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 3444da61b127641f4673be0fdc72ad9f57b63914
4
- data.tar.gz: 3087b5294d9b83cf39e158eb08122b7d8ed19a40
3
+ metadata.gz: def90ea77cc1d012d5715ade12cf309f50c1e5bb
4
+ data.tar.gz: 6cc5b29e5e42b08043e93a54973081dff2249e9c
5
5
  SHA512:
6
- metadata.gz: 23d7a657f5bf47924a98a34351b3d63d39d71035ab08e09992672e47f8cce14ff4a1e4e0c372b1f9495870e79a0f7b726e6fe6392d45a45982fb54dff4b95dd9
7
- data.tar.gz: 50444cc0fcfad27692da5477171bb3d1bd600d90694cb2db305c6ec14fc9ce5a17208d622e43ff109759e66ffb152002844067a48b7c3139f3374cfabab0e7ad
6
+ metadata.gz: 6a291e71610a7edf45d32acaeee2820c18d0187075be89998979cf276854cb6774a0274bc6a1885c41716dc933f0d37540dd616fc26dc064a06b0ee5b780e059
7
+ data.tar.gz: 210f7cb1d9144ea120276c08b47ffd7c39f1e1b46dbb40d3c1928f27c984e6a7c2a0cd536fba36a3b721bab0c60ef88e913b26a55ef46a2e3e52cdaaa8c60142
data/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Viewmd
2
2
 
3
- Viewmd is a command line tool for viewing your Markdown files (e.g. README.md) in your local browser. Uses GitHub Markup parser, so the result should look very close to what you'd see on Github if you put the file there.
3
+ Viewmd is a command line tool for viewing your Markdown files (e.g. README.md) in your local browser. Uses [GitHub dialect](https://help.github.com/articles/github-flavored-markdown) of Markdown, so the result should look very close to what you'd see on Github if you put the file on GitHub.
4
4
 
5
5
  I guess, we all hate committing files with bugs. In case of Markdown files, like README.md, it's possible to make some little mistake while editing the file (e.g. forget the trailing triple-backticks) and end up with an incorrectly formatted file checked in to your repository. Seeing it only on GitHub already, for example, and having to do another little fix & commit just to fix this little formatting mistake seens like an untidy process to me. Thus I created this really simple command-line tool to see how the file would look like *before* committing.
6
6
 
@@ -44,7 +44,7 @@ The public API should not be considered stable.
44
44
  ## Dependencies
45
45
 
46
46
  * [github-markup](https://github.com/github/markup)
47
- * [redcarpet](https://github.com/vmg/redcarpet)
47
+ * [github-markdown](https://rubygems.org/gems/github-markdown)
48
48
  * [launchy](https://github.com/copiousfreetime/launchy)
49
49
 
50
50
  ## Contributing
@@ -1,3 +1,3 @@
1
1
  module Viewmd
2
- VERSION = "0.1.0"
2
+ VERSION = "0.2.0"
3
3
  end
data/viewmd.gemspec CHANGED
@@ -27,7 +27,7 @@ Gem::Specification.new do |spec|
27
27
 
28
28
  spec.add_dependency 'github-markup', '>= 1.3'
29
29
  spec.add_dependency 'launchy', '>= 2.4'
30
- spec.add_dependency 'redcarpet', '>= 3.1'
30
+ spec.add_dependency 'github-markdown', '>= 0.6'
31
31
 
32
32
  spec.add_development_dependency "bundler", ">= 1.6"
33
33
  spec.add_development_dependency "rake"
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: viewmd
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 0.2.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - moonfly (Andrey Pronin)
@@ -39,19 +39,19 @@ dependencies:
39
39
  - !ruby/object:Gem::Version
40
40
  version: '2.4'
41
41
  - !ruby/object:Gem::Dependency
42
- name: redcarpet
42
+ name: github-markdown
43
43
  requirement: !ruby/object:Gem::Requirement
44
44
  requirements:
45
45
  - - ">="
46
46
  - !ruby/object:Gem::Version
47
- version: '3.1'
47
+ version: '0.6'
48
48
  type: :runtime
49
49
  prerelease: false
50
50
  version_requirements: !ruby/object:Gem::Requirement
51
51
  requirements:
52
52
  - - ">="
53
53
  - !ruby/object:Gem::Version
54
- version: '3.1'
54
+ version: '0.6'
55
55
  - !ruby/object:Gem::Dependency
56
56
  name: bundler
57
57
  requirement: !ruby/object:Gem::Requirement