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.

Sign up for GitHub

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

Jump to bottom

Better messages on parse errors #295

Open
georgebrock opened this issue Apr 25, 2017 · 1 comment
Open

Better messages on parse errors #295

georgebrock opened this issue Apr 25, 2017 · 1 comment
Labels
enhancement
Milestone
v1.0

Comments

@georgebrock
Copy link
Collaborator

Any error encountered by the lexer or parser will result in the somewhat unhelpful message gitsh: parse error.

We should try to tell the user:

  • what went wrong.
  • where the error occurred (especially for scripts).
@georgebrock georgebrock added this to the v1.0 milestone Feb 3, 2019
@georgebrock
Copy link
Collaborator Author

The work done in #355 for reporting tab completion config file errors is probably relevant to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
1 participant
@georgebrock