0

Opening vim while recording with script causes script to go wild (my screen starts filling up with a bunch of crap, some of which says "script", and I also believe it is colored neon green).

Does script set any environment variables that vim can check to stop from opening?

Improve this question
3
  • 1
    Does it happen for all files or a particular file or file type? Your vimrc might be adding some control characters for syntax highlighting or something that are not behaving well with your terminal Commented May 8 at 20:19
  • 1
    Does it happen for script -c vim, script -c 'vim -u NONE', /usr/bin/script -c 'vim -u NONE'? Can you show a screenshot? Commented May 9 at 11:29
  • To check whether your script sets or modifies environment variables, you can do env > a; script -qc 'env > b'; diff -u a b. In my case, I get no output meaning the environment is the same inside and outside script. Commented May 9 at 11:33

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.