FilePro from Linux xterm or other terminal?
John Esak
john at valar.com
Tue Aug 10 01:31:35 PDT 2010
Hey, I like Bruce's Comments Inline Belov... We could shorten that to just
CIB at the top of anything that might be questionable.
And since I'm at the top of a very long interspersed thing I'll just finish
my comments up here.
1. I don't see how any setting for Putty xcould affext filePro alerting you
to changing a screen from mono to color (or vicce versa). That's just a
matter of reading the file and alerting one way or the other isan't it?
You'r not changing the screen files by the PUTty settings.
2. On termdcaps for ansi, I've always set the EOF character to a period with
th3e GZ vcalue. I don't see how a ~ does this, but so be it. For those
locked into using Windows, there is a filePro variable called PFEOF to set
the character you want.
3. Boy wouldn't this all be easier if Bob Rasmussen just did all the work he
did on Anziowin for a Linux desktop! :-) Like I say, I bet it is because
of the long standing penchant of the Linux community that everyything should
be free. In this case, it has come back to byte everybody. :-) (Sorry, you
know I can't resist. It's sort of like not laughing my head off when Rosie
O'Donnel says the World Trade Center bombing was an inside job put up by
Bush. :-) You wonder how her brain keeps from imploding from lack of
oxygen. :-) And finally to keep all my political comments inside one
paragraph... I just heard the funniest thing on Red Eye. Since it's all
about "ftolerance", they want to establish a gay bar next to the new mosque
that Muslims want to build next to Ground Zero. :-) Now *that* would be
funny. My comment was let them build a mosque there, if we can build a
church in Mecca. Ya think that's going to happen? :-)
John
> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Bruce Easton
> Sent: Tuesday, August 10, 2010 12:20 AM
> To: filepro-list at lists.celestial.com
> Subject: Re: FilePro from Linux xterm or other terminal?
>
> Comments inline below - Bruce Easton
>
> On 8/9/10 6:56 PM, Bill Campbell wrote:
> > On Wed, Jul 28, 2010, Bruce Easton wrote:
> >
> >> On 7/28/10 3:23 PM, Bill Campbell wrote:
> >>
> >>> On Wed, Jul 28, 2010, Walter Vaughan wrote:
> >>>
> >>>
> >>>> Bill Campbell wrote:
> >>>>
> >>>>
> >>>>
> >>>>> What do people do who want to run FilePro from Linux desktops?
> >>>>> [..]
> >>>>>
> >>>>> Bill
> >>>>>
> >>>> Putty works just fine. Use same settings you would for
> >>>> windows client.
> >>>>
> > ...
> >
> >> I think one setting that I have always have had to have
> set for filepro
> >> is under 'Window', then 'Translation' in putty. The top select box
> >> should be set to CP437. I use Snow Leopard's default
> 'Terminal' app for
> >> connecting to various *nix boxes running filepro, and I think that
> >> setting in the Terminal app is called 'Latin-US (DOS)'
> (or at least
> >> that seems to give similar behavior for fp needs). There
> are some other
> >> tweaks I had to do for the mac terminal short-cuts that I
> made (like
> >> giving me back F9-F12 for fp use), but I don't think those have any
> >> correlation to putty.
> >>
> > OK, I have been working on this for a while now, trying putty,
> > gnome-terminal, and xterm with mixed results.
> >
> > I have eliminated putty, largely because it seems quite limited
> > in the font selection, resulting in a tiny window that I find
> > difficult to use even on a relatively small 19in monitor at
> > 1024x768 resolution. It's also somewhat more difficult to use
> > compared to xterm and gnome-terminal which can invoke commands in
> > the startup using things like ``xterm -e ssh user at system''.
> >
> Hmm. I've not seen Linux version of putty, but on Windows
> version you
> can at least set and save a starting font size (albeit limited font
> selection), and then also save a checked setting that will allow the
> window to grow properly when stretched. Also, I should say right off
> the bat, that I'm not interested in color for character-based
> filepro,
> so I'm sure that's affected my choice of emulation and settings.
> > I find the gnome-terminal somewhat better in that it provides
> > larger fonts, but they're still somewhat limited compared to what
> > I can get using an xterm, and I can also set foreground and
> > background colors easily on the command line with xterms with
> > options like ``-bg LightSkyBlue''. Perhaps one can do the same
> > thing with gnome-terminal, but I don't know how (yet).
> >
> > I am adding an xterm-linux entry to a local copy of the fptermcap
> > file to be sure that FPtech updates don't nuke my changes, and
> > putting a slightly hacked version of the ``pf'' startup script in
> > /usr/local/bin which looks at then environment to set the
> > environment variable TERM=xterm-linux where appropriate.
> >
> >
> > The things I'm doing with the xterm-linux entries include:
> >
> > 1. Eliminating the terminal initialization string which
> sets the wierd
> > colors, leaving the xterm window with whatever foreground and
> > background colors the user selects. This also
> eliminates the need to
> > reset the xterm after exiting FilePro to get the
> screen colors back
> > to the user's definition of normal.
> >
> I'm curious Bill - using your xterm-linux fp termcap entry,
> when you go
> into define screens for a monochrome screen, does it warn
> that you are
> changing to a color screen (and vice versa)?
> > 2. Add ``GZ=~'' to the termcap so that the field ending drawing
> > character is a tiny dot instead of a question mark.
> >
> Neato - I need to add that to mine.
> > 3. Fix the function key mappings so the F1->F4 key
> codes are interpreted
> > properly instead of using the ancient PF key codes
> as found on the
> > old Wyse and VT100 terminals which only had 4 function keys.
> >
> I have not done anything to default xterm for these, but they
> work as-is
> for SL terminal using that Latin-DOS translation - maybe I'm missing
> something.
> > 4. Eliminate the use of function keys> F7 to avoid
> conflicts with the
> > Mac OS X use of these keys, using control key
> sequences in their
> > place.
> >
> Bill - do you have a mixture of OS X and other Linux users
> that you are
> trying to satisfy with one method, or it is all of one type? As I
> mentioned above, for the default Snow Leop. terminal, I just mapped
> (well to correct what I said above - it is for F9 and F10
> [but F11 and
> F12 could be done for consistency]) those function keys to
> require the
> Apple key - for the Expose app I think - so that filepro
> would use them
> normally. (So, for instance - I have to press Apple-key and
> F9 to make
> the windows do that kookey thing where they zoom out and are
> all visible
> and selectable, leaving a regular F9 for 'Go to' in filepro
> processing.)
> > One thing I have not been able to figure out is why FilePro seems
> > to be ignoring the ``LY=Ctrl-C'' entry in the termcap, but says
> > to hit the ``DEL'' key to exit various functions.
> >
> But what behavior do you get (regardless of what it says) -
> does it take
> both Del and Ctrl-C to exit from various places?
>
> On a few of the Linux systems that I ssh to, they have something near
> the end of their /etc/profile that looks like:
>
> stty intr ^?
> (right before 'unset i' and 'unset pathmunge')
> I can't remember, but I think this is what was used to switch
> it so that
> you use Del instead of Ctrl-C. Then in the fp termcap entry
> for xterm,
> it has :LY=Del. But I've never heard of that mixed appearance you
> describe. Maybe changing that default terminal init. string
> is causing
> that?
>
> One of my problems for xterm is that on certain (what I would think
> parallel) systems - the clear to end of field works on one
> and not the
> other. -Bruce
> > BTW: I'm testing here on FP 5.6.
> >
> > Bill
> >
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
More information about the Filepro-list
mailing list