- Use Bike 1.22 (194) on MacOS 15.7.2. (But I experienced the same thing on many, if not all, prior versions of Bike.)
- Expand a TextExpander snippet that has a space (or non-breaking space) at the beginning and/or the end of the snippet.
- Although this class of snippets works flawlessly in other applications, expanding such snippets in Bike trims the whitespace at the beginning and end of the snippet (an undesired behavior).
- Expected behavior: Snippet should expand exactly as it is composed in TextExpander.
- To be sure, this does not seem to be a TextExpander issue. And the snippets’ internal whitespace (i.e., spaces between words in the snippets) is unaffected: spaces between words expand as expected in Bike. The problem is limited to the whitespace at the beginning and end of the snippets.
Is this all whitespace, or is there a difference in behavior between spaces and newlines?
Update Never mind, can reproduce it now…
I was trying to reproduce with Typinator, but that doesn’t have the problem. I now see that TextExpander is using “paste” command to insert text, and Bike trims pasted text, that’ the root of the problem.
I’m unlikely to get this solved in Bike 1.x, but will try to get it solved in Bike 2.
Thanks for doing that.
For the record, new lines get expanded fine — regardless of whether spaces appear before or after the new line. BUT: the spaces still disappear. So:
<space>test<space><new line><space>
expands in Bike to
test<new line>
In other words, the space at the beginning of the line gets removed; the space between “test” and the new line gets removed; a new line is created; and the space after the new line gets removed. Yet:
<space>a test<space><new line><space>
expands in Bike to
a test<new line>
(That is, the internal space in “a test” gets expanded, but Bike trims spaces at the beginning of the line, the end of the line, and both before and after the new line characters.)