Conference unxa::cde

>    How can I get that functionality back?  
    
    Run dxterm? It's still there. 

Dtterm has the functionality you want, it is just very well hidden.  :-(
Dtterm and Xterm both have the capability to scroll QUITE a few lines or
screens.  You have to set values in their application specific resource files.

Dtterm*saveLines: 300s

will allow you to save 300 screens worth of scrolling.  That's what I use, and
it meets my needs.  You can also specify the number of lines, if you prefer.
I think that 

Dtterm*saveLines: 1500

will allow you to scroll 1500 lines, but check me on that just to be sure.

XTerm*saveLines:                1500

will allow you to scroll 1500 lines in Xterm, and that is what I use.

If you need to know how to set up resource files, look first at the man page
for dtterm, xterm, and X.  If it is still unclear, send mail (after making
several attempts), and I'll try to help.

Brian
[Posted by WWW Notes gateway]

Xterm *does* have scrolling, you just have to know how to enable it.  It is
fairly simple, actually.  In xterm, place the mouse inside of the window and
simultaneously press the Ctrl and middle mouse button, (Ctrl-MB2 or C-MB2 in
some literature).  This will bring up a pulldown menu for VT terminal
emulation
options, the FIRST of which is to enable or disable scrolling.  If yours is
NOT checked off, that's why scrolling is not enabled.

Once again, enabling scrolling by default can be done in either xterm or
dtterm
by putting the appropriate resource in your application-specific resource
file.
For xterm, that resource is scrollBar.  Here are a few others that I use:

XTerm*loginShell:       true
XTerm*saveLines:        1500
XTerm*scrollBar:        true
XTerm*pointerShape:     top_left_arrow

You can put these into .Xdefaults or into a XTerm resource file in your home
directory, or a location pointed to by your specific environment.

Brian
[Posted by WWW Notes gateway]

As Paul Beck mentions, you can run dxterm.  It has not been eliminated, (not
yet, anyway, but support is difficult to get on it now).

If you want, you can get as creative as you want and add an icon for dxterm by
using the "Create Action" in the Application Manager Desktop Apps.
To do this, invoke "Create Action" by double clicking on its icon, enter the
"Action Name" dxterm, enter the command /usr/bin/X11/dxterm -ls, put in some
Help text to describe that you're starting your own DECterm, then press "Find
Set..." to select an icon to use for a terminal.  You can an icon from dtterm
or xterm, or edit your own.

Help within the dtcreate application or the corresponding man page can give
you
more, if this explanation is not complete enough.  Once you have an icon built
that invokes dxterm, you can put it in your workspace, copy it to the CDE
Front Panel, add/change/replace existing actions to your heart's content.  In
case you mess up BIG time, there is even a way to get back to the default
Front
Panel.  How do I know this?  I've tried 'em all, messed 'em up, and fixed 'em.

My Front Panel definitely has a personal "The Mas" appearance.

Brian
[Posted by WWW Notes gateway]

I use dxterm for rlogins from my V4.0 system to pre-Platinum UNIX systems or VMS
systems. Those systems don't handle the dtterms well. Other than that, I like
using dtterms.

-Jeff

    Thanks for all the help here!  I'm playing around with the savelines
    settings now.  
    
    Only thing missing is how to do screen prints.  Reading the MAN page
    doesn't give me much insight here.  I know I can log the output through
    a pipe to the printer daemon.  I'd like to be able to highlight an area
    with the mouse and then print it.  Even a subset of the DECterm
    functionality would be nice.
    
    Thanks!
    	David

    I've set savelines as suggested but have the following behavior.  If
    I'm telnetted to a VMS system and am reading mail, backing up through
    the saved lines buffer gets me the following output:
    
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
        #1           4-OCT-1994 17:25:23.66                                MAIL
    
    Get the idea?  I lose the data on each of the previous screens probably
    because of the CLS or FF that occurs at the beginning of each screen. 
    The DECterm program would throw those away and allow you to scroll back
    through the text.  Any way to fix that?
    
    	Thanks!
    		David

    Not offhand, I don't know how to fix such behavior.  I think you're
    starting to catch onto WHY there are all of these emulators.  DECterm
    seems to handle the DEC legacy stuff best, but is very DEC-like, and
    does not fit into non DEC environments very well.  The executable image
    is also very large and bug fix support is dwindling.  Longtime VMS
    users definitely prefer it, however.
    
    Xterm is available on almost any recent UNIX box, and it works the same
    everywhere.  BUT, it only emulates VT100 and Tektronics terminals and
    any customizations that you want to save HAVE to be manually put into
    resource files.  It is the favorite of "heavies", but also has little
    vendor support.
    
    Dtterm is the newest of the terminal emulators, and it works well on
    the desktop.  It does recognize the numerical keypad (LK201-401), so
    VT200 emulation is supported, but it does not work as well as
    DECterm/dxterm, by any means.  On the other hand, you can save the
    geometry and even specific workspace that you want to run Dtterm in,
    which dxterm simply does not understand at all.  (There's something
    dtterm does that dxterm can't as far as I can tell).
    
    NONE of these emulators does every single feature that all the others
    do.  Personally, I prefer running the Bash shell in an xterm window as
    my default environment, but I DO use all three emulators, depending on
    what I'm doing, for the very reasons that I mention.  Stick with
    DECterm/dxterm for DEC legacy stuff until someone threatens to pull the
    plug on it, at which time, scream loudly that the alternatives simply
    do not meet the needs of legacy apps.  [Better yet, be proactive and
    enter suggestion QARs on what needs to change in dtterm to allow it to
    FULLY replace dxterm].
    
    Brian