Comments (5)
ruby 3.2.2 + Rails 7.1.alpha
from kramdown.
You need to use
gem "kramdown"
without the github specifier.
from kramdown.
Hi,
But I always use that specifier as a sort of convention. Among all my hundreds of gems, only Kramdown gives me this problem.
I'll try coming up with a solution. Thanks!
from kramdown.
I figured it out and wrote kramdown.gemspec
:
# coding: utf-8
lib = File.expand_path('../lib', __FILE__)
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
require 'kramdown/version'
Gem::Specification.new do |spec|
spec.name = "kramdown"
spec.version = Kramdown::VERSION
spec.authors = ["Thomas Leitner"]
spec.email = ["[email protected]"]
spec.summary = %q{Kramdown is a fast, pure Ruby Markdown superset converter.}
spec.description = %q{Kramdown is a fast, pure Ruby Markdown superset converter, using a strict syntax definition and supporting several common extensions.}
spec.homepage = "https://kramdown.gettalong.org/"
spec.license = "MIT"
spec.files = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
spec.bindir = "exe"
spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
spec.require_paths = ["lib"]
spec.add_dependency "coderay", "~> 1.1"
spec.add_dependency "rouge", "~> 2.0"
end
However then I noticed you have it in your .gitignore
, why's that? Having it should offer many benefits:
-
Ease of use for developers: Developers will be able to use Bundler's GitHub shorthand to specify the Kramdown gem in their Gemfile. This is simpler and more intuitive than the current method, which involves cloning the repository, building the gem manually, and specifying the path to the built gem in the Gemfile.
-
Increased adoption: By making it easier to use the Kramdown gem directly from the repository, we can potentially increase its adoption. Developers who were previously deterred by the complex installation process might be more inclined to use the gem if they can specify it easily in their Gemfile.
-
Up-to-date usage: Developers can get updates as soon as they are pushed to the repository. This can be particularly beneficial for developers who want to use the latest features or bug fixes before they are included in a released version of the gem.
from kramdown.
So, this is not an "issue". You should, by default, rely only on released versions. If you rely on versions on Github, you might rely on something that is not stable or tested. You can't assume that a repository holds a state that is usable. This might be the case for many but still, mistakes are easy.
What complex installation routine? If you want kramdown, you run gem install kramdown
or you specify gem 'kramdown'
in your Gemfile. This is neither easier nor harder than any other gem.
So with kramdown you have a conscious choice to make: You use the released version (the easy way) or use a potentially unstable version (the harder way because you need to clone the repo and create a Gemfile). It is up to you.
from kramdown.
Related Issues (20)
- handling `br` inside formatting tags HOT 2
- [feature] support inline notes
- Attribute name consisting of colon does not get parsed HOT 1
- Code block language not parsing in details/summary following math expression HOT 2
- Custom Parser Support HOT 1
- MD to HTML is adding spaces to code segments. HOT 4
- Add an extension for parsing Mermaid syntax to the libraries extending the functionality of kramdown HOT 1
- Pipe characters within a inline link is parsed as a table (rather than a link) HOT 1
- `markdown="0"` meaning HOT 1
- Select whether an HTML tag is parsed as block or span level HOT 2
- `time` should be span level by default HOT 1
- Void elements should not use trailing slashes. HOT 2
- Jekyll kramdown: How to disable generating styles in tables? HOT 1
- Rouge CSS not applied to code HOT 2
- Japanese chars combined with MD syntax are not converted HOT 5
- Can I remove the image parsing method? HOT 2
- parse failure on empty tables
- Odd behavior with nested table and mixing block and inline elements HOT 1
- [bug] Kramdown converter fails with NoMethodError: undefined method `type' for nil HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kramdown.