Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From the BBEdit manual (pages 302-304):</p> <blockquote> <p><strong>Using ctags</strong></p> <p>BBEdit allows you to generate and use tags files as text completion sources, and will recognize any tags files associated with your documents.</p> <p>You may place tags files generated via ‘bbedit --maketags’ in the Completion Sources folder of BBEdit’s application support folder (see page 32) for use as text completion sources.</p> <p>[...]</p> <p><strong>Tag Files as Completion Sources</strong></p> <p>You can now add tags files to specific locations to make symbols available as completion data sources when editing in desired languages. In particular:</p> <ul> <li>When you build a (coded) language module, if you place a file named “tags” in the language module’s “Resources” directory, BBEdit will<br> use those tags as completion sources.</li> <li>You can generate a tags file (using exuberant ctags or “bbedit --maketags”) and place the resulting file in Application Support/BBEdit/Completion Data/ /, where “ name>” is the name of the language as it appears in the list of<br> installed languages (or on the Languages popup menu).</li> </ul> <p>So, for example, if you were to generate a tags file for the 10.6 SDK so that you could add completion data when editing Objective-C files, the file would go in Application Support/ BBEdit/Completion Data/Objective-C/. Tags files can be given any appropriate name, so you can have multiple tags files for a single language, and they will all be examined when generating completions.</p> </blockquote> <p>And the Completion Data section on p32:</p> <blockquote> <p><strong>Completion Data</strong></p> <p>This folder does not exist by default, but you may create it. The Completion Data folder contains tags files (or aliases to tags files) which can provide additional text completions for editing documents in the corresponding languages. These tags files should be in the format generated by ‘bbedit --maketags’, and must be placed in subfolders corresponding to their languages.</p> <p>Each subfolder should have the exact name of its language as that language appears in the list of installed languages (or on the Languages popup menu).</p> <p>For example, the subfolder containing a Python tags file must be named “Python”, and the subfolder containing a tags file for ANSI C must be named “ANSI C”.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POBBEdit is not recognizing ctags' tags file
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USsteveax
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, I'd already tried placing them under the Completion Data folder under Ruby and had the same luck (read, none). I've read everything I could find in the user guide about these.
      singulars
      1. PO
      1. UStodd.pierzina
    2. CO@todd.pierzina just a thought, did you try relaunching BBEdit after placing the tags in the completion folder?
      singulars
      1. PO
      1. USsteveax
    3. COYup, restarted every time I tried something different. Thanks for the thought though!
      singulars
      1. PO
      1. UStodd.pierzina
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload