Whitespace is inserted for signature placeholders
See original GitHub issueEverytime I edit my signature and use the “Insert placeholder” feature a whitespace is added in front of it.
Example:
I have written Cache count:
and select to insert [NUMBER] this will result it Cache count: [NUMBER]
instead of Cache count:[NUMBER]
Issue Analytics
- State:
- Created 10 years ago
- Reactions:1
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Use placeholders to personalize email signatures - CodeTwo
Inserted placeholders are surrounded with curly brackets/braces { } to be recognized by the program. ... This leads to empty spaces in the...
Read more >Add a signature line - Microsoft Support
You can create a signature line by underlining blank spaces. The best way to do this depends on whether you want to print...
Read more >CodeTwo tutorial: Create a professional email signature ...
This step-by-step video guide shows how to quickly design a company-wide email signature with CodeTwo Email Signatures for Office 365, ...
Read more >Company-wide email signatures & disclaimers in Office 365
Step-by-step guide on how to set up automatic organization-wide email signatures in Office 365 with users' personal data and HTML elements.
Read more >Active Directory Placeholders in Email Signature - Sigsync
Because User B does not have a number in that field in AD, he will have a blank space for the faxNumber field...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I guess one main difference is also, whether one uses the placeholder from the dropdown while typing his logs or he uses them in his signature. At least when used in the signature thr user would expect the signature to be inserted as he defined it, not adding whitspaces for the placeholders. He could easily do this in the signature template if required.
Having a blank there is the typographically correct way, at least for English and German. That’s why this should stay as is. You are also not complaining about your Swipe keyboard inserting blanks between words, so why do you complain here? If you feel this is wrong for other languages, then please add conditional code depending on the language.
I really want to have c:geo stand up against the general trend of people ignoring all rules of grammar, capitalization, punctuation, typography… en masse on the Internet.