Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New error parsing Runfile using v0.11.0 #70

Closed
brunk opened this issue Jan 24, 2023 · 1 comment · Fixed by #71
Closed

New error parsing Runfile using v0.11.0 #70

brunk opened this issue Jan 24, 2023 · 1 comment · Fixed by #71

Comments

@brunk
Copy link

brunk commented Jan 24, 2023

I just upgraded to run version v0.11.0 on Mac Ventura 13.1 installed with brew and started getting errors for command names containing a dash (-) or underscore (_).

If I am reading the documentation correctly this should work and did in previous versions.

$ run version
run v0.11.0

With the following sample configuration:

# Set default shell for all actions
.SHELL = bash

EXPORT RUNFILE := "${.RUNFILE}"

## Check configuration
config-check:
    echo "RUNFILE: $RUNFILE"

I now get the following error:

$ run list
run: Runfile:7.1: expecting runfile statement

If I remove the dash:

# Set default shell for all actions
.SHELL = bash

EXPORT RUNFILE := "${.RUNFILE}"

## Check configuration
configcheck:
    echo "RUNFILE: $RUNFILE"

I get the correct result:

$ run list
Commands:
  list           (builtin) List available commands
  help           (builtin) Show help for a command
  version        (builtin) Show run version
  configcheck    Check configuration
@TekWizely
Copy link
Owner

@brunk EEK! Thanks for reporting the issue

I did move around a couple of the pattern matchers to accommodate recent features and looks like I might have the dash matcher in the wrong sequence.

I'll dive in soon and update notes here, and likely get a PR started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants