Steve, Thanks for sharing! I looked up PyCharm, and found it's PHPStorm for Python. (a day after reading this did I get the pun in the name)
Grail, Tell me more about this "make tags" I've read about exuberant ctags in the past, and I'm still not sure what they're for (probably because I'm not a proper programmer). From what I can tell, you run the CLI command and BBEdit will scan your (project?|document?) for things it can put into auto-complete suggestions? Will that work for HTML/CSS projects, as well? Breaking away from Python for a moment, and into my day job… The area I always felt BBEdit lagged in web coding is in the intelligence of it's autocomplete. Coda, for example, does autocomplete much better for HTML and CSS properties and attributes. And, ideally, each time I went to enter a class or ID, I'd really want an autocomplete to know what classes and IDs I've already used in other docs in the project, especially those you've already coded into a css, scss, or sass file, and suggest them. Can ctags help with that? ~b On Wednesday, March 12, 2014 9:40:37 PM UTC-4, Grail wrote: > > For me the number one tip for working with any codebase in BBEdit is to > remember to run “bbedit --maketags .” whenever you finish a round of > editing. Then you get the right-click->definitions->source goodness. > > I have PHPtidy and Perltidy text filters, but strangely enough I don’t > have a Python tidying script. > > Alex > > -- This is the BBEdit Talk public discussion group. If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].
