Yes, my current practice is to precede *on the same line* "TERM=xterm " the invocation of ved, xved, etc.:
bill@debian-desktop:~$ TERM=xterm xved ;;; WARNING - PIXMAP FILE NOT FOUND ;;; INVOLVING: '$usepop/pop/x/ved/bitmaps/src_48.xbm' ;;; PRINT DOING ;;; DOING : runproc ;;; editing: temp.p, ON LINE 1 or bill@debian-desktop:~$ TERM=xterm pop11 Sussex Poplog (Version 16.0 Sun Aug 16 18:54:52 CDT 2020) Copyright (c) 1982-1999 University of Sussex. All rights reserved. Setpop : ved ───┤ 1├ ved (editing: temp.p, 2 lines) ──────────────────────────────────────────────────────────── (I found out recently that setting an environment variable on the same line as a shell command modifies the environment *for only that command*; as soon as the command terminates the environment variable resumes its previous value, sorta like rebinding a variable inside a LET form in Common Lisp.) Anyway, I am satisfied that the terminal type issue is resolved, and thanks to everyone who had info on the issue, Bill Wood
