filepro menus and Ctrl-S - maybe Anzio setting?

[Bruce Easton]

On 12/6/10 5:14 PM, Kenneth Brody wrote:
> On 12/6/2010 3:38 PM, Bruce Easton wrote:
>> A client has a few menus that have nineteen options on them.
>> The first character on each of these menus is a Ctrl-S.  (I think
>> dmakemenu starts at Ctrl-A and then goes up by one - up through the
>> last non-blank option - so on these menus, the nineteenth option
>> is the last option, ergo the Ctrl-S as the first char in the file.)
> [...]
>
> I don't understand what you mean by "the first character on each of 
> these menus is a Ctrl-S".  How do you get a filePro menu option to be 
> a non-printing character?  (And dmakemenu doesn't "start" at anything, 
> except for 24 menu entries into which you decide what to place.)
>
That's what I thought, too.  But, for instance, on one of our Linux 
boxes, for the supplied tutorial menus, "pclient", the first character 
in the file (or at least it shows that way in vi right before "filePro 
Plus Client Menu", there is a ^E.  That menu has four menu options with 
a blank spot in between two of them, so the last non-blank option is the 
fifth spot (ergo I was guessing that maybe five away from ^A correlated 
to that).  If I vi the menu "util", it has a ^G at the beginning of the 
file and it's last non-blank option is in the seventh spot, so after 
checking a few menus, my theory seemed to hold up.

But under Unix - I just get a 'line too long' when trying to vi the menu 
files - that is what I was used to  - I never noticed these control 
chars in Linux and actually being able to see some of the content in 
vi.  Cesar said only a few menus he was working with (on a different, 
client Linux box) would freeze as soon as they came up - the ones with 
nineteen options on them where looking at them in vi on Linux would show 
a ^S at the beginning of the menu file.

Bruce