You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just brainstorming with @natebosch about this idea:
I often use stacktraces to debug issues, I go through each line in the stack trace trying to find some details. I manually convert the source location to jump back in the code, desugaring package:* URIs as needed.
It would be great if the vim plugin could support this via some function. The function could let you invoke a command and parse the output, or it could take an input file instead. Not sure how to combine this together with vim-lsc: will the two conflict with each other if there happen to be errors in a file produced from the dart_language_server?
The text was updated successfully, but these errors were encountered:
I was just brainstorming with @natebosch about this idea:
I often use stacktraces to debug issues, I go through each line in the stack trace trying to find some details. I manually convert the source location to jump back in the code, desugaring
package:*
URIs as needed.It would be great if the vim plugin could support this via some function. The function could let you invoke a command and parse the output, or it could take an input file instead. Not sure how to combine this together with vim-lsc: will the two conflict with each other if there happen to be errors in a file produced from the dart_language_server?
The text was updated successfully, but these errors were encountered: