Issuing 'echo <ESC>[r' from .cshrc doesn't work, HELP

Issuing 'echo <ESC>[r' from .cshrc doesn't work, HELP

Post by R. Stewart Ell » Fri, 09 Jul 1993 23:29:56



Setup:
  386 running Intel SVR4.0.3 and Xfree386 (1.1?: I just finished browsing
   through the config files and can't find a version #), using olwm and
   xterms to connect to SunOS 4.1.3 server over ethernet.

Problem:
  Although I am running my xterms locally on the 386 with 44x80, when I
   rlogin in to the Sun server and try to start up elm or nn, they seem to
   issue a "set scrolling region" command to 24 lines.  If I look at
   'stty -a' before I run one of these commands, rows and cols are 0.  In
   order to get elm or nn to use the full window I must manually set the
   rows to 44 or run a command that is smart enough to figure it out properly
   (I am not sure right now, but I believe 'less' may work).  I cannot
   remember what all I have tried (resize, etc), but the one thing I know
   works is to issue <ESC>[r from the command line to reset scrolling
   region.  After that stty -a shows rows and columns correctly.  
  I also dial into the Sun server from a Sun workstation and run term to set
   up a socket over which I can connect multiple local xterms to the remote
   host.  These xterms always seem to propagate the size properly.

My attempted solution:
  Although it seems kludgey, I would be happy if I could simply get the
   <ESC>[r to work from .cshrc or .login.  I can tell from the commandline
   that the command has worked because it moves the cursor to the top of the
   screen without clearing.  From within the .cshrc and .login it does not
   seem to be recognized.  I have also tried 'eval'ing it.  I suspect if I
   recompiled the terminfo resource with the init string set to <ESC>[r that
   that would work.  I know how to setup a per-account termcap, but not
   terminfo.

Any insight or help will be appreciated.

--
                                                          ___________________
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765  /   _____  ______
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.   /        / /  /  / /

 
 
 

Issuing 'echo <ESC>[r' from .cshrc doesn't work, HELP

Post by Joachim Schnitt » Sat, 10 Jul 1993 17:22:54



: < deleted >

I am not sure what the exact reason for your  problem is. But browsing
through  the X11R5  xterm sources I  saw  that for  certain systems no
SINWICH signal is sent by xterm to its child processes. At that time I
was running  ISC 2.2.1  (System V 3.2)  and  the #ifdefs in  the xterm
sources were not set up correctly  for that system.   There was a note
(as far as  I remember)  in  the sources  stating  that an `#ifdef  0'
should be changed for some systems in  order to use SIGWINCH. Grep for
SIGWINCH  in the xterm  sources and you will  find what I mean. Try to
recompile xterm. Perhaps that helps...

-Joachim
--
______________________________________________________________________
Joachim Schnitter                           Tel.: +49 (61 51) 16-53 97
Technische Hochschule Darmstadt             Fax : +49 (61 51) 16-42 98
Physikalische Chemie I
Petersenstr. 20
64287 Darmstadt


 
 
 

1. Why: perl -e <<'EOF' doesn't work (bash)

Why is it that, at least under bash, the following snippet

  % perl -e 'print "ok\n"'
  ok

works fine, but this one

  % perl -e <<'EOF'
  > print "ok\n"
  > EOF

fails with the error message

  No code specified for -e.

?

TIA,

jill
--
To  s&e^n]d  me  m~a}i]l  r%e*m?o\v[e  bit from my a|d)d:r{e:s]s.

2. nvidia, GForce, XFree 4.0.1, Suse7.0

3. <ESC><ESC> or <TAB>

4. bash dumps core

5. <ctrl><alt> + or - doesn't work to change resolution

6. Microstar 6167 m.b. for AMD Athlon -- experiences??

7. sar <interval> <number> doesn't work for non-root user

8. Looking for info on ADSM & HACMP

9. Why doesn't echo "text" 'command' "more text" work?

10. ----->>>XF86Config Help Needed Here's a Copy of<<<------

11. <Alt>+<key> = <Esc><key> ?

12. Problem echoing special characters with '<<'