On Dec 27, 1:31 pm, consiglieri <apelsi...@gmail.com> wrote: > Can anyone give me a helping hand or tip with > regards to this? What i tried was the following > > sudo bbedit --maketags /Developer/SDKs/MacOSX10.7.sdk/System/Library/ > Frameworks/Python.framework/Versions/2.7/
I tried this, and it ended up creating a tags folder in /Developer/ SDKs/MacOSX10.7.sdk/System/Library/ > Frameworks/Python.framework/Versions/2.7/ (Perhaps you were expecting it to > be created in your current directory?) Disadvantage of generating this file? It's actually a ctags file for the Python C API (what's in that folder). That's not exactly what I expected (I expected a listing of the items in the Python standard library...) I think you actually want to run bbedit --maketags in the /System/ Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 directory :) PS: What I've done in the past to generate a Python ctags file is to download Django's code (the Python framework I'm using for this client), and run ctags in that directory. It's not the whole standard library, but it was good enough for my purposes. (And a lot smaller than generating the entire Python Standard Library, which generated a 3.1 MB ctags file). Hope this helps, _Ryan Wilcox -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "supp...@barebones.com" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
