Exactly! Which is why I continue to use KN. I only use K when calling CQ.
On Tue, 19 Jul 2011 06:29:06 -0700 Matt Zilmer <mzil...@verizon.net> wrote: > KN also tells a breaking station that you're in QSO. So if they creep > up on your signal during the tail end (callsign exchange), the context > is clear. I've always taken KN to mean a context marking rather than > some unfriendly indicator of exclusion. Haven't met any hams that are > like that.... :) > > 73, > matt W6NIA > > > > > On Tue, 19 Jul 2011 08:31:18 -0400, you wrote: > >>bk doesn't bother me so much if it's sent as BK and not _BK_ (i.e. not run >>together). For clarity's sake, if I just end with K I leave an extra amount >>of space so that meaning is clear, per Igor's note below. >> >>I don't ever use _KN_ myself anymore. Mostly because, yes, it's a >>parentheses, but also because all the ARRL books I ever read when I was >>studying back in the '80's, and these books were older than that by some >>amount, said that _KN_ means something like, "I only want a response from the >>other station, no breaking stations please", which doesn't seem terribly >>friendly. > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecraft@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
