Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
remove auto-correct when full command/text-to-correct is typed
See original GitHub issueif you dont use auto-correct and just type out a command, like /part, you need to hit enter twice. Auto-correct should notice when you type a full command
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Turn AutoCorrect on or off in Word - Microsoft Support
Go to File > Options > Proofing and select AutoCorrect Options. Autocorrect options button on the Proofing dialog. On the AutoCorrect tab, select...
Read more >How to Turn Off Autocorrect on a Windows Computer
1. Click the Windows "Start" icon and scroll the apps list until you see "Settings." Select it. · 2. Choose "Devices." · 3....
Read more >Too Many Autocorrect Fails? How to Tweak Your Keyboard ...
From the keyboard settings screen, tap Text Replacement and select the + icon. Type in the phrase, then add the corresponding shortcut. For ......
Read more >How to turn off autocorrect and predictive text on Android
If you're in this shoe, follow the simple steps below to disable autocorrect on Android, and gain full control over your text.
Read more >How to use Auto-Correction and predictive text on your iPhone ...
Tap Keyboard Settings, then turn on Predictive. Or go to Settings > General > Keyboard, and turn Predictive on or off. See a...
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 Free
Top 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
For commands, yes because there is no reason not to have a space after that. Not after channels for the same reason that we don’t add a space after nicks.
This is mildly related to #2100 bug. We could fix both of these by inserting a space after completing commands and channels. Would that be fine?