We have currently simple GitHub page, but we need to think about it's update with some better design.

Since state is a reserved keyword in Truffle's guard mechanism, it should not be possible to use it in a guard definition as this can cause serious problems. The annotation processor should either reject the state keyword in guard definitions or the state temporary variable produced by the processor should be renamed to avoid this conflict.

Here's an example:
<img width="629" alt="screen

Steps to reproduce

Run asdf. In help output a line is printed for the asdf env command:

asdf env <command> [executable]      Prints or runs an executable under a command environment

I would assume <command> is an arbitrary command. But from what I can tell needs to be a plugin name or a shim name? I'm also not sure how this differs from executing the shim directly.

FY

        --fail-level SEVERITY        Minimum severity (A/I/R/C/W/E/F) for exit
                                     with error code.

• say what the letters mean or only show long-form (autocorrect etc)
• ideally support all or any so it's obvious that I want to fail on anything
  because someone reading --fail-level A needs to read up on what that means whereas `--fail-level an

I am trying to write my own custom route matcher and using the example in the readme, I receive the following error:
AllButPattern can't be coerced into Mustermann::Pattern (TypeError)

Here is my example code:

require 'sinatra'

get '/index' do
  'Hello world!'
end

class AllButPattern
  Match = Struct.new(:captu

To allow Linux users to use brew services and to make formula less OS dependent we should migrate the formulae to use the OS agnostic service do block.

• bitlbee
• dbus
• kapacitor
• launch_socket_server
• launchdns
• opentsdb
• questdb
• rtags
• ssdb
• wildfly-as
• zookeeper

Homebrew/homebrew-core#91809