;>> 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 = *\'* ]] && ...
>>
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/v
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
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
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/50e5edd51003010556p1
; 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:i
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 o
6 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
>> >>
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,
>>
>&
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 w
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
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 color
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: [E
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 especi
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 env
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
>
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 "unsubs
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 PROTE
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:
>
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 [EM
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
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 W
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'
>
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 st
"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 color
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 star
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 whi
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
> sy
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
| settin
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.
ian-user"
Sent: Tuesday, August 28, 2001 4:58 PM
Subject: 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 http://kmself.home.netcom.com/
What part of "Gestalt
ssage -
From: "Karsten M. Self"
To: "debian-user"
Sent: Tuesday, August 28, 2001 9:26 AM
Subject: 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 e
* 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
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
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
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 con
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 *.
"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 (matchin
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 th
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 particular
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
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
: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
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.
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
-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
48 matches
Mail list logo
