In a message of , andrew clarke (3:635/728.4) writes:

 >>The only thing I can't make work yet is Home and End.  Instead of
 >>"First Msg in Thread" and "Last Msg Read", the
message pointer shoots
 >>to Message #1 and the Last Message in the Area.  Any clues?  This
 >>feature used to work in v2.1.

In this 1.99L version, there is no "First Msg in Thread", thread
reading is done with the CTRL + left and right arrows.  "Home"
exits thread reading and takes you where you entered 'thread reading', but
hitting  while thread reading takes you to the 'Next Msg', and
aborts 'thread reading'.  If you were lucky enough to be at your
"highest read" when you entered 'thread reading', then 'END' will
get you back there.

 ac>I've never used Msged 2.1, but I think I know what you want.  Put the 
 ac>following in MSGED.CFG (be sure to replace any existing ReadKey 
 ac>commands with the same 0xNNNN value):

 ac>ReadKey 0x4700 Home
 ac>ReadKey 0x4F00 Last

 ac>Looking at the source code, it looks as though the above is actually 
 ac>the default setting for ReadKeys 0x4700 (the `Home' key) and 0x4F00 
 ac>(the `End' key).  I'm guessing you may be unknowingly using the 
 ac>Home/End ReadKey redefinitions that were provided in the Msged 4.10 
 ac>sample MSGED.CFG, which override the defaults.

 ac>I just tested the "Home" ReadKey function, and it doesn't
seem to be 
 ac>doing what it's supposed to.  Or doing anything at all.  Not even in 
 ac>Msged 4.00.  I think I need a copy of 2.1 to find out what it's 
 ac>supposed to do.

Functional or not, it _does_ appear that someone's been trying to make
those items 'individually definable'.    :-)

      Good luck...  M.

--- msged 1.99L MSC