> 1. It seems that the problem is in the "Identifier and Keyword Character
Class".
I made the suggested change, and now it works with keywords (the ones
defined in the PLIST file are considered "keywords" right?) and clippings
(which I assume are the little "C" in the autocomplete list). I actually
tried using clippings before and already have a clippings file with "Rand"
in it, so Rand now shows up from that clipping file. However, using
clippings means I would have to create hundreds/thousands of individual
files for each character? If so, that seems like an odd way of going about
it. I guess I could make a Python script that generates all those files..
but it seems like having a basic list of character names for each book
makes the most sense (if that's possible). Is there a way to create a
keyword list that is separate from the PLIST file? If creating a list isn't
possible, then I could probably make the clippings thing work, assuming
thousands of clippings files will work and not slow things down.
Also, I still can't get the normal autocomplete to work properly with my
"Shawn" language, which still might be a solution that works good enough.
So how do I go about making it so that autocomplete uses words from the
document when using my "Shawn" language? For example, if I type "Ce" then
it would autofill "Cenn" which is a word found in that sample text, but
that still doesn't work.
Thanks much,
Shawn
On Tuesday, January 18, 2022 at 9:48:42 AM UTC-8 jj wrote:
> Shawn,
>
> 1. It seems that the problem is in the "Identifier and Keyword Character
> Class".
> By specifying *\S* (Anything that is not whitespace) the starting square
> bracket is included in the completion prefix.
> Obviously there is no "[ra..." entry in "BBLMPredefinedNameList".
>
> Try with this:
>
> <key>Identifier and Keyword Character Class</key>
> <string>*\p{Xwd}*</string>
>
> \p{Xwd} is a unicode character class that matches letters, digits and
> underscores.
> The BBEdit keyword parser should now use "ra..." as a completion prefix.
>
>
> 2. BTW, a *completely different but probably easier approach* whould be
> to use *Clippings*. (BBEdit manual p. 315).
>
> Create a directory for the Shawn language clippings:
>
> % mkdir -p ~/Library/Application\
> Support/BBEdit/Clippings/Shawn.shawn/
>
> Inside that directory create a file named "ys".
> and inside that file paste this content: "We all live in a yellow
> submarine."
>
> % echo "We all live in a yellow submarine." > ~/Library/Application\
> Support/BBEdit/Clippings/Shawn.shawn/ys
>
> The "ys" entry should now appear in the completion menu after you type a
> "y" in a Shawn language document .
>
> This approach *doesn't need* you to restart BBEdit.
> Just keep adding clipping files to the Shawn.shawn/ directory.
> The name of the file should be the abbreviation, the contents of the file
> should be the replacement string.
>
> HTH
>
> Jean Jourdain
>
>
--
This is the BBEdit Talk public discussion group. If you have a feature request
or need technical support, please email "supp...@barebones.com" rather than
posting here. Follow @bbedit on Twitter: <https://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 bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bbedit/915dc65f-66d7-4b84-862d-3f14c62247dfn%40googlegroups.com.
