# Keyboard Characters not the same?

**URL:** <https://community.allstarlink.org/t/keyboard-characters-not-the-same/17062>\
**Category:** AllStarLink\
**Created:** [May 28, 2020, 7:54pm UTC](https://community.allstarlink.org/t/keyboard-characters-not-the-same/17062 "2020-05-28T19:54:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [May 29, 2020, 1:41am UTC](https://community.allstarlink.org/t/keyboard-characters-not-the-same/17062/2 "2020-05-29T01:41:20Z")

</div>

See if this post helps with that:

> [@OK...Not showing up in stats, but IAX2 shows registered](https://community.allstarlink.org/t/ok-not-showing-up-in-stats-but-iax2-shows-registered/17009/3):
>
> I ran into the double hyphen problem just a couple of days ago. Here’s how to fix it on MacOS [https://www.tjvantoll.com/2015/11/13/em-dash-and-hyphens/](https://www.tjvantoll.com/2015/11/13/em-dash-and-hyphens/) Also, I found that waiting about 5 seconds before typing the second hyphen will work. P.S. I was surprised that I never had run into this before, then realized I recently switched to zsh. Still, it seems weird that would impact cli on remote Linux boxes.

---

_[View the full topic](https://community.allstarlink.org/t/keyboard-characters-not-the-same/17062)._