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

Traceback for MiniHTML parse errors #1882

Open
keith-hall opened this issue Sep 1, 2017 · 0 comments
Open

Traceback for MiniHTML parse errors #1882

keith-hall opened this issue Sep 1, 2017 · 0 comments

Comments

@keith-hall
Copy link
Collaborator

Summary

Currently, when a minihtml parse error occurs, there is no way to tell which package / in which plugin file (and where in the plugin i.e. line number) the invalid HTML came from.

Expected behavior

The console would show a file path and a line number for the minihtml engine's parse errors, maybe something similar to a Python traceback.

Traceback (most recent call last):
  File "C:\Program Files\Sublime Text 3\sublime_plugin.py", line 818, in run_
    return self.run(edit)
  File "C:\Users\Keith\AppData\Roaming\Sublime Text 3\Packages\User\example_minihtml.py", line 7, in run
    raise Exception('Parse Error:  code: Unexpected EOF')

Actual behavior

The console just shows the parse error with no package or location information.

Parse Error: code: Unexpected EOF

Steps to reproduce

  1. Create a new plugin file
  2. In the run method, enter self.view.show_popup('<') Enter
  3. Execute the command (i.e. in the ST console type view.run_command('example') Enter)
  4. Observe that the output in the ST console is Parse Error: code: Unexpected EOF
  5. Wonder which plugin caused this parse error and where

Environment

  • Operating system and version:
    • Windows
    • Mac OS
    • Linux
  • Sublime Text:
    • Build 3142
    • 64 bit

(This was originally suggested on the forum)

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

No branches or pull requests

1 participant