0
Not a bug

On a D72 you can not enter k@ as a shortcut for k1.

Sander Pool fa 12 anys updated by Winlink Moderator fa 12 anys 1
Wnlk-1 says the message number is incorrect. No big deal but below it suggests that should be possible. Maybe list as caveat that '1' always needs to be explicit.

APRSLink is great, thanks a lot!

Answer

Answer
Not a bug
The help does not mention the use of "@" only letter keys:


"APRSLink is tailored to fit the needs of remote TH-D7 and TM D700/710 users, but is fully functional for other clients as well. To allow easy entry using the D7 or D700/710 keypads, you can use a keypad letter instead of a number for the second part of commands that require message line numbers. For example, to read message 3 you can send Rd instead of R3; use Rj for message 5, etc. Actually, any letter on the key will be interpreted as the number on that same key for any command that uses a number following the command character."

Not a bug
The help does not mention the use of "@" only letter keys:


"APRSLink is tailored to fit the needs of remote TH-D7 and TM D700/710 users, but is fully functional for other clients as well. To allow easy entry using the D7 or D700/710 keypads, you can use a keypad letterinstead of a number for the second part of commands that require message line numbers. For example, to read message 3 you can send Rd instead of R3; use Rj for message 5, etc. Actually, any letter on the key will be interpreted as the number on that same key for any command that uses a number following the command character."

Answer
Not a bug
The help does not mention the use of "@" only letter keys:


"APRSLink is tailored to fit the needs of remote TH-D7 and TM D700/710 users, but is fully functional for other clients as well. To allow easy entry using the D7 or D700/710 keypads, you can use a keypad letter instead of a number for the second part of commands that require message line numbers. For example, to read message 3 you can send Rd instead of R3; use Rj for message 5, etc. Actually, any letter on the key will be interpreted as the number on that same key for any command that uses a number following the command character."

I see two possible positive reactions to my comment:
  • Take the opportunity to spend 10 seconds to improve the documentation with "You always need to use the number 1 because we can't recognize '@' as 1."
  •  Enhancing the code so it complies with the spirit of what the documentation says so it will interpret '@' as 1.

It is unfortunate you chose to hide behind semantics.