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
tokens ignored in top level command line after ';;' #6472
Comments
Comment author: @damiendoligez It's been there for decades. Most people don't ever notice it. |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
This is more of a specification: The double semicolon |
It seems the same was reported in the still open #8813. Personally I see it as an issue since you cannot cut and paste code from a script into a toplevel prompt and expect the same as if you had run the script. |
How about we finally change this broken specification? :p |
Original bug ID: 6472
Reporter: jrrk101
Status: confirmed (set by @damiendoligez on 2014-07-08T08:49:30Z)
Resolution: open
Priority: low
Severity: tweak
Platform: x86_64
OS: OSX
OS Version: 10.9
Version: 3.12.1
Target version: later
Category: toplevel
Monitored by: @gasche
Bug description
After a certain statement ending in ;; the next tokens are ignored to end of line
Steps to reproduce
Additional information
4.0 series seems affected. Seems to be a parser bug.
The text was updated successfully, but these errors were encountered: