[Dxspider-support] SH/DX not working as expected
Martin Davies G0HDB
marting0hdb at gmail.com
Fri May 3 15:00:36 BST 2024
I recently wanted to check whether the station JG8NQJ/JD1 had been spotted on the
DXCluster.
The DXSpider Command Reference information for the sh/dx command includes the
following:
<prefix> - for a spotted callsign beginning with <prefix>
*<suffix> - for a spotted callsign ending in <suffix>
*<string>* - for a spotted callsign containing <string>
I found that when I entered 'sh/dx JG8NQJ' I got a list of spots of JG8NQJ/JD1, as would be
expected, but when I tried either 'sh/dx *JD1' or 'sh/dx *JD1*' the system returned a 'not
found' message.
Has the syntax for searching for partial callsign strings changed, or is there a bijou bug in the
sh/dx command that's preventing the correct return of spots that contain a specified suffix or
string?
--
73, Martin G0HDB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240503/c132ddb9/attachment.htm>
More information about the Dxspider-support
mailing list