-
Notifications
You must be signed in to change notification settings - Fork 531
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
Remapping of escape character not handled #245
Comments
@paulcallen Hi, could you attach a screenshot and your Dockerfile to more clearly identify what the problem is? |
I think this is the same as issue #75 |
@thomashillyer I don't think that's quite the same. I feel like #75 is a parsing issue with quotes and backslashes whereas this #245 is due to the parser not being capable of reading Dockerfile's escape parser directive (understandably so in my opinion). |
@thomashillyer Yeah, you basically need a way to tell the grammar when you're in some For this issue #245 you need a way to teach the grammar about Dockerfile escape parser directives. That sounds equally difficult and non-standard for a grammar but I could be wrong... |
It's not clear how many people this is affecting. Is it blocking people? |
not blocking for me. It was more of an fyi for you. if it is easy to fix then go for it, if not then that is fine also, |
I have this problem. It's definitely frustrating, but, as it doesn't not actually prevent editing the file, I wouldn't classify it as blocking for me. It just completely breaks syntax highlighting. |
From a quick look it doesn't look like this would be very easy, but not an expert in g4. If someone wants to give it a shot, go for it! |
I filed microsoft/vscode#82985 and will close this issue as external. |
put this at the top of a docker file: # escape=`
and it remaps the escape character such that windows file paths can exist as
c:\foo
. Really nice feature.Unfortunately this plug-in does not recognize this and as a result it thinks
\f
is an invalid escape sequence.The text was updated successfully, but these errors were encountered: