Warning about syntax parsing in Version 3.0b21 (21)
I was trying to create a horizontal rule tag, by using three consecutive asterisk characters. I have auto-pairing enabled, so after typing one asterisk, I had two, and after typing a second, I had four. I only wanted three, though, so I deleted the fourth manually, with the backspace key. This triggers the parser warning.
- Composer_Parser_Error.txt 2.53 KB
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Fletcher on 19 Feb, 2015 05:11 PM
This has already been fixed. Make sure you're using the latest version
so you can take advantage of the latest improvements.
Thanks for helping me improve Composer!
Fletcher
2 Posted by Joshua Hamilton on 19 Feb, 2015 05:37 PM
Sorry for this. But before sending the bug report, I used the check for updates feature, and it didn’t find an update. Is this feature not working in the beta?
—
Josh
Support Staff 3 Posted by Fletcher on 19 Feb, 2015 06:09 PM
What version are you using? Is it really 3.0b21? The most recent
version or two includes the version in the error report, which was not
present in the message you sent.
3.0b (26) is the latest version. The check for updates works (I check
it with every release).
3.0b (21), assuming your subject line is correct, was almost 2 weeks ago.
F-
4 Posted by Joshua Hamilton on 19 Feb, 2015 06:12 PM
When I first checked, check for updates was greyed out in the menu bar. And I copied and pasted the version information from the about screen.
It's working now. I downloaded a new copy from the link in my email, and then I successfully updated with the "check for updates" feature. I’m now on (26).
—
Josh
Support Staff 5 Posted by Fletcher on 19 Feb, 2015 08:13 PM
If you're on 10.10, try rebooting your computer. I've noticed some
strange behavior that seems to resolve with a reboot. It's been there
for at least the last two versions of 10.10, and maybe since 10.10
itself (I didn't update my main machine for a while, and use my test
machine rarely.)
F-