Topic: https://brettterpstra.com/2011/03/23/additional-characters-for-textexpander/
hide preview

What's next? verify your email address for reply notifications!

pax 13y, 128d ago

Great bundle, I used to have a page up http://goo.gl/9kIcT for handy snippets but this saved touching the mouse.

I have 2 suggestions:
› adding and · to the list (&rsaquo and ·)
› and adding an index - I have added ,,chars which gives me the whole content of your characters bundle - in case I forget some shortcodes.

hide preview

What's next? verify your email address for reply notifications!

Dwight Zahringer 13y, 361d ago

Dr. Drang has a good point. A standard would be cool to have that we could all adopt.

hide preview

What's next? verify your email address for reply notifications!

Dr. Drang 13y, 361d ago

I've had a Symbols set for quite a while that uses my preferred system of "semicolon-abbreviation," e.g., ";cmd" for ⌘, ";opt" for ⌥, and so on. It's not nearly as extensive as your Characters set, but it does have a few things your set is missing: ";times" for ×, ";1/2" for ½, and similarly for the other fractions.

Since people have different preferences for their prefix character(s), I wonder if maybe we could establish a standard for distributing TextExpander files in which the prefix is given by something odd like "PREFIX." Then a simple Perl, Python, or Ruby script could change PREFIX to the end user's preference before it's opened in TextExpander.

remark link
hide preview

What's next? verify your email address for reply notifications!

Brett 13y, 361d ago

That sounds brilliant.

@plovs has started up te-snippets.com to start gathering snippet collections in one place. It's not fleshed out yet, but it's a good beginning. What would be awesome is to have a download setup where it asked you for your preferred prefix and adjusted the file prior to download. The only problem is that it would break the install from URL functionality for hosted groups. Unless… you gave out custom URLs that bounced a prefix string off of a script and then spit out the XML. That wouldn't actually be too difficult. Consider your suggestion duly noted.

hide preview

What's next? verify your email address for reply notifications!