On Tue, Feb 06, 2007 at 03:27:02AM -0500, Manu Hack wrote:
> >I noticed that vim-latexsuite no longer worked with vim 7.x whereas it
> >was working with vim 6.x. Filed a bug against vim-latexsuite but no
> >reply.
>
> yes, I reported the F5 problem and maybe they are working on it.
Interesting.
I
I noticed that vim-latexsuite no longer worked with vim 7.x whereas it
was working with vim 6.x. Filed a bug against vim-latexsuite but no
reply.
yes, I reported the F5 problem and maybe they are working on it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tro
On Sun, Feb 04, 2007 at 10:45:08PM -0500, Stephen wrote:
> > seems autodetection of the filetype is not working (?)
>
> Yup. I'm surprised that no one else upgrading from Sarge to Etch has
> experienced this either. I had a vanilla Sarge.
I noticed that vim-latexsuite no longer worked with vim 7
Update:
Getting a little frustrated, I aptitude purged all my vim files. I then
re-installed 'vim vim-common vim-runtime'. I now have colour syntax
hi-lighting back.
I know it's not the proper way to fix things, but damn, I tried to do it
the right way.
Thanks again for the assistance !
--
Re
On Mon, Feb 05, 2007 at 06:35:29PM -0500 or thereabouts, cga2000 wrote:
> On Sun, Feb 04, 2007 at 03:26:42PM EST, Stephen wrote:
> > On Sun, Feb 04, 2007 at 12:55:01PM -0500 or thereabouts, Michael Pobega
> > wrote:
> >
> > > I'm not asking for help, I'm offering it. I think the problem is just
On Sun, Feb 04, 2007 at 03:26:42PM EST, Stephen wrote:
> On Sun, Feb 04, 2007 at 12:55:01PM -0500 or thereabouts, Michael Pobega wrote:
>
> > I'm not asking for help, I'm offering it. I think the problem is just a
> > Debian based distro thing, because none of them come with vim-full
> > insta
On Mon, Feb 05, 2007 at 04:21:16PM +0800 or thereabouts, breeze50 wrote:
> I think the version you installed is vim-tiny, it don't include
> [syntax] function.
Actually no, but I would have agreed with you earlier on in this thread, when I
installed vim-full. I guess you haven't bothered reading
On Mon, Feb 05, 2007 at 09:28:06PM +1300 or thereabouts, Chris Bannister wrote:
Hi Chris:
> What type of file are you trying to edit? What error message do you get?
> Is this with a clean .vimrc file?
Yes, the skeleton sample from the install, and I've been trying this primarily
on *.php files,
2007/2/5, Chris Bannister <[EMAIL PROTECTED]>:
On Sat, Feb 03, 2007 at 08:53:27PM -0500, Stephen wrote:
> On Sun, Feb 04, 2007 at 12:31:29AM + or thereabouts, Liam O'Toole wrote:
> > On Sat, 3 Feb 2007 01:44:18 -0500
> > Stephen <[EMAIL PROTECTED]> wrote:
> >
> > > Hello Friends:
> > >
> > >
On Sat, Feb 03, 2007 at 08:53:27PM -0500, Stephen wrote:
> On Sun, Feb 04, 2007 at 12:31:29AM + or thereabouts, Liam O'Toole wrote:
> > On Sat, 3 Feb 2007 01:44:18 -0500
> > Stephen <[EMAIL PROTECTED]> wrote:
> >
> > > Hello Friends:
> > >
> > > After upgrading to Etch, vim doesn't show colou
On Sun, Feb 04, 2007 at 09:56:26PM -0500 or thereabouts, cga2000 wrote:
> On Sun, Feb 04, 2007 at 08:54:18PM EST, Stephen wrote:
[ ...]
> > That didn't produce anything.
>
> I meant :colorscheme + .. not :colorscheme +
Yup that's what I did.
> But that could very well be the case .. I don't h
On Sun, Feb 04, 2007 at 08:54:18PM EST, Stephen wrote:
> On Sun, Feb 04, 2007 at 07:42:28PM -0500 or thereabouts, cga2000 wrote:
>
> [ ...]
>
> > In vim, you could try:
> >
> > :colorscheme
>
> That didn't produce anything.
I meant :colorscheme + .. not :colorscheme +
But that could very wel
On Sun, Feb 04, 2007 at 07:42:28PM -0500 or thereabouts, cga2000 wrote:
[ ...]
> In vim, you could try:
>
> :colorscheme
That didn't produce anything.
I'm been playing around with this on my own a bit. When I ':syntax enable' I'm
returned;
Error detected while processing /usr/
On Sun, Feb 04, 2007 at 03:20:25PM EST, Stephen wrote:
> On Sun, Feb 04, 2007 at 12:12:38PM -0500 or thereabouts, cga2000 wrote:
>
> > Other things the OP could check:
>
> OK I'm trying the following on a *.php file.
>
> > :set compatible?
>
> nocompatible
looks ok -- vim has a "bare vi" mode
On Sun, Feb 04, 2007 at 01:10:53PM -0500 or thereabouts, cga2000 wrote:
> I thought the OP had already tried the vim-full fix.
I did/had.
[ ...]
> I was suggesting a different approach -- ie. ask the vim list where you
> will quickly be provided with info as to the various options you have
> as
On Sun, Feb 04, 2007 at 12:55:01PM -0500 or thereabouts, Michael Pobega wrote:
> I'm not asking for help, I'm offering it. I think the problem is just a
> Debian based distro thing, because none of them come with vim-full
> installed by default (As far as I know). vim-full is the package you
On Sun, Feb 04, 2007 at 12:12:38PM -0500 or thereabouts, cga2000 wrote:
> Other things the OP could check:
OK I'm trying the following on a *.php file.
> :set compatible?
nocompatible
> :set t_Co?
t_Co=8
> :echo g:colors_name
Two errors.
E121: Undefined variable: g:colors_name
E15: Invali
On Sun, Feb 04, 2007 at 09:58:08AM -0500 or thereabouts, cga2000 wrote:
> On Sat, Feb 03, 2007 at 08:51:03PM EST, Stephen wrote:
> > I'm baffled, I've searched in the suspect places, but I don't see anything
> > obvious, (at least to me).
>
> output of:
>
> $ vim --version
OK cga2000, you aske
On Sun, Feb 04, 2007 at 12:55:01PM EST, Michael Pobega wrote:
> cga2000 wrote:
> >You should have posted on the vim@vim.org mailing list.
> I'm not asking for help, I'm offering it.
I thought the OP had already tried the vim-full fix.
> I think the problem is just a Debian based distro t
cga2000 wrote:
On Sun, Feb 04, 2007 at 10:59:47AM EST, Michael Pobega wrote:
cga2000 wrote:
On Sat, Feb 03, 2007 at 08:51:03PM EST, Stephen wrote:
output of:
$ vim --version
?
Actually, just /sudo aptitude install vim-full.
???
among other things, v
On Sun, Feb 04, 2007 at 10:59:47AM EST, Michael Pobega wrote:
> cga2000 wrote:
> >On Sat, Feb 03, 2007 at 08:51:03PM EST, Stephen wrote:
> >output of:
> >
> >$ vim --version
> >
> >?
> Actually, just /sudo aptitude install vim-full/.
???
among other things, vim --version lists the capabiliti
cga2000 wrote:
On Sat, Feb 03, 2007 at 08:51:03PM EST, Stephen wrote:
On Sat, Feb 03, 2007 at 05:32:35PM +0100 or thereabouts, Mathias Brodala wrote:
I've checked all the places I can find a vimrc and/or .vimrc, ensuring that
each has 'syntax on'. Still, I'm not getting syntax colourin
On Sun, Feb 04, 2007 at 08:15:43AM +0200 or thereabouts, Mehmet Fatih Akbulut
wrote:
> hi again,
Hi Mehmet:
> these are the packages installed on my system related with vim.
> and with the 'vimrc' file that i sent in my previous mail, everything works
> great.
Interesting, I have the same, ex
On Sat, Feb 03, 2007 at 08:51:03PM EST, Stephen wrote:
> On Sat, Feb 03, 2007 at 05:32:35PM +0100 or thereabouts, Mathias Brodala
> wrote:
>
> > >>> I've checked all the places I can find a vimrc and/or .vimrc, ensuring
> > >>> that
> > >>> each has 'syntax on'. Still, I'm not getting syntax col
hi again,
[~]> dpkg -l vim* | grep ii
ii vim-common 7.0-164+3 Vi IMproved - Common files
ii vim-full 7.0-164+3 Vi IMproved - enhanced vi editor - full
fled
ii vim-gui-common 7.0-164+3 Vi IMproved - Common GUI files
ii vim-runtime7.0-164+3 Vi IMproved - Runtim
On Sun, Feb 04, 2007 at 12:58:22AM +0200 or thereabouts, Mehmet Fatih Akbulut
wrote:
> put the attached file in your home directory as .vimrc
> it contains a lot of useful options (syntax highlight, line numbers, cursor
> position ... etc) for vim.
Mehmet:
Thanks. I tried it out, still no colour
On Sun, Feb 04, 2007 at 12:31:29AM + or thereabouts, Liam O'Toole wrote:
> On Sat, 3 Feb 2007 01:44:18 -0500
> Stephen <[EMAIL PROTECTED]> wrote:
>
> > Hello Friends:
> >
> > After upgrading to Etch, vim doesn't show colour syntax anymore.
> >
> > I've checked all the places I can find a vim
On Sat, Feb 03, 2007 at 05:32:35PM +0100 or thereabouts, Mathias Brodala wrote:
> >>> I've checked all the places I can find a vimrc and/or .vimrc, ensuring
> >>> that
> >>> each has 'syntax on'. Still, I'm not getting syntax colouring.
> >
> >> apt-get install vim-runtime
> >
> > I had|have th
On Sat, 3 Feb 2007 01:44:18 -0500
Stephen <[EMAIL PROTECTED]> wrote:
> Hello Friends:
>
> After upgrading to Etch, vim doesn't show colour syntax anymore.
>
> I've checked all the places I can find a vimrc and/or .vimrc,
> ensuring that each has 'syntax on'. Still, I'm not getting syntax
> colou
put the attached file in your home directory as .vimrc
it contains a lot of useful options (syntax highlight, line numbers, cursor
position ... etc) for vim.
On 2/3/07, Stephen <[EMAIL PROTECTED]> wrote:
Hello Friends:
After upgrading to Etch, vim doesn't show colour syntax anymore.
I've chec
Hello Stephen.
Stephen, 03.02.2007 16:56:
>> On Sat, Feb 03, 2007 at 09:30:26AM +0100 or thereabouts, Gerard Robin wrote:
>
>>> On Sat, Feb 03, 2007 at 01:44:18AM -0500, Stephen wrote:
>>> From: Stephen <[EMAIL PROTECTED]>
>
>>> After upgrading to Etch, vim doesn't show colour syntax anymore.
>
>On Sat, Feb 03, 2007 at 09:30:26AM +0100 or thereabouts, Gerard Robin wrote:
>> On Sat, Feb 03, 2007 at 01:44:18AM -0500, Stephen wrote:
>>From: Stephen <[EMAIL PROTECTED]>
>> After upgrading to Etch, vim doesn't show colour syntax anymore.
>>I've checked all the places I can find a vimrc and/o
On Sat, Feb 03, 2007 at 01:44:18AM -0500, Stephen wrote:
From: Stephen <[EMAIL PROTECTED]>
To: debian
Subject: Vim colour syntax
After upgrading to Etch, vim doesn't show colour syntax anymore.
I've checked all the places I can find a vimrc and/or .vimrc, ensuring that
eac
Hello Friends:
After upgrading to Etch, vim doesn't show colour syntax anymore.
I've checked all the places I can find a vimrc and/or .vimrc, ensuring that
each has 'syntax on'. Still, I'm not getting syntax colouring.
Any ideas?
--
Regards
Stephen A.
34 matches
Mail list logo
