On Jan 5, 2009, at 2:28 PM, talklists wrote:
> When I open more than one file, it is opened in the
> drawer, I want to go back to my multiple window method I used to use.
Take a look at Preferences -> Documents & Drawer. Enable the "Open in
a new window" option under the "New & opened documents" heading.
> I see no preference to set line numbers to on by default to
> work around it.
Enable the Preferences -> Text Status Display -> Show line numbers
setting to have line numbers be displayed by default.
> Saved state is not working at all, line numbers and language which I
> set, save, and then open from ftp servers again, are not being
> honored.
When opening remote documents with Interarchy or Transmit, BBEdit's
saved state mechanism will not work because it depends on a consistent
file path to identify the document. When you open a remote document
via FTP or SFTP, Interarchy creates a temporary copy of the file on
your local machine. Because that path is different every time, BBEdit
won't recognize it.
You have a couple options to work around this:
(1) Use Interarchy's FTP Disk feature to sync remote files with a
local directory. Then edit only the local copies since their paths
don't change. Transmit has a similar syncing feature.
(2) Sync your files with a command line tool like rsync and again only
edit the local version.
(3) Use a FUSE-based utility like ExpanDrive to mount your remote
server as a volume in OS X. Then all folders and files will appear to
be local and file paths won't change.
(4) If your server's filesystem is HFS+, you could tell BBEdit to
preserve state information in the file's resource fork rather than in
its central repository. From BBEdit's Expert Preferences Help:
Beginning with version 8.0, BBEdit stores document
state (window position and various settings) in a
central repository in your BBEdit preferences
folder. If you wish, you can ask BBEdit to store
document state in the resource fork of the
document's file:
defaults write com.barebones.bbedit
State:UseResourceFork -bool YES
(5) In most cases, BBEdit can accurately determine a file's source
language automatically. This can be overridden by simply choosing a
different language from the source language menu at the bottom of the
document's window. But, like preserving other state information, it
depends on the file's path for identification.
To work around this, you can add an Emacs local variable to your file
to manually specify a language setting (see page 227 of the User
Manual). For example, placing the following variable at the bottom of
your file would tell BBEdit to interpret the contents as a Unix shell
script, even if the document had no shebang line or filename
extension. Also, the language setting would persist even after
reopening the document with Interarchy because BBEdit doesn't have to
rely on the file path to get this state info.
Local Variables:
mode: unix-shell-script
End:
Note that you must have the Preferences -> Text Files -> Honor saved
state -> Emacs local variables option enabled for this to work.
-Dennis
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "BBEdit Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/bbedit?hl=en
If you have a specific feature request or would like to report a suspected (or
confirmed) problem with the software, please email to "[email protected]"
rather than posting to the group.
-~----------~----~----~----~------~----~------~--~---
