Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 01.03.2010 16:59, Mart Frauenlob wrote:
On 01.03.2010 12:06, Mart Frauenlob wrote:
On 28.02.2010 09:29, Mart Frauenlob wrote:
after I upgraded from etch to lenny a few days ago (new config files
have been installed for vim), I noticed that syntax highlighting for my
bash scripts is not working as before.
There are some things i've noticed, where of the first is worse to me.
1: If I put the following statement onto a single line, it does not
cause problems:
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
But as soon as i put it into a for loop:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
Everything from the 'done' word is marked with as syntax error, making
the whole file unreadable (could turn of syntax highlighting).
2:
if [[ $1 = +([[:digit:]]) ]]; then
...
fi
is good, but with:
case $1 in
+([[:digit:]])) :
;;
esac
the last 2 `]]' are shown in red background (syntax error).
3: This one causes everything after the `'' (single quote) to be
rendered as error:
[[ $x = *\'* ]] ...
this is my .vimrc:
set ts=4
set sw=4
let g:is_bash= 1
let sh_minlines= 500
Any ideas how I could get that fixed?
Many of my scripts are garbled now. they are more readable without
syntax highlighting.
I've tried to look up this problem with vim syntax highlighting a bit more.
It seems to me that escaping (single|double quotes?) in any loop
statement does not work.
So I've to correct my first report, those escaping problems lead to the
result, that all following code is formatted as it was inside quotes
(not rendered as error, like the [[:digit:]] string).
So this one:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
needs a `' (double quote) added, to become valid for vim (while
becoming invalid in case of shell syntax).
Same thing inside an if statement:
if true; then
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
fi
while inside a case statement it remains rendered valid.
And this one:
[[ $x = *\'* ]]
needs `' ]]' to become valid for vim.
I guess that could be fixed by modifying
/usr/share/vim/vim71/syntax/sh.vim - but I'm lost on how to.
It all worked out of the box on sarge and etch.
Most of the work I do on linux is write bash scripts with vim. This is
now messed up since the upgrade to lenny.
Any hints? Please anyone?
Trimming it down more:
var[0]=\foo bar\ is valid on a line for itself.
But:
if true; then
echo \foo\
var=\foo bar\
var[0]=\foo bar\
fi
the 'echo' and the 'var=' escape well, but the 'var[0]=' array member
assignment fails.
Hello,
though I'm mainly talking to myself here, I got some updates.
I manually compiled/installed the vim versions 6.4, 7.0, 7.1 and 7.2.
Running version 6.4 and 7.0 with a slightly modified vimrc from the etch
version (vimrc.dpkg-old) (leaving out some debian specific things), I
get back the bash script syntax highlighting I was used to in sarge and
etch.
However vim versions 7.1 and 7.2 seem to have changed. I get different
results with both. I don't know if this is caused by the sh.vim or the
actual vim code, but however it does not seem to be a debian specific
problem, as far as I can tell.
Guess I need to find the time to talk to the people in the vim mailing list.
Good day
Mart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b8d5790.6070...@chello.at
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 28.02.2010 09:29, Mart Frauenlob wrote:
Hello,
after I upgraded from etch to lenny a few days ago (new config files
have been installed for vim), I noticed that syntax highlighting for my
bash scripts is not working as before.
There are some things i've noticed, where of the first is worse to me.
1: If I put the following statement onto a single line, it does not
cause problems:
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
But as soon as i put it into a for loop:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
Everything from the 'done' word is marked with as syntax error, making
the whole file unreadable (could turn of syntax highlighting).
2:
if [[ $1 = +([[:digit:]]) ]]; then
...
fi
is good, but with:
case $1 in
+([[:digit:]])) :
;;
esac
the last 2 `]]' are shown in red background (syntax error).
3: This one causes everything after the `'' (single quote) to be
rendered as error:
[[ $x = *\'* ]] ...
this is my .vimrc:
set ts=4
set sw=4
let g:is_bash= 1
let sh_minlines= 500
Any ideas how I could get that fixed?
Many of my scripts are garbled now. they are more readable without
syntax highlighting.
Thanks a lot
Mart
Hello again,
I've tried to look up this problem with vim syntax highlighting a bit more.
It seems to me that escaping (single|double quotes?) in any loop
statement does not work.
So I've to correct my first report, those escaping problems lead to the
result, that all following code is formatted as it was inside quotes
(not rendered as error, like the [[:digit:]] string).
So this one:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
needs a `' (double quote) added, to become valid for vim (while
becoming invalid in case of shell syntax).
Same thing inside an if statement:
if true; then
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
fi
while inside a case statement it remains rendered valid.
And this one:
[[ $x = *\'* ]]
needs `' ]]' to become valid for vim.
I guess that could be fixed by modifying
/usr/share/vim/vim71/syntax/sh.vim - but I'm lost on how to.
It all worked out of the box on sarge and etch.
Most of the work I do on linux is write bash scripts with vim. This is
now messed up since the upgrade to lenny.
Any hints? Please anyone?
Best regards
Mart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b8b9fc4.8060...@chello.at
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
Check `update-alternatives --list vim` to ensure your not running vim-tiny. -- Jordan Metzmeier -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50e5edd51003010556p15a51dc7x475c5951dac84...@mail.gmail.com
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 01.03.2010 14:56, Jordan Metzmeier wrote: Check `update-alternatives --list vim` to ensure your not running vim-tiny. eris:~# update-alternatives --display vim vim - status is auto. link currently points to /usr/bin/vim.basic /usr/bin/vim.tiny - priority 10 /usr/bin/vim.basic - priority 30 Current `best' version is /usr/bin/vim.basic. there are no other vim.X versions, right? Best regards Mart -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b8bde1d.1090...@chello.at
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 01.03.2010 12:06, Mart Frauenlob wrote:
On 28.02.2010 09:29, Mart Frauenlob wrote:
after I upgraded from etch to lenny a few days ago (new config files
have been installed for vim), I noticed that syntax highlighting for my
bash scripts is not working as before.
There are some things i've noticed, where of the first is worse to me.
1: If I put the following statement onto a single line, it does not
cause problems:
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
But as soon as i put it into a for loop:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
Everything from the 'done' word is marked with as syntax error, making
the whole file unreadable (could turn of syntax highlighting).
2:
if [[ $1 = +([[:digit:]]) ]]; then
...
fi
is good, but with:
case $1 in
+([[:digit:]])) :
;;
esac
the last 2 `]]' are shown in red background (syntax error).
3: This one causes everything after the `'' (single quote) to be
rendered as error:
[[ $x = *\'* ]] ...
this is my .vimrc:
set ts=4
set sw=4
let g:is_bash= 1
let sh_minlines= 500
Any ideas how I could get that fixed?
Many of my scripts are garbled now. they are more readable without
syntax highlighting.
I've tried to look up this problem with vim syntax highlighting a bit more.
It seems to me that escaping (single|double quotes?) in any loop
statement does not work.
So I've to correct my first report, those escaping problems lead to the
result, that all following code is formatted as it was inside quotes
(not rendered as error, like the [[:digit:]] string).
So this one:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
needs a `' (double quote) added, to become valid for vim (while
becoming invalid in case of shell syntax).
Same thing inside an if statement:
if true; then
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
fi
while inside a case statement it remains rendered valid.
And this one:
[[ $x = *\'* ]]
needs `' ]]' to become valid for vim.
I guess that could be fixed by modifying
/usr/share/vim/vim71/syntax/sh.vim - but I'm lost on how to.
It all worked out of the box on sarge and etch.
Most of the work I do on linux is write bash scripts with vim. This is
now messed up since the upgrade to lenny.
Any hints? Please anyone?
Trimming it down more:
var[0]=\foo bar\ is valid on a line for itself.
But:
if true; then
echo \foo\
var=\foo bar\
var[0]=\foo bar\
fi
the 'echo' and the 'var=' escape well, but the 'var[0]=' array member
assignment fails.
Regards
Mart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b8be45a.6030...@chello.at
Re: after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
On 01.03.2010 16:32, Mart Frauenlob wrote: On 01.03.2010 14:56, Jordan Metzmeier wrote: Check `update-alternatives --list vim` to ensure your not running vim-tiny. eris:~# update-alternatives --display vim vim - status is auto. link currently points to /usr/bin/vim.basic /usr/bin/vim.tiny - priority 10 /usr/bin/vim.basic - priority 30 Current `best' version is /usr/bin/vim.basic. there are no other vim.X versions, right? Sorry, don't want to spam, just installed the vim.nox (as no gui here), but that didn't change anything. eris:~# update-alternatives --display vim vim - status is auto. link currently points to /usr/bin/vim.nox /usr/bin/vim.tiny - priority 10 /usr/bin/vim.basic - priority 30 /usr/bin/vim.nox - priority 40 Current `best' version is /usr/bin/vim.nox. Best regards Mart -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b8be685.9080...@chello.at
after upgrade etch - lenny, problem with vim syntax highlighting in bash scripts
Hello,
after I upgraded from etch to lenny a few days ago (new config files
have been installed for vim), I noticed that syntax highlighting for my
bash scripts is not working as before.
There are some things i've noticed, where of the first is worse to me.
1: If I put the following statement onto a single line, it does not
cause problems:
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
But as soon as i put it into a for loop:
for tmp_content in ${str_attr_val}; do
RESULT_ARR[IDX++]=[$((m_count++))]=\${str_attr_name}[$((opt_idx++))]=\\\${tmp_content}
done
Everything from the 'done' word is marked with as syntax error, making
the whole file unreadable (could turn of syntax highlighting).
2:
if [[ $1 = +([[:digit:]]) ]]; then
...
fi
is good, but with:
case $1 in
+([[:digit:]])) :
;;
esac
the last 2 `]]' are shown in red background (syntax error).
3: This one causes everything after the `'' (single quote) to be
rendered as error:
[[ $x = *\'* ]] ...
this is my .vimrc:
set ts=4
set sw=4
let g:is_bash= 1
let sh_minlines= 500
Any ideas how I could get that fixed?
Many of my scripts are garbled now. they are more readable without
syntax highlighting.
Thanks a lot
Mart
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b8a296f.6080...@chello.at
Re: vim syntax line
Jerome, Could you figure out what the issue is and how to fix that? I am using version 7.0.235 and I experience the same problem. My debian.vim does not mention anything about the syntax option. -- Bernd On Wed, 12 Dec 2007 12:34:59 +0800, Jerome BENOIT [EMAIL PROTECTED] wrote: Hi, there is an explanation in the `debian.vim' . Jerome Lucas Prado Melo wrote: I don't know why... but when it happens I (re-(?))install vim... On Dec 11, 2007 8:00 PM, Jerome BENOIT [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: You get the point. Thanks, Jerome Magnus Therning wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 10, 2007 6:16 PM, Jerome BENOIT [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello List, I have just noticed on my Lenny box that the vim syntax line command in files does not work anymore whereas the syntax feature is on. May I set something in vimrc to make it works ? or is it a bug ? Are you talking about `modeline'? The relevant variables are `modeline' and `modelines'. /M -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHXmF6iMWTaatN+6QRAq4PAKCU4nFeDaZmZ+QmXIf7wsNaYm+HcwCfRb6m LKmDnl1aK4DS1dEhsFxUgII= =hE3K -END PGP SIGNATURE- -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Bernd Prager -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax line
You get the point. Thanks, Jerome Magnus Therning wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 10, 2007 6:16 PM, Jerome BENOIT [EMAIL PROTECTED] wrote: Hello List, I have just noticed on my Lenny box that the vim syntax line command in files does not work anymore whereas the syntax feature is on. May I set something in vimrc to make it works ? or is it a bug ? Are you talking about `modeline'? The relevant variables are `modeline' and `modelines'. /M -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHXmF6iMWTaatN+6QRAq4PAKCU4nFeDaZmZ+QmXIf7wsNaYm+HcwCfRb6m LKmDnl1aK4DS1dEhsFxUgII= =hE3K -END PGP SIGNATURE- -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax line
Hi, there is an explanation in the `debian.vim' . Jerome Lucas Prado Melo wrote: I don't know why... but when it happens I (re-(?))install vim... On Dec 11, 2007 8:00 PM, Jerome BENOIT [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: You get the point. Thanks, Jerome Magnus Therning wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 10, 2007 6:16 PM, Jerome BENOIT [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello List, I have just noticed on my Lenny box that the vim syntax line command in files does not work anymore whereas the syntax feature is on. May I set something in vimrc to make it works ? or is it a bug ? Are you talking about `modeline'? The relevant variables are `modeline' and `modelines'. /M -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHXmF6iMWTaatN+6QRAq4PAKCU4nFeDaZmZ+QmXIf7wsNaYm+HcwCfRb6m LKmDnl1aK4DS1dEhsFxUgII= =hE3K -END PGP SIGNATURE- -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
vim syntax line
Hello List, I have just noticed on my Lenny box that the vim syntax line command in files does not work anymore whereas the syntax feature is on. May I set something in vimrc to make it works ? or is it a bug ? Thanks in advance, Jerome -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
vim syntax on
Hallo, neuerdings habe ich die sensationelle option syntax on bei vim entdeckt (bewirkt das der textblock in versch. farben dargestellt wird). lästig ist nur das ich bei jeder datei von neuem diesen befehl eingeben muss. gibt es keine möglichkeit dies als standard für alle dateien die ich mit vim öffne zu definieren? patrik -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: vim syntax on
* patrik matt wrote: gibt es keine möglichkeit dies als standard für alle dateien die ich mit vim öffne zu definieren? echo syntax on ~/.vimrc Norbert -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: vim syntax on
* patrik matt: gibt es keine möglichkeit dies als standard für alle dateien die ich mit vim öffne zu definieren? Ja, in der ~/.vimrc: »set syntax=on« Grüße, kro -- Veteran of the Bermuda Triangle Expeditionary Force 1990-1951 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: vim syntax on
Hi, gibt es keine möglichkeit dies als standard für alle dateien die ich mit vim öffne zu definieren? :syntax on in die .vimrc in deinem home schreiben (zur Not anlegen). - Moritz
Re: vim syntax on
* patrik matt schrieb am 2005-02-08 um 12:49 Uhr: lästig ist nur das ich bei jeder datei von neuem diesen befehl eingeben muss. gibt es keine möglichkeit dies als standard für alle dateien die ich mit vim öffne zu definieren? Entweder du schreibst bei jedem Öffnen ein :syntax on rein oder du entdeckst, dass vom, wie viele andere Programme, eine Konfigurationdatei (.vimrc, siehe auch http://www.michael-prokop.at/computer/config/.vimrc) besitzt. Dort kannst du dies reinschreiben. -- Jens Kubieziel http://www.kubieziel.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: vim syntax on
Hallo, Am Dienstag, 08. Feb 2005, 12:57:09 +0100 schrieb Norbert Tretkowski: echo syntax on ~/.vimrc Oder syntax on in `/etc/vim/vimrc' wieder einkommentieren. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: vim syntax on
* Bertram Scharpf wrote: Norbert Tretkowski: echo syntax on ~/.vimrc Oder syntax on in `/etc/vim/vimrc' wieder einkommentieren. Fuer globale Anpassungen ist /etc/vim/vimrc.local gedacht, zumindest fuer den Fall dass man sarge oder sid verwendet. Wobei mir gerade auffaellt dass das nirgends dokumentiert ist... mal auf die TODO Liste packen. Norbert -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: vim syntax on
On Tue, Feb 08, 2005 at 04:02:46PM +0100, Bertram Scharpf wrote: Hallo, Am Dienstag, 08. Feb 2005, 12:57:09 +0100 schrieb Norbert Tretkowski: echo syntax on ~/.vimrc Oder syntax on in `/etc/vim/vimrc' wieder einkommentieren. Besser ist es wohl es in /etc/vim/vimrc.local zu schreiben, da dann die Updates von VIM nich rummeckern. Die Datei wird automatisch gelesen wenn sie existiert. Michael -- http://www.worldforge.org/ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: vim syntax on
Norbert Tretkowski schrieb am Dienstag, 08. Februar 2005 um 16:16:32 +0100: * Bertram Scharpf wrote: Norbert Tretkowski: echo syntax on ~/.vimrc Oder syntax on in `/etc/vim/vimrc' wieder einkommentieren. Fuer globale Anpassungen ist /etc/vim/vimrc.local gedacht, zumindest fuer den Fall dass man sarge oder sid verwendet. ach, dann sollte man vielleicht mal ein Wishlist-Bug gegen vim aufmachen, um dem Maintainer in den Allerwertesten zu treten, denn jedes mal beim Update wird meckert dpkg dass sich die vimrc geändert hat. Wobei mir gerade auffaellt dass das nirgends dokumentiert ist... mal auf die TODO Liste packen. apt-cache show vim | grep Maintainer achso :-) -- Jörg Friedrich There are only 10 types of people: Those who understand binary and those who don't. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: vim syntax on
* Joerg Friedrich wrote: Norbert Tretkowski schrieb: Fuer globale Anpassungen ist /etc/vim/vimrc.local gedacht, zumindest fuer den Fall dass man sarge oder sid verwendet. ach, dann sollte man vielleicht mal ein Wishlist-Bug gegen vim aufmachen, um dem Maintainer in den Allerwertesten zu treten, denn jedes mal beim Update wird meckert dpkg dass sich die vimrc geändert hat. Das ist nur dann der Fall wenn du die vimrc angefasst hast. Das ist dann auch kein Bug, sondern das gewuenschte Verhalten von dpkg, und genau der Grund warum die (undokumentierte) vimrc.local eingefuehrt wurde. Norbert -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
vim syntax suddenly stopped
Hi all All of sudden vim shows no syntax coloring :set syntax on is of no help. Though ls --color is working fine. I recently upgraded ncurses could that be the problem?? Any suggestion will be highly appreciated especialy from someone who faced similar problem before or Do I have to set some environment variable ?? i use testing version of vim and debian both TIA Prashant kumar home page http://home.iitk.ac.in/student/prashkr +-+ |Nothing is fool-proof for a sufficiently talented fool! | +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax suddenly stopped
On Tue, Sep 14, 2004 at 07:25:18AM -0400, Prashant Kumar wrote: Hi all All of sudden vim shows no syntax coloring :set syntax on is of no help. Though ls --color is working fine. I recently upgraded ncurses could that be the problem?? Any suggestion will be highly appreciated especialy from someone who faced similar problem before or Do I have to set some environment variable ?? i use testing version of vim and debian both Is this helpful: http://lists.debian.org/debian-user/2004/09/msg00233.html Exec. summary: Check your 'runtimepath'. -- The world's most effective spam filter: ln -sf /dev/full /var/mail/$USER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax suddenly stopped
On Mon, 13 Sep 2004, Stefan O'Rear wrote: Date: Mon, 13 Sep 2004 19:33:56 -0700 From: Stefan O'Rear [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: vim syntax suddenly stopped Resent-Date: Mon, 13 Sep 2004 21:33:59 -0500 (CDT) Resent-From: [EMAIL PROTECTED] On Tue, Sep 14, 2004 at 07:25:18AM -0400, Prashant Kumar wrote: Hi all All of sudden vim shows no syntax coloring :set syntax on is of no help. Though ls --color is working fine. I recently upgraded ncurses could that be the problem?? Any suggestion will be highly appreciated especialy from someone who faced similar problem before or Do I have to set some environment variable ?? i use testing version of vim and debian both Is this helpful: http://lists.debian.org/debian-user/2004/09/msg00233.html Exec. summary: Check your 'runtimepath'. -- The world's most effective spam filter: ln -sf /dev/full /var/mail/$USER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Hi all That didnot help my $VIMRUNTIME PATH is set correctly, vim echos it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[solved]Re: vim syntax suddenly stopped
Thanks a lot , it worked , though vim was echoing $VIMRUNTIME correctly it had conflicts with one in /etc/vim/vimrc I chnaged that and vim looks colorful again. Prashant kumar home page http://home.iitk.ac.in/student/prashkr +-+ |Nothing is fool-proof for a sufficiently talented fool! | +-+ On Mon, 13 Sep 2004, Stefan O'Rear wrote: Date: Mon, 13 Sep 2004 19:33:56 -0700 From: Stefan O'Rear [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: vim syntax suddenly stopped Resent-Date: Mon, 13 Sep 2004 21:33:59 -0500 (CDT) Resent-From: [EMAIL PROTECTED] On Tue, Sep 14, 2004 at 07:25:18AM -0400, Prashant Kumar wrote: Hi all All of sudden vim shows no syntax coloring :set syntax on is of no help. Though ls --color is working fine. I recently upgraded ncurses could that be the problem?? Any suggestion will be highly appreciated especialy from someone who faced similar problem before or Do I have to set some environment variable ?? i use testing version of vim and debian both Is this helpful: http://lists.debian.org/debian-user/2004/09/msg00233.html Exec. summary: Check your 'runtimepath'. -- The world's most effective spam filter: ln -sf /dev/full /var/mail/$USER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax
On Sun, Oct 26, 2003 at 08:53:22AM -0500, Gregory Seidman wrote: On Sun, Oct 26, 2003 at 05:25:01PM +1300, Paul William wrote: } Hi } } How do I have vim syntax highlighting always on instead of having to } type :syntax on? Add syntax on to your .vimrc or to '/etc/vim/vimrc' for other users, too -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax
On Sun, Oct 26, 2003 at 05:25:01PM +1300, Paul William wrote: } Hi } } How do I have vim syntax highlighting always on instead of having to } type :syntax on? Add syntax on to your .vimrc } Thanks } Paul --Greg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
vim syntax
Hi How do I have vim syntax highlighting always on instead of having to type :syntax on? Thanks Paul -- .''`. Paul William : :' :Debian admin and user `. `'` `- Debian - when you have better things to do than fixing a system -- .''`. Paul William : :' :Debian admin and user `. `'` `- Debian - when you have better things to do than fixing a system -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax
On Sun, Oct 26, 2003 at 05:41:05PM +1300, Paul William wrote: Hi How do I have vim syntax highlighting always on instead of having to type :syntax on? in .vimrc: syntax on Thanks Paul -- .''`. Paul William : :' :Debian admin and user `. `'` `- Debian - when you have better things to do than fixing a system -- .''`. Paul William : :' :Debian admin and user `. `'` `- Debian - when you have better things to do than fixing a system An extra sig? -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
vim syntax
Hi How do I have vim syntax highlighting always on instead of having to type :syntax on? Thanks Paul -- .''`. Paul William : :' :Debian admin and user `. `'` `- Debian - when you have better things to do than fixing a system -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax
Thanks for your help. On Sun, 2003-10-26 at 17:44, Bill Moseley wrote: On Sun, Oct 26, 2003 at 05:41:05PM +1300, Paul William wrote: Hi How do I have vim syntax highlighting always on instead of having to type :syntax on? in .vimrc: syntax on Thanks Paul -- .''`. Paul William : :' :Debian admin and user `. `'` `- Debian - when you have better things to do than fixing a system -- .''`. Paul William : :' :Debian admin and user `. `'` `- Debian - when you have better things to do than fixing a system An extra sig? -- Bill Moseley [EMAIL PROTECTED] -- .''`. Paul William : :' :Debian admin and user `. `'` `- Debian - when you have better things to do than fixing a system -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vim syntax
On Sun, Oct 26, 2003 at 05:41:05PM +1300, Paul William said Hi How do I have vim syntax highlighting always on instead of having to type :syntax on? Create a ~/.vimrc with this one line: syntax on and it will highlight whatever it can. -- Rob Weir [EMAIL PROTECTED] | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: top secret electronic surveillance monarchist Uzi Leitrim signature.asc Description: Digital signature
Uso de Vim, syntax
Hola, uso gvim, pero ahora necesito usar vim desde modo texto y no veo como instalar los archivos de sintasis para los diferentes lenguajes, estoy en otro ordenador que solo tiene el modo texto y busco con el apt-cache pero nada. Salu2 ___ Do You Yahoo!? Yahoo! Messenger Comunicación instantánea gratis con tu gente. http://messenger.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Uso de Vim, syntax
Hola: Según tengo entendido, el resaltar la sintaxis no viene en un paquete aparte, es algo de vim, pon en tu vimrc syntax on, aunque hay otras formas mejores de hacerlo, pero en este momento no recuerdo como eran (y no las tengo a mano). -- Atentamente, yo Matías Libertad para la Argentina On Sat, 11 May 2002 22:56:22 +0200 (CEST) Francisca Ceballos [EMAIL PROTECTED] wrote: Hola, uso gvim, pero ahora necesito usar vim desde modo texto y no veo como instalar los archivos de sintasis para los diferentes lenguajes, estoy en otro ordenador que solo tiene el modo texto y busco con el apt-cache pero nada. Salu2 ___ Do You Yahoo!? Yahoo! Messenger Comunicación instantánea gratis con tu gente. http://messenger.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Uso de Vim, syntax
--- Matias [EMAIL PROTECTED] escribió: Hola: Según tengo entendido, el resaltar la sintaxis no viene en un paquete aparte, es algo de vim, pon en tu vimrc syntax on, aunque hay otras formas mejores de hacerlo, pero en este momento no recuerdo como eran (y no las tengo a mano). No, la sintasis para el resaltado viene definida en diferentes archivos que son instalados, pero en la instalacion basica de Vim en debian potato no se han instalado... Yo lo tengo instalado en un sistema Read Hat y en windows usando gvim, pero en debian potato he instalado vim y no se han instalado... sino hay manera tendria que instalar manualmente los archivos de los lenguajes que utilizo, pero si hay forma de hacerlo con apt lo preferiria ___ Do You Yahoo!? Yahoo! Messenger Comunicación instantánea gratis con tu gente. http://messenger.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Uso de Vim, syntax
Hola, si no recuerdo mal en potato es vim-rt lo que tienes que instalar, en sid ya vienen con el vim Saludos. On Sat, May 11, 2002 at 11:09:30PM +0200, Francisca Ceballos wrote: --- Matias [EMAIL PROTECTED] escribió: Hola: Según tengo entendido, el resaltar la sintaxis no viene en un paquete aparte, es algo de vim, pon en tu vimrc syntax on, aunque hay otras formas mejores de hacerlo, pero en este momento no recuerdo como eran (y no las tengo a mano). No, la sintasis para el resaltado viene definida en diferentes archivos que son instalados, pero en la instalacion basica de Vim en debian potato no se han instalado... Yo lo tengo instalado en un sistema Read Hat y en windows usando gvim, pero en debian potato he instalado vim y no se han instalado... sino hay manera tendria que instalar manualmente los archivos de los lenguajes que utilizo, pero si hay forma de hacerlo con apt lo preferiria ___ Do You Yahoo!? Yahoo! Messenger Comunicación instantánea gratis con tu gente. http://messenger.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OT: vim syntax highlight on C program files only?
On Tue, Aug 28, 2001 at 01:18:43PM -0700, Karsten M. Self wrote: on Tue, Aug 28, 2001 at 08:31:18AM -0400, Rob Ransbottom ([EMAIL PROTECTED]) wrote: On Mon, 27 Aug 2001, Osamu Aoki wrote: Just a thought and matter of taste, but... You may also embed commands near the start of your file: :vi set tabstops=4 showmatch: Is there a setting which allows a tab to indent by 4 chars, but leaves tabstops at 8 chars, where most apps seem to expect to find them? I'm also curious as to the interaction between vim and indent, particularly the ~/.indent.pro preferences file, in vim's 'cindent' mode. I've found that with -kr4 set in my indent preferences file, I'm getting the desired behavior in vim with autoindentation, but I'm not convinced it's a causal relation. probably (sts and ts, i'd say) but just so we're clear, anyone found recommending the MIXTURE of spaces AND tabs for indentation should be shot in the head. wanna indent two spaces at a time? fine -- use two spaces, then four, six, eight, ten... never two, four, six, tab, tab+2... ALWAYS spaces or ALWAYS tabs. any cross-breeding is bound for trouble. not that i have any opinions on the matter. -- DEBIAN NEWBIE TIP #75 from USM Bish [EMAIL PROTECTED] : Do you want to have MUTT IGNORE PGP-SIGNED MESSAGES? To have mutt to *not* verify PGP-signed messages, you can shut it off by including set pgp_verify_sig = no in your ~/.muttrc Or you could use: set pgp_verify_sig = ask-no to have mutt prompt you each time a signed message comes up, with the default being not to verify. Also see http://newbieDoc.sourceForge.net/ ...
Re: OT: vim syntax highlight on C program files only?
On Tue, Sep 25, 2001 at 03:36:14AM -0500, will trillich wrote:
On Tue, Aug 28, 2001 at 01:18:43PM -0700, Karsten M. Self wrote:
Is there a setting which allows a tab to indent by 4 chars, but leaves
tabstops at 8 chars, where most apps seem to expect to find them?
'set softtabstop=4'
probably (sts and ts, i'd say) but just so we're clear, anyone
found recommending the MIXTURE of spaces AND tabs for
indentation should be shot in the head.
wanna indent two spaces at a time? fine -- use two spaces, then
four, six, eight, ten... never two, four, six, tab, tab+2...
I agree [1], except for one nice indenting strategy I've seen. Sometimes
you want to distinguish between indentation used for blocks and
indentation used for lining things up. I don't mind whether people use
spaces or tabs for blocks, but for lining things up it should always be
spaces.
For example (tabs here may be clobbered in transit, though):
if (function_call ((my_variable + other_variable) *
yet_another_variable)) {
foo ();
}
Before 'yet_another_variable' comes one tab followed by a load of
spaces. All other lines begin with tabs. That way, no matter what your
tabstop settings are, the various bits of the if will always be lined up
correctly.
Not that I actually have the discipline to practice what I preach all
the time, of course.
[1] Wow, I agreed with Will about something involving tabs!
--
Colin Watson [EMAIL PROTECTED]
Re: OT: vim syntax highlight on C program files only?
Karsten M. Self wrote: on Mon, Aug 27, 2001 at 06:52:48PM -0700, Erik Steffl ([EMAIL PROTECTED]) wrote: ... In particular, I'd like to enable syntax highlighting, and maybe get some ideas of what I should change to make things a bit more readable (some of my screen colors are very hard to read, particularly blue, also red, bolding them should help a lot). the gvim (opens vim in its own window) has much better colors since it is not limited to few colors that xterm uses (by default). Prefer working in xterms (well, rxvts). gvim has few advantages (apart from better colors) - it changes the cursor (block for command mode, vertical line for insert, half block for replace etc. (those are defaults)), when you split the window you can move the split border using mouse (depends on mouse mode you set) etc... not saying you should switch:-) [I usually use gvim for longer editing sessions and vi for shorter ones] also, set up your background (light or dark): set background=dark This has no effect. I'm already running gold (fg) on black (bg). it should have effect on syntax highlighting - if you say you are using dark background it will pick colors that are better for dark background. erik
Re: OT: vim syntax highlight on C program files only?
* Rob Hudson ([EMAIL PROTECTED]) wrote: I found stuff like this before and have been using it: When using mutt or slrn, text width=72 autocmd BufRead mutt*[0-9]set tw=72 autocmd BufRead .followup,.article,.letterset tw=72 Thank you very much. Rich
Re: OT: vim syntax highlight on C program files only?
Just a thought and matter of taste, but... For file like *.c, I understand use of auto command to set some settings. But for editing mail, I thought activating proper vim mode by the MUA configuration file may be more straight forward. For example, my ~/.muttrc or /etc/Muttrc has followng: set editor=vim -c 'set tw=72 et ft=mail' just an alternative, ciao, :-) On Mon, Aug 27, 2001 at 08:01:35PM -0700, Rob Hudson wrote: I found stuff like this before and have been using it: When using mutt or slrn, text width=72 autocmd BufRead mutt*[0-9]set tw=72 autocmd BufRead .followup,.article,.letterset tw=72 -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://www.aokiconsulting.com/quick/+
Re: vim syntax highlight on C program files only?
You need to tell vim that your terminal is white on black - it's defaulted to the opposite :-) A gas which obeys to the perfect gas equation is a perfect gas, where the perfect gas equation describes the relationship between pressure, volume and temperature of a perfect gas. - Original Message - From: Karsten M. Self kmself@ix.netcom.com To: debian-user debian-user@lists.debian.org Sent: Tuesday, August 28, 2001 9:26 AM Subject: OT: vim syntax highlight on C program files only?
Re: vim syntax highlight on C program files only?
on Tue, Aug 28, 2001 at 04:44:29PM +0800, Calvin Chong ([EMAIL PROTECTED]) wrote: You need to tell vim that your terminal is white on black - it's defaulted to the opposite :-) Ummany good way to do this? -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry! Boycott Adobe! Repeal the DMCA!http://www.freesklyarov.org Geek for Hirehttp://kmself.home.netcom.com/resume.html pgpEdVuWRMyqd.pgp Description: PGP signature
Re: vim syntax highlight on C program files only?
set background=dark syntax on -- A gas which obeys to the perfect gas equation is a perfect gas, where the perfect gas equation describes the relationship between pressure, volume and temperature of a perfect gas. - Original Message - From: Karsten M. Self kmself@ix.netcom.com To: debian-user debian-user@lists.debian.org Sent: Tuesday, August 28, 2001 4:58 PM Subject: Re: vim syntax highlight on C program files only?
Re: OT: vim syntax highlight on C program files only?
On Mon, 27 Aug 2001, Osamu Aoki wrote: Just a thought and matter of taste, but... You may also embed commands near the start of your file: :vi set tabstops=4 showmatch: This has the dwindling advantage of working with most of the vi clones. rob Live the dream.
Re: OT: vim syntax highlight on C program files only?
On Mon, Aug 27, 2001 at 06:26:41PM -0700, Karsten M. Self wrote: | I'm starting to play with C a bit. Discovering some nice things in vim. | | I know that there's an 'au' and 'augroup' commands, and that a number of | vim settings can be configured using these. I'm not sure what current | settings exist for C program files (matching pattern *.c), or how I | should use these settings to enable appropriate settings for programming | support. | | In particular, I'd like to enable syntax highlighting, and maybe get | some ideas of what I should change to make things a bit more readable | (some of my screen colors are very hard to read, particularly blue, also | red, bolding them should help a lot). You want something like the following : augroup C au! au FileType c syntax on You can also specify stuff like the cool auto-indenting feature and a length of the lines, or tab appearance au FileType c set ai si cin tw=80 fo=croq au FileType c set ts=8 sts=4 sw=4 et autocmd FileType c set comments=sr:/*,mb:*,ex:*/ augroup END For those trying to set vim properties for mail messages only, the easiest way is with the 'mail' type, as follows : au! FileType mail set tw=70 fo=tcq Personally I prefer having a dark background an light foreground. With gnome-terminal (or other xterms) this is set in it's config, but for gvim the following line sets it right : highlight Normal guibg=black guifg=grey90 A side effect of that, as Karsten pointed out, is that much of the syntax highlighting is dark and doesn't contrast well. The solution is to put : set background=dark makes syntax highlighing lighter before calling syntax on. If you put it after calling syntax on it will have no apparent effect. A side effect of this, though, is if you use a black-on-white terminal you will have a hard time seeing the really bright colors against the white background. If you use set bg=light followed by syn on you can correct that situation. HTH, -D
Re: OT: vim syntax highlight on C program files only?
on Tue, Aug 28, 2001 at 11:05:48AM -0400, dman ([EMAIL PROTECTED]) wrote: On Mon, Aug 27, 2001 at 06:26:41PM -0700, Karsten M. Self wrote: | I'm starting to play with C a bit. Discovering some nice things in vim. ... A side effect of that, as Karsten pointed out, is that much of the syntax highlighting is dark and doesn't contrast well. The solution is to put : set background=dark makes syntax highlighing lighter before calling syntax on. If you put it after calling syntax on it will have no apparent effect. Awesome. That's what I needed. Some nice suggestions here and elsewhere in this thread. Keepers. -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry! Boycott Adobe! Repeal the DMCA!http://www.freesklyarov.org Geek for Hirehttp://kmself.home.netcom.com/resume.html pgpiRNukWMnrl.pgp Description: PGP signature
Re: OT: vim syntax highlight on C program files only?
on Tue, Aug 28, 2001 at 08:31:18AM -0400, Rob Ransbottom ([EMAIL PROTECTED]) wrote: On Mon, 27 Aug 2001, Osamu Aoki wrote: Just a thought and matter of taste, but... You may also embed commands near the start of your file: :vi set tabstops=4 showmatch: Is there a setting which allows a tab to indent by 4 chars, but leaves tabstops at 8 chars, where most apps seem to expect to find them? I'm also curious as to the interaction between vim and indent, particularly the ~/.indent.pro preferences file, in vim's 'cindent' mode. I've found that with -kr4 set in my indent preferences file, I'm getting the desired behavior in vim with autoindentation, but I'm not convinced it's a causal relation. -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry! Boycott Adobe! Repeal the DMCA!http://www.freesklyarov.org Geek for Hirehttp://kmself.home.netcom.com/resume.html pgpW6l2qXaIja.pgp Description: PGP signature
Re: OT: vim syntax highlight on C program files only?
On Tue, Aug 28, 2001 at 01:18:43PM -0700, Karsten M. Self wrote: | on Tue, Aug 28, 2001 at 08:31:18AM -0400, Rob Ransbottom ([EMAIL PROTECTED]) wrote: | On Mon, 27 Aug 2001, Osamu Aoki wrote: | | Just a thought and matter of taste, but... | | You may also embed commands near the start of your file: | |:vi set tabstops=4 showmatch: | | Is there a setting which allows a tab to indent by 4 chars, but leaves | tabstops at 8 chars, where most apps seem to expect to find them? See my example. The key settings are softtabstop and shiftwidth, which can be abbreviated sts and sw respectively. | I'm also curious as to the interaction between vim and indent, | particularly the ~/.indent.pro preferences file, in vim's 'cindent' | mode. I've found that with -kr4 set in my indent preferences file, I'm | getting the desired behavior in vim with autoindentation, but I'm not | convinced it's a causal relation. I didn't think vim used any external files to control it's indenting behavior but I could be wrong. Vim's cindent mode is controlled by the 'cinwords' and other variables inside of vim. -D
OT: vim syntax highlight on C program files only?
I'm starting to play with C a bit. Discovering some nice things in vim. I know that there's an 'au' and 'augroup' commands, and that a number of vim settings can be configured using these. I'm not sure what current settings exist for C program files (matching pattern *.c), or how I should use these settings to enable appropriate settings for programming support. In particular, I'd like to enable syntax highlighting, and maybe get some ideas of what I should change to make things a bit more readable (some of my screen colors are very hard to read, particularly blue, also red, bolding them should help a lot). Cheers. -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry! Boycott Adobe! Repeal the DMCA!http://www.freesklyarov.org Geek for Hirehttp://kmself.home.netcom.com/resume.html pgpdQukjZPzn3.pgp Description: PGP signature
Re: OT: vim syntax highlight on C program files only?
Karsten M. Self wrote: I'm starting to play with C a bit. Discovering some nice things in vim. I know that there's an 'au' and 'augroup' commands, and that a number of vim settings can be configured using these. I'm not sure what current settings exist for C program files (matching pattern *.c), or how I should use these settings to enable appropriate settings for programming support. if you install vim-rt the syntax highlighting should work on most files. put: syntax on into your ~/.vimrc In particular, I'd like to enable syntax highlighting, and maybe get some ideas of what I should change to make things a bit more readable (some of my screen colors are very hard to read, particularly blue, also red, bolding them should help a lot). the gvim (opens vim in its own window) has much better colors since it is not limited to few colors that xterm uses (by default). also, set up your background (light or dark): set background=dark erik
Re: OT: vim syntax highlight on C program files only?
On Mon, Aug 27, 2001 at 06:52:48PM -0700, Erik Steffl wrote: Karsten M. Self wrote: I know that there's an 'au' and 'augroup' commands, and that a number of vim settings can be configured using these. I'm not sure what current settings exist for C program files (matching pattern *.c), or how I should use these settings to enable appropriate settings for programming support. put: syntax on into your ~/.vimrc Another location is to check id /etc/vimrc. There is more comments so idiot like me can set it right. -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://www.aokiconsulting.com/quick/+
Re: OT: vim syntax highlight on C program files only?
on Mon, Aug 27, 2001 at 06:52:48PM -0700, Erik Steffl ([EMAIL PROTECTED]) wrote: Karsten M. Self wrote: I'm starting to play with C a bit. Discovering some nice things in vim. I know that there's an 'au' and 'augroup' commands, and that a number of vim settings can be configured using these. I'm not sure what current settings exist for C program files (matching pattern *.c), or how I should use these settings to enable appropriate settings for programming support. if you install vim-rt the syntax highlighting should work on most files. put: syntax on into your ~/.vimrc I'd rather not as I'm very used to not having syntax highlighting in shell scripts, and find it distracting. Hence the conditional activation. In particular, I'd like to enable syntax highlighting, and maybe get some ideas of what I should change to make things a bit more readable (some of my screen colors are very hard to read, particularly blue, also red, bolding them should help a lot). the gvim (opens vim in its own window) has much better colors since it is not limited to few colors that xterm uses (by default). Prefer working in xterms (well, rxvts). also, set up your background (light or dark): set background=dark This has no effect. I'm already running gold (fg) on black (bg). -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry! Boycott Adobe! Repeal the DMCA!http://www.freesklyarov.org Geek for Hirehttp://kmself.home.netcom.com/resume.html pgpgyg1LHfuZI.pgp Description: PGP signature
Re: OT: vim syntax highlight on C program files only?
on Mon, Aug 27, 2001 at 06:59:56PM -0700, Osamu Aoki ([EMAIL PROTECTED]) wrote: On Mon, Aug 27, 2001 at 06:52:48PM -0700, Erik Steffl wrote: Karsten M. Self wrote: I know that there's an 'au' and 'augroup' commands, and that a number of vim settings can be configured using these. I'm not sure what current settings exist for C program files (matching pattern *.c), or how I should use these settings to enable appropriate settings for programming support. put: syntax on into your ~/.vimrc Another location is to check id /etc/vimrc. There is more comments so idiot like me can set it right. Thanks. Found the 'augroup cprog' stanza there. -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry! Boycott Adobe! Repeal the DMCA!http://www.freesklyarov.org Geek for Hirehttp://kmself.home.netcom.com/resume.html pgpENMOgrrgRb.pgp Description: PGP signature
Re: OT: vim syntax highlight on C program files only?
I found stuff like this before and have been using it: When using mutt or slrn, text width=72 autocmd BufRead mutt*[0-9]set tw=72 autocmd BufRead .followup,.article,.letterset tw=72 Text files have a text width of 72 characters autocmd BufNewFile *.txt set tw=72 autocmd BufRead*.txt set tw=72 I'm sure the same could be said for C files, like so: autocmd BufNewFile *.cset formatoptions=croql cindent autocmd BufRead*.cset formatoptions=croql cindent -Rob On 20010827.1826, Karsten M. Self said ... I'm starting to play with C a bit. Discovering some nice things in vim. I know that there's an 'au' and 'augroup' commands, and that a number of vim settings can be configured using these. I'm not sure what current settings exist for C program files (matching pattern *.c), or how I should use these settings to enable appropriate settings for programming support. In particular, I'd like to enable syntax highlighting, and maybe get some ideas of what I should change to make things a bit more readable (some of my screen colors are very hard to read, particularly blue, also red, bolding them should help a lot). Cheers. -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry! Boycott Adobe! Repeal the DMCA!http://www.freesklyarov.org Geek for Hirehttp://kmself.home.netcom.com/resume.html Random Quote: A morning without coffee is like something without something else...
testing upgrade loses vim syntax coloring
The vim in testing tries to access '/usr/share/vim/syntax' but that directory is in '/usr/share/vim/vim56/syntax'. I created a symbolic link and now no longer get the error messages but following up in slrn doesn't give me colors. -- Certain nations seem particularly liable to fall prey to governmental plunder. They are those in which men, lacking faith in their own dignity and capability, would feel themselves lost if they were not governed and administered every step of the way. -- Fr?d?ric Bastiat (1801-1850) Rick Pasotto[EMAIL PROTECTED]http://www.niof.net
Re: vim syntax files
Previously Alisdair McDiarmid wrote: I have (well, had) a set of customised vim syntax command in the /usr/share/vim/vim54/syntax/synload.vim file. I just upgraded to vim[-rt] 5.4.21 and lost all my syntax settings. Is the file likely to be backed up anywhere or anything? No. You should add the extra syntax-commands in /etc/vimrc. Wichert. pgptVxpBibqhj.pgp Description: PGP signature
Re: vim syntax files
On Fri, Aug 13, 1999 at 21:04 +0100, Alisdair McDiarmid wrote: I have (well, had) a set of customised vim syntax command in the /usr/share/vim/vim54/syntax/synload.vim file. I just upgraded to vim[-rt] 5.4.21 and lost all my syntax settings. Is the file likely to be backed up anywhere or anything? Anyway, I guess this is probably my fault for doing things wrong, but where else can I put these syntax settings? I'm sure I didn't concede to overwriting these files on install, and I don't want to lose the settings next time I upgrade. Where else should they go? I simply copied the syntax file to my home dir, and put the line source ~/.vim_syntax in my .vimrc (thanks to whoever it was who suggested that to me). Cheers Dave -- Dave Swegen | Debian 2.1 on Linux i386 2.2.3 [EMAIL PROTECTED] | PGP key available on request [EMAIL PROTECTED] | Linux: The Choice of a GNU Generation ---
vim syntax files
I have (well, had) a set of customised vim syntax command in the /usr/share/vim/vim54/syntax/synload.vim file. I just upgraded to vim[-rt] 5.4.21 and lost all my syntax settings. Is the file likely to be backed up anywhere or anything? Anyway, I guess this is probably my fault for doing things wrong, but where else can I put these syntax settings? I'm sure I didn't concede to overwriting these files on install, and I don't want to lose the settings next time I upgrade. Where else should they go? -- alisdair mcdiarmid[EMAIL PROTECTED] [if you see some guy spit on me knock him on the side of the head]
Re: vim syntax files
Friday, August 13, 1999, 1:04:25 PM, Alisdair wrote: Anyway, I guess this is probably my fault for doing things wrong, but where else can I put these syntax settings? I'm sure I didn't concede to overwriting these files on install, and I don't want to lose the settings next time I upgrade. Where else should they go? Have your .vimrc point to a main syntax file that is local that also points to syntax files that are local. -- Steve C. Lamb | I'm your priest, I'm your shrink, I'm your ICQ: 5107343 | main connection to the switchboard of souls. ---+-
Re: vim syntax files
:help mysyntaxfile Personally, I don't bother with that stuff, and just edit the default global syntax files directly (they're owned by me, not root). I know I shouldn't do that; however, because I tend not to trust dpkg, I compile install vim myself (into /usr/local/), and therefore don't have to worry about arrogant package programs screwing me up. BTW, I'm disappointed with vim's default syntax files (specif., C and Java, although Perl's is actually pretty good); does anyone have or know where I could find better ones instead of having to hack them myself? This is not entirely relevant, but I just thought of something: a vi quine. I've got `2i2i', but that leaves off the esc -- it would take a lot of fumbling around with ^V's and ^['s to get it right, but it must be possible
vim syntax colors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just started using vim a few weeks ago and really love it! Anyway, when I run vim in X (not gvim, just vim in an xterm) the colors are different than those vim uses when at the console. I like the color scheme of the console better (for example, the blue used for comments while in X is impossible to read, along with some other colors). I'm using vim from slink btw. So how do I change the colors vim uses? I'd like to just tell vim to use the colors that I get while in console mode, and modify from there, but whatever. tia, Chris - Visit Me At http://www.frostnet.advicom.net/chris/ - -- Public PGP Key: Email [EMAIL PROTECTED] with the subject retrieve pgpkey or visit http://www.frostnet.advicom.net/chris/pgp_key.phtml -BEGIN PGP SIGNATURE- Version: PGP for Personal Privacy 5.0 Charset: noconv iQA/AwUBNn6gJeEzIlbKpewXEQK26gCeKZBG0f4DiQYykbjF25bYCjgxbXQAnj2c wSvz91LaY6NMPmAmGo3lTL/d =bzPJ -END PGP SIGNATURE-
