Re: vim control characters in file
I had a disk failure and recovered from a backup, BUT... something is missing. Now whenever I vim a file I can see the control characters in the text file. Here's what I see in my .cshrc file: [33mumask 022 These go away if I comment out the 'syntax on' in my .vimrc file, but what's the deal? What am I missing? It looks like your term settings are wonky. Vim is doing syntax coloring by sending VT-100 escape sequences to your terminal, but your terminal isn't properly handling them. Check your $TERM setting in your shell: bash echo $TERM and what vim thinks your term setting is: :set term? My guess is that they don't jive, and that most likely, you'll see the same symptom in other colorizing console apps. Or, your vimrc is manually specifying what the 'term' should be and overriding whatever vim finds in the environment. If you're not manually specifying your 'term' setting in your vimrc, then it's likely a problem with configuration of the $TERM in which vim is running. -tim
Re: vim control characters in file
On 10/11/06, Alan Treece [EMAIL PROTECTED] wrote:
I had a disk failure and recovered from a backup, BUT... something is
missing.
Now whenever I vim a file I can see the control characters in the
text file. Here's what I see in my .cshrc file:
[33mumask 022
[33msetenv ORACLE_HOME /usr/local/sqlplus
[34m#setenv [31mSQLPATH[34m ${[31mHOME[34m}/sql
[33msetenv SQLPATH [32m${[35mHOME[32m}/cvs-projects/SunSolve/
br_R5_15_0/sunsolve5/server/purgeIDS/sql_lib
[33msetenv TNS_ADMIN [32m$SQLPATH
[34m#setenv TNS_ADMIN $ORACLE_HOME
These go away if I comment out the 'syntax on' in my .vimrc file, but
what's the deal? What am I missing?
Your vim emit color codes but your temrinal does not
interpret colors ? I suspect misalignment between your $TERM
setting and the actual term.
Yakov
Re: vim control characters in file
Thanks... this was the issue. Setting the term value in the .vimrc file fixed the issue. Later, ajTreece On Oct 11, 2006, at 10:35 AM, Tim Chase wrote: I had a disk failure and recovered from a backup, BUT... something is missing. Now whenever I vim a file I can see the control characters in the text file. Here's what I see in my .cshrc file: [33mumask 022 These go away if I comment out the 'syntax on' in my .vimrc file, but what's the deal? What am I missing? It looks like your term settings are wonky. Vim is doing syntax coloring by sending VT-100 escape sequences to your terminal, but your terminal isn't properly handling them. Check your $TERM setting in your shell: bash echo $TERM and what vim thinks your term setting is: :set term? My guess is that they don't jive, and that most likely, you'll see the same symptom in other colorizing console apps. Or, your vimrc is manually specifying what the 'term' should be and overriding whatever vim finds in the environment. If you're not manually specifying your 'term' setting in your vimrc, then it's likely a problem with configuration of the $TERM in which vim is running. -tim
