* A.J.Mechelynck [060831 02:48]:
> Hmmm... it seems you configured a nonstandard location for your system
> vimrc and gvimrc.
I have CFLAGS with escaped quotes. Backslashes should be escaped
too.
> ; compiling pathdef.c gives me no errors or warnings whatsoever. How did
> you configure yours?
A.J.Mechelynck wrote:
> David Brown wrote:
>> What I'm having difficulty with is figuring out what to put there. Is
>> there a way of finding out what region a given part of the buffer is in?
>
> I'm not a specialist of these matters; but try help completion on synID
Well, I did figure out how
David Brown wrote:
I'm trying to get cweb.vim to work better, and am not sure how to go
about this.
Most of a cweb file is regular TeX (or LaTeX), with some occasional regions
that are C code. The way it is implemented now, works with simple
constructs.
However, tex.vim frequently will enclos
I'm trying to get cweb.vim to work better, and am not sure how to go
about this.
Most of a cweb file is regular TeX (or LaTeX), with some occasional regions
that are C code. The way it is implemented now, works with simple
constructs.
However, tex.vim frequently will enclose large sections of
Alexey I. Froloff wrote:
* A.J.Mechelynck [060831 01:48]:
If I misunderstood, please be more specific: do you or don't you want to
override the filetype detected by filetype.vim ?
No. Not override, but extend as if it was done in filetype.vim.
What user scripts can break with this changes?
Alexey I. Froloff wrote:
There is QUOTESED expression for creating auto/pathdef.c:
QUOTESED = sed -e 's/"/\\"/g' -e 's/\\"/"/' -e 's/\\";$$/";/'
...
@echo 'char_u *default_vim_dir = (char_u *)"$(VIMRCLOC)";' | $(QUOTESED) >> $@
However:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -pipe -Wall -O2
* A.J.Mechelynck [060831 01:48]:
> If I misunderstood, please be more specific: do you or don't you want to
> override the filetype detected by filetype.vim ?
No. Not override, but extend as if it was done in filetype.vim.
What user scripts can break with this changes?
--
Regards,
Sir Raorn.
Alexey I. Froloff wrote:
* Bram Moolenaar [060831 00:14]:
The current method is correct. In the ftdetect scripts you can check
for 'filetype' being equal to "conf" and then do ":set ft=anything" to
overrule it. Use ":setf" only when you don't want to overrule the
default filetype.
I want the
There is QUOTESED expression for creating auto/pathdef.c:
QUOTESED = sed -e 's/"/\\"/g' -e 's/\\"/"/' -e 's/\\";$$/";/'
...
@echo 'char_u *default_vim_dir = (char_u *)"$(VIMRCLOC)";' | $(QUOTESED) >> $@
However:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -pipe -Wall -O2 -march=pentium4
-DSYS_VIMR
On Wed, Aug 30, 2006 at 10:12:44PM +0200, Bram Moolenaar wrote:
> > > Apparently the sorbs blacklist mechanism is still being used, causing
> > > trouble for some people. I have asked the mail server maintainer to
> > > remove sorbs a few times now...
> >
> > Twice recently, sorbs has bounced my
On 8/30/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Benji Fisher wrote:
> On Sun, Aug 27, 2006 at 02:40:24PM +0200, Bram Moolenaar wrote:
> >
> > Apparently the sorbs blacklist mechanism is still being used, causing
> > trouble for some people. I have asked the mail server maintainer to
> >
* Bram Moolenaar [060831 00:14]:
> The current method is correct. In the ftdetect scripts you can check
> for 'filetype' being equal to "conf" and then do ":set ft=anything" to
> overrule it. Use ":setf" only when you don't want to overrule the
> default filetype.
I want these files act as "defa
* A.J.Mechelynck [060830 23:53]:
> 1. You should never create, delete or modify any file in the $VIMRUNTIME
By "$VIMRUNTIME" I mean &rtp. Those file comes modified from
vim-* rpm packages and I just want to _package_ system-specific
settings in separate file instead of rediff'ing patch for every
Yakov Lerner wrote:
When 'acd' is set, 'vim -S' open files in wrong directory.
To reproduce:
1. make your ~/.vimrc 1-liner 'set acd'
(Alternatively, use use "vim -u NONE -c 'set acd'" instead of vim
in commands below).
2. vim ~/xxx# or
:he options.txt
" now you have two
Benji Fisher wrote:
> On Sun, Aug 27, 2006 at 02:40:24PM +0200, Bram Moolenaar wrote:
> >
> > Apparently the sorbs blacklist mechanism is still being used, causing
> > trouble for some people. I have asked the mail server maintainer to
> > remove sorbs a few times now...
>
> Twice recentl
Alexey I. Froloff wrote:
> filetype.vim looks like:
>
> augroup filetypedetect
>
> ...
>
> " Generic configuration file (check this last, it's just guessing!)
> au BufNewFile,BufRead,StdinReadPost *
> \ ... some files are being setf'ed to "conf"
>
> " Use the plugin-filetype checks la
Alexey I. Froloff wrote:
filetype.vim looks like:
augroup filetypedetect
...
" Generic configuration file (check this last, it's just guessing!)
au BufNewFile,BufRead,StdinReadPost *
\ ... some files are being setf'ed to "conf"
" Use the plugin-filetype checks last, they may overrule
Alexey I. Froloff wrote:
filetype.vim looks like:
augroup filetypedetect
...
" Generic configuration file (check this last, it's just guessing!)
au BufNewFile,BufRead,StdinReadPost *
\ ... some files are being setf'ed to "conf"
" Use the plugin-filetype checks last, they may overrule
Gautam Iyer wrote:
On Wed, Aug 30, 2006 at 07:17:16PM +0200, Stefano Zacchiroli wrote:
I agree with the comment that plain TeX users may also define such
sectioning commands. Maybe it would be safe if you check for such
definitions, using an include-file search ... but of course, that is
more
When 'acd' is set, 'vim -S' open files in wrong directory.
To reproduce:
1. make your ~/.vimrc 1-liner 'set acd'
(Alternatively, use use "vim -u NONE -c 'set acd'" instead of vim
in commands below).
2. vim ~/xxx# or
:he options.txt
" now you have two files open: (1) ~/xxx
* Alexey I. Froloff [060830 21:21]:
> Solution is simple - source ftdetect/*.vim before "conf"
> fallback.
Also, it would be nice to use StarSetf() from ftdetect/*.vim...
--
Regards,
Sir Raorn.
signature.asc
Description: Digital signature
On Wed, Aug 30, 2006 at 07:17:16PM +0200, Stefano Zacchiroli wrote:
> > I agree with the comment that plain TeX users may also define such
> > sectioning commands. Maybe it would be safe if you check for such
> > definitions, using an include-file search ... but of course, that is
> > more conven
filetype.vim looks like:
augroup filetypedetect
...
" Generic configuration file (check this last, it's just guessing!)
au BufNewFile,BufRead,StdinReadPost *
\ ... some files are being setf'ed to "conf"
" Use the plugin-filetype checks last, they may overrule any of the previously
" det
On Wed, Aug 30, 2006 at 08:42:52AM -0400, Benji Fisher wrote:
> If you maintain a vim package (for Debian, guessing from your
> sig?), then you can always define g:tex_flavor in a system vimrc if you
> want. BTW, the documentation for this is under
Yes, sure, I was proposing it to you assumi
On 8/30/06, Chris Littell <[EMAIL PROTECTED]> wrote:
On 8/30/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> In C99 you can initialize values "out of order", yes, but you can't do
> it with ranges. Ranges are a GNU C extension. The propagation
> neither happens in any of the ANSI standards, no
On 8/30/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
On 8/30/06, Chris Littell <[EMAIL PROTECTED]> wrote:
> On 8/30/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> > On 8/29/06, Brad Beveridge <[EMAIL PROTECTED]> wrote:
> > > On 29/08/06, Ilya <[EMAIL PROTECTED]> wrote:
> > > > Brad Beveridge
On 8/30/06, Chris Littell <[EMAIL PROTECTED]> wrote:
On 8/30/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> On 8/29/06, Brad Beveridge <[EMAIL PROTECTED]> wrote:
> > On 29/08/06, Ilya <[EMAIL PROTECTED]> wrote:
> > > Brad Beveridge wrote:
> > > >static char string[2] = {0};
> > > Should not
On Wed, Aug 30, 2006 at 08:57:13AM -0400, Chris Littell wrote:
> On 8/30/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> >On 8/29/06, Brad Beveridge <[EMAIL PROTECTED]> wrote:
> >> On 29/08/06, Ilya <[EMAIL PROTECTED]> wrote:
> >> > Brad Beveridge wrote:
> >> > >static char string[2] = {0};
>
On Sun, Aug 27, 2006 at 02:40:24PM +0200, Bram Moolenaar wrote:
>
> Apparently the sorbs blacklist mechanism is still being used, causing
> trouble for some people. I have asked the mail server maintainer to
> remove sorbs a few times now...
Twice recently, sorbs has bounced my mails to the
On Tue, Aug 29, 2006 at 09:16:41PM +0200, Stefano Zacchiroli wrote:
> On Tue, Aug 29, 2006 at 03:06:39PM -0400, Benji Fisher wrote:
> > I do not think there is any reliable way to distinguish between
> > plain TeX and LaTeX. After my RFC, I decided to treat plain TeX as the
> > default, since
On 8/30/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
On 8/29/06, Brad Beveridge <[EMAIL PROTECTED]> wrote:
> On 29/08/06, Ilya <[EMAIL PROTECTED]> wrote:
> > Brad Beveridge wrote:
> > >static char string[2] = {0};
> > Should not you have "= {0, 0}" here? Second element never get
> > initia
On 8/29/06, Brad Beveridge <[EMAIL PROTECTED]> wrote:
On 29/08/06, Ilya <[EMAIL PROTECTED]> wrote:
> Brad Beveridge wrote:
> >static char string[2] = {0};
> Should not you have "= {0, 0}" here? Second element never get
> initialized but it could be accessed by ml_append_string.
That might b
32 matches
Mail list logo
