JED Question
Kai Daumiller, FZK-IK1, Tel. 07247-82-3506
Hello Experts,
I have a problem using JED, an EMACS/EDT clone.
JED has the option to use color syntax highlighting.
This works very well using XJED, the X version of JED.
But with this option activated the normal JED doesn't rebuild the
screen correctly after deleting characters via backspace, it simply overwrites
the existing text of that line.
When doing a redraw with ctrl-l, the screen is ok again.
Any Ideas?
Thanks in advance
Kai
J.JANSEN
I observed the same for some time now but can give some more data:
1) The problem occurs only when running JED on a VMS machine.
2) THe problem occurs only if DECTERM is used as terminal and if the
version of
DECWINDOWS is at least 1.2-3
All other combinations (i.e. runnig JED on a UNIX(Brrr) system and
display on a DECTERM is no problem. Using a real VT241 is no problem. So
my guess there is some problem in DECTERM.
--
>------------------------------------------------------------------------------<
Jouk Jansen
jo...@crys.chem.uva.nl
>------------------------------------------------------------------------------<
John E. Davis
On Fri, 31 Jan 1997 14:43:42 +0000, J.JANSEN <JO...@crys.chem.uva.nl>
wrote:
> All other combinations (i.e. runnig JED on a UNIX(Brrr) system and
>display on a DECTERM is no problem. Using a real VT241 is no problem. So
>my guess there is some problem in DECTERM.
Try adding:
TERM_CANNOT_INSERT = 1;
to your jed.rc file. I thought that DECTERM emulated a vt102.
--
John E. Davis Center for Space Research/AXAF Science Center
617-258-8119 MIT 37-662c, Cambridge, MA 02139
http://space.mit.edu/~davis
fair...@sldb4.slac.stanford.edu
In article <slrn5fa78...@aluche.mit.edu>,
da...@space.mit.edu (John E. Davis) writes:
[...]
> On Fri, 31 Jan 1997 14:43:42 +0000, J.JANSEN <JO...@crys.chem.uva.nl>
> wrote:
>> All other combinations (i.e. runnig JED on a UNIX(Brrr) system and
>>display on a DECTERM is no problem. Using a real VT241 is no problem. So
>>my guess there is some problem in DECTERM.
>
> Try adding:
>
> TERM_CANNOT_INSERT = 1;
>
> to your jed.rc file. I thought that DECTERM emulated a vt102.
Well, yes, no, sometimes. :-) In the DECterm "Options" menu,
"General...", the user has the choice of setting the DECterm
emulation mode to "VT52", "VT100", "VT300, 7-bit Controls" or
"VT300, 8-bit Controls". Those are the basic emulations, and
"VT300", probably with 7-bit controls, is the default.
However, the user can also (independently) select the "Terminal
ID" as any of VT100, VT101, VT102, VT125, VT220, VT240, VT320,
VT330, VT340, or DECterm (the default). I am not sure of the
interaction between the emulation mode and the terminal ID, but I'd
expect that an inquire of the terminal will return the
characteristics of the associated "Terminal ID" rather than the
emulation mode (so they'd better be consistent).
The upshot is that I don't understand either the statement, "I
thought that DECterm emulated a vt102" (the VT102 supports a
_subset_ of what a DECterm or VT320 supports), or the recommendation
to set TERM_CANNOT_INSERT to 1. Is is possible the original
questioner has set his DECterm to emulate a VT52?!
One other possibility is that the DECterm's screen size (columns
and rows) is different than what the VMS terminal driver thinks it
is (show terminal). In such cases, you can get strange and jumpy
behaviour, e.g., in an editor like EVE.
-Ken
--
Kenneth H. Fairfield | Internet: Fair...@Slac.Stanford.Edu
SLAC, P.O.Box 4349, MS 46 | DECnet: 45537::FAIRFIELD (45537=SLACVX)
Stanford, CA 94309 | Voice: 415-926-2924 FAX: 415-926-3515
-------------------------------------------------------------------------
These opinions are mine, not SLAC's, Stanford's, nor the DOE's...
John E. Davis
On 2 Feb 97 20:24:39 -0800, fair...@sldb4.slac.stanford.edu <fair...@sldb4.slac.stanford.edu>
wrote:
> The upshot is that I don't understand either the statement, "I
> thought that DECterm emulated a vt102" (the VT102 supports a
> _subset_ of what a DECterm or VT320 supports), or the recommendation
> to set TERM_CANNOT_INSERT to 1. Is is possible the original
> questioner has set his DECterm to emulate a VT52?!
I believe that the vt102 supports insert/delete character escape
sequences. Under VMS, unless told otherwise, JED assumes that the
terminal provides an emulation of basic vt102 capabilities. From the
description provided by the original poster, I guessed (perhaps wrong)
that the terminal emulation that was being used failed this assumption.
I realise that there is a system call to get the terminal type;
however, I have not used VMS for several years and I will have to rely
upon someone else to provide the code to deduce whether or not the
current terminal provides vt102 capabilities. Whether or not the
terminal can emulate a vt102 is not the question; rather the question
concerns the currently selected emulation.
J.JANSEN
John E. Davis wrote:
>
> On 2 Feb 97 20:24:39 -0800, fair...@sldb4.slac.stanford.edu <fair...@sldb4.slac.stanford.edu>
> wrote:
> > The upshot is that I don't understand either the statement, "I
> > thought that DECterm emulated a vt102" (the VT102 supports a
> > _subset_ of what a DECterm or VT320 supports), or the recommendation
> > to set TERM_CANNOT_INSERT to 1. Is is possible the original
> > questioner has set his DECterm to emulate a VT52?!
>
> I believe that the vt102 supports insert/delete character escape
> sequences. Under VMS, unless told otherwise, JED assumes that the
> terminal provides an emulation of basic vt102 capabilities. From the
> description provided by the original poster, I guessed (perhaps wrong)
> that the terminal emulation that was being used failed this assumption.
>
> I realise that there is a system call to get the terminal type;
> however, I have not used VMS for several years and I will have to rely
> upon someone else to provide the code to deduce whether or not the
> current terminal provides vt102 capabilities. Whether or not the
> terminal can emulate a vt102 is not the question; rather the question
> concerns the currently selected emulation.
> --
Surely my DECTERM was NOT in VT52 mode when I got the error. The first
time I encountered it, it was after upgrading from DECWindows 1.2 to
1.2-3. After downgrading again it was gone again. Then I decided to use
xjed instead of jed. After upgrading to 1.2-4 I tested again and the
same error occured still. After that I applied some patches to
DECWindows and did not bother to test jed (We never use it anymore). But
If I had done so I would have noticed that the problem was GONE!!!.
Jouk