be an issue (at least on my BBS system) with the Mystic Full Screen Message Editor where I cannot input things like apostrophies, quote
marks, tildes or any such. The strange thing is that the more general
ones like exclamation, hash, the @ sign, and the various types of
brackets all work fine. Is there a character setting in Mystic that I
be an issue (at least on my BBS system) with the Mystic Full Screen Message Editor where I cannot input things like apostrophies, quote marks, tildes or any such. The strange thing is that the more general ones like exclamation, hash, the @ sign, and the various types of brackets all work fine. Is there a character setting in Mystic that I
So " " quote work for me as do ' and `
Hello All,
I do not know whether other people have noticed this, but there seems to be an issue (at least on my BBS system) with the Mystic Full Screen Message Editor where I cannot input things like apostrophies, quote marks, tildes or any such. The strange thing is that the more general ones like exclamation, hash, the @ sign, and the various types of brackets all work fine. Is there a character setting in Mystic that I have to change in order to fix this? I find it quite frustrating not having at least the apostrophy available, it is amazing how irritating it is if you cannot do a good can&t (ampersand instead of apostrophy), but instead have to do a [cannot] or [do not]. In interferes with muscle memory! :-(
As it turns out, the issue seems to be terminal-related. If I am in syncTerm or Netrunner, it is an issue. If I'm in the Message Editor via SSH and running mystic directly, the problem does not manifest. It seems that I will have to play around with different fonts.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 3 |
Nodes: | 8 (0 / 8) |
Uptime: | 141:45:57 |
Calls: | 2,129 |
Calls today: | 2 |
Files: | 11,149 |
D/L today: |
29 files (9,998K bytes) |
Messages: | 951,086 |