[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2115.0. "Should CREATE/TERMINAL/NOPROCESS/INSERT work?" by ARTFUL::SCOTT (Mikey hates it.) Tue Jan 23 1990 16:54

When I attempt to do a CREATE/TERMINAL/NOPROCESS/INSERT I get the following:

$ create/term/noproc/insert
%DCL-W-CONFLICT, illegal combination of command elements - check documentation
 \INSERT\

Well, there is nothing in the only documentation of this that I have (the V5.3
New Features Manual) which implies that these switches shouldn't work together.
Also, the documentation says that the terminal will take the insert/overstrike
mode from it's "parent" (whatever that means).  Though the terminal that I
create it from is in insert mode, the created terminal is overstrike.

What gives?  Is this the way it's supposed to work?

                                                                 -- Mike
T.RTitleUserPersonal
Name		DateLines
2115.1/INSERT/NOPROCESS is (incorrectly) disallowedHANNAH::MESSENGERBob MessengerWed Jan 24 1990 11:0618
Re: .0

For some reason I thought it wouldn't make sense to set terminal
characteristics if you weren't creating a process (maybe because I thought
people would be confused when LOGINOUT.EXE over-rode those characteristics),
so I explicitly disallowed the /INSERT/NOPROCESS combination (along with many
others) in the create.cld file.  I think the combination would produce the
expected results if it weren't disallowed in create.cld.

Consider this a bug; I'd suggest entering a QAR.

The documentation could also be improved; it's true that if you say CREATE
TERM without specifying /INSERT or /OVERSTRIKE that the insert/overstrike
mode would be inherited from the parent, because CREATE TERM would create
a subprocess.  In other cases, though, there is no parent, so it would
default to the permanent default (I think this might be a SYSGEN parameter).

				-- Bob
2115.2I use /NOPROCESS a lotARTFUL::SCOTTMikey hates it.Wed Jan 24 1990 12:2610
Thanks for the reply.  About half of my use of CREATE/TERMINAL is with the
/NOPROCESS switch.  I commonly use it to create a separate window in which to
run the mundane (and, IMHO, infinitely better), non-DECwindows version
of DEBUG (see the discussion in 2069.*).  For the same purpose, I'd like to
lodge a wish-list request for a "/ALLOCATE" switch to allocate the terminal
to the CREATE'ing process so that the terminal could be used multiple times.
Thanks again.

                                                           -- Mike
2115.3PRNSYS::LOMICKAJJeffrey A. LomickaFri Jan 26 1990 14:0910
>lodge a wish-list request for a "/ALLOCATE" switch to allocate the terminal

This is not possible without CMEXEC priv.

To fix CREATE/TERMINAL, use the SHOW COMMAND tooshed utility to generate a
.CLD for the CREATE command, delete all the DISALLOW clauses for the
/TERMINAL variation, and SET COMMAND the result.

Either that, or go back to CHILD which has both /ALLOCATE and the
/INSERT working by default.