`jekyll` command prints a backtrace #1040

Closed
postmodern opened this Issue May 7, 2013 · 4 comments

Projects

None yet

2 participants

@postmodern
Contributor

Users should never see a backtrace from a CLI program.

$ jekyll
       Deprecation: Jekyll now uses subcommands instead of just switches. Run `jekyll help' to find out more.
/home/hal/.gem/ruby/1.9.1/gems/commander-4.1.3/lib/commander/runner.rb:365:in `block in require_program': program version required (Commander::Runner::CommandError)
    from /home/hal/.gem/ruby/1.9.1/gems/commander-4.1.3/lib/commander/runner.rb:364:in `each'
    from /home/hal/.gem/ruby/1.9.1/gems/commander-4.1.3/lib/commander/runner.rb:364:in `require_program'
    from /home/hal/.gem/ruby/1.9.1/gems/commander-4.1.3/lib/commander/runner.rb:52:in `run!'
    from /home/hal/.gem/ruby/1.9.1/gems/commander-4.1.3/lib/commander/delegates.rb:11:in `run!'
    from /home/hal/.gem/ruby/1.9.1/gems/commander-4.1.3/lib/commander/import.rb:10:in `block in '
@parkr
Member
parkr commented May 7, 2013

Users should never see a backtrace from a CLI program.

I hope you're kidding! Backtraces are incredibly helpful.

I agree that this could be cleaner, though.

@postmodern
Contributor

@parkr I am not kidding. Print a proper error message. Backtraces are only useful to developers, not users.

@parkr parkr closed this in d0a9948 May 7, 2013
@parkr
Member
parkr commented May 7, 2013

Now prints this:

~/code/jekyll/site$ bundle exec ../bin/jekyll --server
       Deprecation: Jekyll now uses subcommands instead of just switches. Run `jekyll help' to find out more.
       Deprecation: The --server command has been replaced by the 'serve' subcommand.
invalid option: --server
@parkr parkr added a commit that referenced this issue May 7, 2013
@parkr parkr Update history to reflect fix of #1040 e12482f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment