-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] HTML code complete blocks (a bit) adding comments #1562
Comments
If we're going to add !, then we should have it as "!--" so that you don't need to type two dashes after you select. |
Sounds smart. To be clear, even if you don't add !, it should at least On Sat, Sep 8, 2012 at 12:05 PM, Raymond Lim notifications@github.comwrote:
Raymond Camden, Adobe Developer Evangelist Email : raymondcamden@gmail.com |
Oh, I didn't realize that you're having the issue of unable to type ! (#1394). This has been fixed about 3 weeks ago. If you have Sprint 13, then you won't have this issue. |
I'm seeing it with 13. To be clear, if I wait or dismiss the autocomplete I
|
FWIW, I can't reproduce this in the Sprint 13 build on Mac (just did a clean install). |
I've only tested it with HTML files. On Tue, Sep 11, 2012 at 2:48 PM, Narciso Jaramillo <notifications@github.com
Raymond Camden, Adobe Developer Evangelist Email : raymondcamden@gmail.com |
Actually, nj meant to say Debug > Show Extensions Folder. We did make some changes in Sprint 14 and he was referring to the Help menu only available in Sprint 14. Also, in case your Sprint 13 is using your github clone of brackets, you can relaunch Brackets with holding down Shift key. If you launch with Shift key, then Brackets will prompt you to select index.html file from your sprint 13 installed folder. Default installed folder is C:\Program Files (x86)\Brackets Sprint 13\www. |
I'm using the DMG install - so no source folder at all. (afaik) On Wed, Sep 12, 2012 at 12:31 AM, Raymond Lim notifications@github.comwrote:
Raymond Camden, Adobe Developer Evangelist Email : raymondcamden@gmail.com |
Reviewed - |
You can also use Raymond's trick -- choose Debug > Show Extensions Folder -- and double check that the folder you see is inside the .app (rather than pointing at some other copy of the Brackets src that you have on your system). |
Boom - that did it. So this was all a non-issue, right? Sorry if so - and On Wed, Sep 12, 2012 at 12:18 PM, Peter Flynn notifications@github.comwrote:
Raymond Camden, Adobe Developer Evangelist Email : raymondcamden@gmail.com |
Not your fault--the transition to the new shell has been a little rocky because of the way we manage which folder it's pointed at. We've changed things now to remove the keyboard shortcuts--now the installed build will always just run off its installed content unless you run a shell script that points it explicitly at your dev folder (and there's another shell script that points it back at the installed content), so it should be more obvious when you're doing which. (We should also add something in the UI that shows when you're running off a dev folder, but that might be next sprint :)) |
Well, the issue was really a developer-level usability problem: #1536. Will be fixed in the next build. |
Closing as UTR |
Hey |
Not for another 4 minutes :-) |
Saturday Sep 08, 2012 at 14:44 GMT
Originally opened as adobe/brackets#1600
I noticed lately that I keep screwing up my HTML comments. So instead of doing
The text was updated successfully, but these errors were encountered: