Fri May 02, 2014 9:34 am |
Replies: 12 |
Views: 8106 |
|
|
Yeah, case in point: the new carbon theme. It's a step in the right direction, but only a half-hearted one.
|
Thu Apr 24, 2014 9:25 am |
Replies: 5 |
Views: 2667 |
|
|
Very nice on the eyes. I had trouble with your link, so I've created this one; it points to your page.
_http://goo.gl/j98F1A
|
Wed Apr 16, 2014 7:37 am |
Replies: 12 |
Views: 8106 |
|
|
[citation needed]
If that's true, it's a step in the right direction, but unless they allow users to customize the experience, it's not likely that anyone will be completely pleased with the result ...
|
Tue Apr 15, 2014 10:09 am |
Replies: 12 |
Views: 8106 |
|
|
+1
I fully support this option.
|
Thu May 31, 2012 7:26 am |
Replies: 4 |
Views: 3623 |
|
|
I am using win7 64-bit. I have installed the TFS power tools; I am able to use them in explorer but they do not show up in the Shell Menu inside PhpEd. I know there have been some issues with 64-bit ...
|
Wed Jul 22, 2009 7:29 am |
Replies: 5 |
Views: 5359 |
|
|
That's great and all, but it's still annoying to try to edit 100+ lines of javascript inside {literal} tags without syntax highlighting. Surely I'm not the only one with that problem.
|
Tue Jul 21, 2009 5:00 pm |
Replies: 5 |
Views: 5359 |
|
|
Thanks for the info. I got the standard "working as intended" reply from my bug report email that I expected. I still think it should follow dynamic highlighting rules though.
|
Mon Jul 20, 2009 8:50 am |
Replies: 9 |
Views: 3724 |
|
|
And the motion carries. I like this when coding but having it occur in comments is just plain annoying.
|
Sun Jul 19, 2009 7:37 am |
Replies: 5 |
Views: 5359 |
|
|
There seems to be a bug in how the editor handles code entered between Smarty's {literal} {/literal} tags. It is displayed as non-smarty text even with dynamic highlighting disabled. HTML code outsi ...
|