[RTTY] What abt LINE feed

[Tom - KE1JF]

This is my standard exchange in N1MM and wondering if anything should be 
changed. It looks ok on my screen but I never really see what everyone else 
prints.

{TX} {CALL}  599  {EXCH}  {EXCH}  DE  {MYCALL}{RX}

73,
Tom, KE1JF


----- Original Message ----- 
From: "Dave Hachadorian" <K6LL at ARRL.net>
To: "RTTY Reflector" <rtty at contesting.com>
Sent: Tuesday, January 05, 2010 8:09 AM
Subject: Re: [RTTY] What abt LINE feed


> You have it correct, Larry. SPACE at the end of all your macros,
> not a linefeed. If the last word in your macro is a callsign,
> better add TWO spaces, because Writelog needs two extra
> characters before it highlights a callsign. Linefeed at the
> beginning of a macro is OK.
>
> Dave Hachadorian, K6LL
> Yuma, AZ
>
>
> ----- Original Message ----- 
> From: "RW4WZ" <rw4wz at udm.net>
> To: "'RTTY Reflector'" <rtty at contesting.com>
> Sent: Tuesday, January 05, 2010 9:42 AM
> Subject: Re: [RTTY] What abt LINE feed
>
>
>>
>>
>>> -----Original Message-----
>>> From: rtty-bounces at contesting.com
>>> [mailto:rtty-bounces at contesting.com] On Behalf Of Dave
>>> Hachadorian
>>> Sent: Tuesday, January 05, 2010 4:12 AM
>>> To: RTTY Reflector
>>> Subject: Re: [RTTY] What abt LINE feed
>>>
>>> N1MM does strip excessive line feeds, but not the first one.
>>> For example, if the sender's macro is 599 GA-linefeed, the GA
>>> may jump up from under your mouse pointer. You may think you
>>> have clicked on GA, but the contact won't be logged, because
>>> the state is missing. If you are doing two radios, you may
>>> not notice this right away, and after a few minutes on the
>>> other radio, you come back to find an unlogged qso with the
>>> state missing. Then you have to scroll back and see what
>>> state the guy was in.
>>>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>