filepro menus and Ctrl-S - maybe Anzio setting?

[Bruce Easton]

(bottom)

On 12/6/10 6:03 PM, Kenneth Brody wrote:
> On 12/6/2010 5:32 PM, Bruce Easton wrote:
>> On 12/6/10 5:14 PM, Kenneth Brody wrote:
> [...]
>>> 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 just means that there are 5 menu items in use.
>
>>  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
>
> Which just means there are 7 menu items in use.
>
>> 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.
>
> filePro menus aren't text files.  Bringing them up in a text editor is 
> not advisable.  Certainly, saving them from a text editor is a "Bad 
> Thing"[tm].
>
>> But under Unix - I just get a 'line too long' when trying to vi the menu
>
> Again, "don't do that".  Vi is a text editor, and menus are not text 
> files.
>
>> 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.
>
> Well, I don't know why that would freeze things, unless your version 
> of vi actually sends a Ctrl-S, rather than displaying "^S".
>
> But, this has nothing to do with _using_ a menu, as implied in your 
> original post.  Rather, it has to do with attempting to treat a 
> non-text file as a text file.
>
OK - let me try to simplify:

The behavior on the client menu is that it freezes as soon as the menu 
is run from option G - and only for the menus that have 19 options on them.

In my investigation of this (not even on the client's site by the way, 
but on one of our Linux boxes), I went into vi and notice this 
correlation about this control char visible at the top and the number of 
options.  Nothing is freezing up during my investigation.

At this point, I'm sure there must be some problem with the termcap, OS 
terminal configuration, something other than filepro or Anzio - it has 
to be.

In my inital post I say:

"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.

Since I'm seeing these control characters for the first time in vi,
it would be helpful to know - does filepro put the control character there or not?

I see you're now talking about vim which I will try.

Bruce