Finally figured this out. Here's the exact contents of my tags test file:
!_TAG_FILE_FORMAT 2 /extended format; --format=1 will not append ;" to
lines/
!_TAG_FILE_SORTED 1 /0=unsorted, 1=sorted, 2=foldcase/
!_TAG_PROGRAM_AUTHOR Darren Hiebert /dhieb...@users.sourceforge.net/
!_TAG_PROGRAM_NAME Ex
Alright, all that makes sense but it doesn't seem to be working. Here's what
I've got:
1. A folder called "tags_test" on my desktop.
2. the files "tags" and "tags_test.md" within that folder.
The contents of the "tags" file (with tab separators, as you said):
!_TAG_FILE_FORMAT 2 /extended forma
On Wednesday, September 7, 2011, Oliver Taylor
wrote:
ctags_test *.txt 0;" kind:f access:public
I think you can get away with just:
ctags_test *.txt 0
Make sure that the fields are separated by tabs.
Is the idea that I put this in the same directory as a test file and
"ctags_test"
Thanks Rich, now I know it's possible...
So now I have to get to work on a test. This is what I've got as a tags
file:
!_TAG_FILE_FORMAT 2 /extended format; --format=1 will not append ;" to
lines/
!_TAG_FILE_SORTED 1 /0=unsorted, 1=sorted, 2=foldcase/
ctags_test *.txt 0;" kind:f access:public
On Wednesday, September 7, 2011, Oliver Taylor
wrote:
Here's what I've got so far:
1. A script attached to the save event (or something) scans the
open document for a regex pattern.
2. This script creates a ctags file from the regex matches in
BBEdit's "Completion Data" folder, and adds som
TextMate has a built-in way of creating a custom (and live) completion
parser. You start by telling the completion parser, in regex, what you want
to scan the document for (e.g. /^chapter\s?\d+$/). This creates a list that
TextMate presents in a completion pop-up (it also lets you manually defin
