filepro menus and Ctrl-S - maybe Anzio setting?

[Bruce Easton]

On 12/6/10 7:03 PM, Brian K. White wrote:
> On 12/6/2010 6:19 PM, Bruce Easton wrote:
>> "The first character on each of these menus is a Ctrl-S."
>>
>> Not exactly sure how to be any clearer about that part - well it's only once at the top of the file.
> To be fair it wasn't clear to me either.
>
> "on the menu" to me means "displayed to the user by runmenu"
> not in the menu file itself.
Good point.  Yeah - I never mentioned already being in vi in front of 
that paragraph - apologies to all about the confusion.
> The menu file may contain anything since it's a binary format that only
> runmenu reads directly. It's contents only have any bearing on terminal
> behavior in so far as runmenu outputs stuff based on reading the file,
> but runmenu does not cat the file verbatim any more than the kernel or
> shell cats the runmenu binary when you run that.
>
> I didn't know what you meant at all actually. I was thinking "Was the
> menu choice "S" and the users usually press Ctrl-menuchoice to invoke
> them and now the S ones don't work? What does a Ctrl-S, or any other
> byte from 0 to 255, in the the binary contents of the menu files have to
> do with anything?"
>
> It's definitely a weird problem for exactly that reason.
> I can only say I've never seen this behavior even once.
>
> Definitely you want to go over all the things that have a hand in making
> the terminal work from top to bottom, which I know you already know, but
>
> that is too many things and too many possible interactions for me to try
> to write a comprehensive diagnostic recipe here&  now, since, there is
> no right way. It's a big bag of variables and many combinations that add
> up to equally right ways.
>
> Just so I don't leave without saying at least something helpful, I'd
> start by manually setting LANG=C TERM=linux temporarily in a session,
> stty intr '^c', and making sure Anzio is set for linux and cp437.
I think the cp437 is already OK.  But at this site, they already have 
some Linux with Anzio and still use SCO Unix termcap which I don't get - 
it just seems like a mismatch to me.  I guess I should set up a menu 
with nineteen options and see if it's doing the same there (on the older 
box).    I know from my mac, I could never get the SCO termcap to work 
well, so I use xterm.

But thanks for the recommendations, Brian.  We will look further.

Bruce
> That
> should make filepro work assuming a standard stock fp termcap even if it
> doesn't help anything else. Finding the shortest path to making
> everything work will take more description of your system.
>