Guest User

Untitled

a guest
Feb 20th, 2018
64
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.90 KB | None | 0 0
  1.  
  2. The "Find in Reference..." command (on the Search Menu) now supports language-specific templates for on-line references. The old default of the Apple Developer Connection is still the factory default; for PHP, "Find in Reference" will look up the selected symbol on php.net; for Unix Shell Script, it'll open the appropriate Unix man page.
  3.  
  4. The URL templates are customizable in the Languages preferences; click the "Options" button to edit the URL template (along with other language-specific settings, such as the comment delimiters). Note that the URL can be any well-formed URL of any scheme supported by the OS or installed applications. (Witness the above x-man-page:// usage.) The string "__SYMBOLNAME__" (without the quotes) is replaced where it occurs in the template.
  5.  
  6. BBEdit accomplishes this by introducing two new URL schemes: "x-perldoc" and "x-pydoc". In a fashion analogous to the "x-man-page" URL scheme, these new URL forms provide a shim to the "perldoc", "pydoc", and "ri" commands. At this writing, the only forms supported are for generic lookups:
  7.  
  8. x-perldoc://lookup/symbolname
  9. x-pydoc://lookup/symbolname
  10. x-rubydoc://lookup/symbolname
  11.  
  12. In future, it may be possible to substitute other words where "lookup" is to provide finer control over perldoc, pydoc, and ri.
  13.  
  14. When sent to BBEdit, these URL forms trigger documentation lookup and display (the results are in BBEdit itself).
  15.  
  16. If desired, other applications may register to handle these URL schemes; if so, it will serve everyone's interest if the URL forms are mutually agreed upon, documented, and implemented.
  17.  
  18. ----
  19.  
  20. There's a new setting in "Text Files: Saving" preferences: "Save auto-recover info every...". This setting controls whether, and at what frequency BBEdit saves auto-recovery information for unsaved open documents.
  21.  
  22. If auto-recovery information is stored (it'll always be in ~/Library/Application Support/BBEdit/Auto-Save Recovery/), then at next launch, BBEdit will reopen and restore the contents of any documents for which recovery information exists.
  23.  
  24. The "interval" setting controls the frequency with which this information is written out; the shorter the interval, the smaller the window for data loss in the event of a system crash, but the more frequently your disk will be used (the latter being a consideration for laptop users running on battery). The factory default interval is ten minutes.
  25.  
  26. Auto-save recovery can ensure that all is not lost in the event of a disaster, but will not protect you against events that render your disk unreadable, nor is it a substitute for manually saving a document after making a very important change to it.
  27.  
  28. ----
  29.  
  30. BBEdit now supports "camel case" navigation: press Control-left-arrow or Control-right-arrow to jump to the next (or previous) transition from lower-case to upper-case characters (or a word boundary, whichever comes first).
  31.  
  32. Note that this use of Control-left-arrow and Control-right-arrow replaces the old behavior of using these key combinations to scroll horizontally. If you prefer the old behavior, you can do the following from the command line:
  33.  
  34. defaults write com.barebones.bbedit Editor:ControlArrowCamelCase -bool FALSE
  35. defaults write com.barebones.bbedit Editor:ControlArrowHScroll -bool TRUE
  36.  
  37. ----
  38.  
  39. There's a new collection of settings in the Editing: General preferences: "Soft wrapped line indentation". These control how the soft-wrapped portions of a long line are indented: Flush Left (not at all); First Line (same as the first visual line of the wrapped line); and Reverse (one tab stop's worth of hanging indent). The factory default is "First Line", and changes to these preferences take effect immediately.
  40.  
  41. ----
  42.  
  43. If a file contains no cues to indicate its text encoding (for example, Emacs variables, HTML/XML character set declaration, saved state, BOM, etc), BBEdit will attempt to interpret it as UTF-8 (No BOM), before giving up and asking you what to do.
Add Comment
Please, Sign In to add comment