|Summary:||Smart Quotes prevents using strings in the REPL|
|Product:||Workbooks & Inspector||Reporter:||Matisse Hack <matisse.hack>|
|Severity:||normal||CC:||inspectordev-discuss, sandy, woodjon|
|Tags:||Is this bug a regression?:||---|
|Last known good build:|
Description Matisse Hack 2015-11-04 17:45:31 UTC
Created attachment 13675 [details] Proof By default "Smart Quotes" is turned on inside the REPL. One can disable it through Edit > Substitutions > Smart Quotes, but by default you get some funny errors since the double quote is replaced by a version of the double quote that is slightly skewed. Therefore writing: > selectedView.Text = “hi"; returns the error: (1,22): Unexpected character `“' After turning off Smart Quotes, typing: selectedView.Text = "hi"; works just fine (note the first quote in that line is no longer angled slightly). Easy fix, but people might not know to turn off this option.
Comment 1 Sandy Armstrong [MSFT] 2015-11-04 17:58:17 UTC
I wonder if this is coming from a global setting; we haven't seen it yet. Thanks for finding it!
Comment 2 Matisse Hack 2015-11-04 18:16:08 UTC
Yes, I believe so. I have never touched it before though so it must be the default setting for everybody.
Comment 3 Sandy Armstrong [MSFT] 2015-11-04 18:25:26 UTC
Clearly not for *everybody*, but regardless, I'll make sure we're ignoring it in the REPL.
Comment 4 JW 2015-11-05 11:47:02 UTC
I've noticed this, as well.
Comment 5 Sandy Armstrong [MSFT] 2015-11-05 14:04:31 UTC
In System Preferences > Keyboard -> Text, is "Use smart quotes and dashes" checked? I'm working on a fix, but want to make sure that that's the difference in our systems.
Comment 6 Sandy Armstrong [MSFT] 2015-11-05 14:26:39 UTC
Interesting...we do actually already disable this, but it only appears to take effect starting with the second run.
Comment 7 JW 2015-11-05 15:01:29 UTC
"In System Preferences > Keyboard -> Text, is "Use smart quotes and dashes" checked?" Yep, it's checked for me.
Comment 8 Matisse Hack 2015-11-05 18:22:58 UTC
Checked for me as well. And I did notice that it seems to fix itself on subsequent launches.
Comment 9 Sandy Armstrong [MSFT] 2015-11-13 12:34:22 UTC
First run experience will be fixed in next release.