brew/Library/Homebrew/cmd/home.rb

# frozen_string_literal: true

require "cli/parser"

module Homebrew
  module_function

  def home_args
    Homebrew::CLI::Parser.new do
      usage_banner <<~EOS
        `home` [<formula>]

        Open <formula>'s homepage in a browser, or open Homebrew's own homepage
        if no formula is provided.
      EOS
      switch :debug
    end
  end

  def home
    home_args.parse

    if args.remaining.empty?
      exec_browser HOMEBREW_WWW
    else
      exec_browser(*Homebrew.args.formulae.map(&:homepage))
    end
  end
end
Add frozen_string_literal to all files. 2019-04-19 15:38:03 +09:00			`# frozen_string_literal: true`

Rename cli_parser to cli/parser. 2019-04-17 18:25:08 +09:00			`require "cli/parser"`
home: Use CLI::Parser to parse args 2018-11-06 21:28:12 +05:30
Only "extend self" once on the Homebrew module 2014-06-18 22:41:47 -05:00			`module Homebrew`
Use `module_function` for commands. 2016-09-26 01:44:51 +02:00			`module_function`

home: Use CLI::Parser to parse args 2018-11-06 21:28:12 +05:30			`def home_args`
			`Homebrew::CLI::Parser.new do`
			`usage_banner <<~EOS`
			`home` [<formula>]

manpages: sentence rewording for readability Use active voice when applicable, better verbs & adjectives, preposition usage, proper tense, etc. 2019-08-20 00:04:14 -04:00			`Open <formula>'s homepage in a browser, or open Homebrew's own homepage`
			`if no formula is provided.`
home: Use CLI::Parser to parse args 2018-11-06 21:28:12 +05:30			`EOS`
			`switch :debug`
			`end`
			`end`

Refactor the brew command into one file per command The code was sucking. To the extent that maintenance was hard. It's a lot easier to work with code that is sensibly split at sensible boundaries. So now it is more like that. But the refactor is minimal. Because we don't want you to have more merge hell than absolutely necessary. If you merge you will need to pay attention to brew.h.rb (as it is deleted) and bin/brew (as command logic is gone). It will be painful, but you will just have to help git out by moving any changes around manually. Note compatibility.rb. It ensures that any function renames or removals don't break anything. We're pretty serious about backwards compatibility. And that's because we encourage you to hack around with the innards. And we couldn't do that if we would then just make stuff disappear behind your back. 2010-09-11 20:22:54 +01:00			`def home`
home: Use CLI::Parser to parse args 2018-11-06 21:28:12 +05:30			`home_args.parse`

			`if args.remaining.empty?`
Respect BROWSER environment variable 2012-12-27 23:34:29 -06:00			`exec_browser HOMEBREW_WWW`
Refactor the brew command into one file per command The code was sucking. To the extent that maintenance was hard. It's a lot easier to work with code that is sensibly split at sensible boundaries. So now it is more like that. But the refactor is minimal. Because we don't want you to have more merge hell than absolutely necessary. If you merge you will need to pay attention to brew.h.rb (as it is deleted) and bin/brew (as command logic is gone). It will be painful, but you will just have to help git out by moving any changes around manually. Note compatibility.rb. It ensures that any function renames or removals don't break anything. We're pretty serious about backwards compatibility. And that's because we encourage you to hack around with the innards. And we couldn't do that if we would then just make stuff disappear behind your back. 2010-09-11 20:22:54 +01:00			`else`
argv: move formulae to cli/args 2019-09-08 19:56:24 +05:30			`exec_browser(*Homebrew.args.formulae.map(&:homepage))`
Refactor the brew command into one file per command The code was sucking. To the extent that maintenance was hard. It's a lot easier to work with code that is sensibly split at sensible boundaries. So now it is more like that. But the refactor is minimal. Because we don't want you to have more merge hell than absolutely necessary. If you merge you will need to pay attention to brew.h.rb (as it is deleted) and bin/brew (as command logic is gone). It will be painful, but you will just have to help git out by moving any changes around manually. Note compatibility.rb. It ensures that any function renames or removals don't break anything. We're pretty serious about backwards compatibility. And that's because we encourage you to hack around with the innards. And we couldn't do that if we would then just make stuff disappear behind your back. 2010-09-11 20:22:54 +01:00			`end`
			`end`
			`end`