Unfortunately after upgrading BBEdit from 9.6.3 to 11.0.1 it seems that 
per-directory settings are now gone or broken. I've tried the commands to 
enable the feature as mentioned in the 10.1.1 release notes 
<http://www.barebones.com/support/bbedit/arch_bbedit1011.html>:

>
>    - 
>    
>    Scanning for .bbeditSettings files is now *off* by default, gated on 
>    an expert preference. The feature is deprecated, so don't get too attached 
>    to it because it's going to go away for good in a future version. 
>    Meanwhile, if you rely in it, please let us know how you use it, and you 
>    can turn it back on using an expert preference:
>    
>    defaults write com.barebones.bbedit EnableSettingsScan -bool YES
>    
> but this no longer seems to have an effect.

During years of using BBEdit 9.6 I've been relying on .bbeditSettings files 
like this to keep my white-space correct for each project:
[Editor]
AutoExpandTabs = 1
DefaultTabWidth = 2



If this feature is truly gone is there any other way to set the "Auto 
Expand Tabs" and "Tab Width" for a collection of files? I work on many 
open-source projects in the same language (PHP) and they all have different 
coding standards related to tabs versus spaces. This feature was a saving 
grace for not messing that up.

Best,
Adam

On Wednesday, November 10, 2010 1:06:20 PM UTC-5, Adam Franco wrote:
>
> Thanks Rich, it is now working as I hoped. This is a fabulous feature! 
>
> Thanks again for you prompt help. 
>
> - Adam 
>
>
> On Nov 10, 12:16 pm, Rich Siegel <[email protected]> wrote: 
> > On Wednesday, November 10, 2010, Adam Franco 
> > 
> > <[email protected]> wrote: 
> > >However, when I copy to the drupal.bbeditSettings file to a directory 
> > >on a SMB share, then it doesn't get used by BBEdit. I've also tried 
> > >copying my entire test directory to an SMB share and the settings file 
> > >doesn't get used there as it does when it is on my local drive. 
> > 
> > Correct - this is done by default for performance reasons, but 
> > you can enable it. Here's the excerpt from the 9.6 change notes: 
> > 
> >      When editing files that are on remote file servers (AFP, NFS, 
> >      SMB, etc), BBEdit will no longer look for directory-relative 
> >      tags files or settings files. This is a particular performance 
> >      win when the file is located on a volume mounted via MacFUSE/SSH 
> >      or similar, or if the file server is over a slow or high-latency 
> >      link. 
> > 
> >      To re-enable scanning for tags or settings files, use these 
> >      separately or together: 
> > 
> >      defaults write com.barebones.bbedit 
> > Misc:DisableCtagsScanOnRemoteVolumes -bool NO 
> > 
> >      defaults write com.barebones.bbedit 
> > Misc:DisableSettingsScanOnRemoteVolumes -bool NO 
> > 
> > >3. The EntabWidth, DetabWidth, and TidySpacesPerTab don't seem to have 
> > >any effect, but I don't really need these settings anyway. 
> > 
> > Not all settings are loaded from directory-specific files. 
> > Unfortunately there is no documentation of which ones are and 
> > which ones aren't, so you'll need to try the ones you care about 
> > -- but in general, settings which affect the display and editing 
> > behaviors and are remembered with a document's state can be 
> > changed with directory specific prefs, and most others cannot. 
> > 
> > R. 
> > -- 
> > Rich Siegel                                 Bare Bones Software, Inc. 
> > <[email protected]>                      <http://www.barebones.com/> 
> > 
> > Someday I'll look back on all this and laugh... until they 
> > sedate me.

-- 
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].

Reply via email to