On 6/19/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Yakov Lerner wrote:
> After the following patch, the output is better. Two out of
> three 'readonly' lines are now in place.
>
> --- message.c.000 2006-06-19 02:49:34.0 +0300
> +++ message.c 2006-06-19 02:52:41.0 +0300
Bram Moolenaar wrote:
Yakov Lerner wrote:
In case you can't reproduce it, Bram, I' attaching the output
with all escape sequences. The output was taken using
vim -u /tmp/1 /tmp/1 | tee >/tmp/output
It clearly shows how the three delayed 'readonly readonly readonly'
are printed *afer* vim u
Yakov Lerner wrote:
> In case you can't reproduce it, Bram, I' attaching the output
> with all escape sequences. The output was taken using
> vim -u /tmp/1 /tmp/1 | tee >/tmp/output
> It clearly shows how the three delayed 'readonly readonly readonly'
> are printed *afer* vim uninitialized t
On 6/18/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
On 6/18/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>
> Yakov Lerner wrote:
>
> > > On 5/23/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> > > > create a file ~/.vimtest as follows:
> > > >
> > > > cat > .vimtest
> > > > set nocompatible
> > >
Yakov Lerner wrote:
On 6/18/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Yakov Lerner wrote:
> > On 5/23/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> > > create a file ~/.vimtest as follows:
> > >
> > > cat > .vimtest
> > > set nocompatible
> > > set readonly
> > >
> > >
> > > and execute
On 6/18/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Yakov Lerner wrote:
> > On 5/23/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> > > create a file ~/.vimtest as follows:
> > >
> > > cat > .vimtest
> > > set nocompatible
> > > set readonly
> > >
> > >
> > > and execute (g)vim:
> > >
> > > v
Yakov Lerner wrote:
> > On 5/23/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> > > create a file ~/.vimtest as follows:
> > >
> > > cat > .vimtest
> > > set nocompatible
> > > set readonly
> > >
> > >
> > > and execute (g)vim:
> > >
> > > vim .vimtest -u .vimtest
> > >
> > > try :set readonly? a
On 5/24/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
On 5/24/06, Eric Arnold <[EMAIL PROTECTED]> wrote:
> I think 'readonly' does not belong in the .vimrc since it is a
> buffer-local-only option.
If you try to set any other buffer-local option in .vimrc,
you'll see that it works just fine.
I tr
On 5/24/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> -Original Message-
> From: Eric Arnold [mailto:[EMAIL PROTECTED]
> Sent: 24 May 2006 12:38
> To: Zdenek Sekera
> Cc: vim-dev@vim.org
> Subject: Re: set readonly - strange?
>
> I think 'readonly'
On 5/24/06, Eric Arnold <[EMAIL PROTECTED]> wrote:
I think 'readonly' does not belong in the .vimrc since it is a
buffer-local-only option.
If you try to set any other buffer-local option in .vimrc,
you'll see that it works just fine.
I tried 'set tw=22' in file opened as 'vim -u file file' an
> -Original Message-
> From: Eric Arnold [mailto:[EMAIL PROTECTED]
> Sent: 24 May 2006 12:38
> To: Zdenek Sekera
> Cc: vim-dev@vim.org
> Subject: Re: set readonly - strange?
>
> I think 'readonly' does not belong in the .vimrc since it is a
> buffer-l
-dev@vim.org
> Subject: Re: set readonly - strange?
>
> On 5/24/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> > > -Original Message-
> > > From: Eric Arnold [mailto:[EMAIL PROTECTED]
> > > Sent: 23 May 2006 18:12
> > > To: Yakov Lerner
> -Original Message-
> From: Eric Arnold [mailto:[EMAIL PROTECTED]
> Sent: 24 May 2006 11:21
> To: Zdenek Sekera
> Cc: Yakov Lerner; vim-dev@vim.org
> Subject: Re: set readonly - strange?
>
> On 5/24/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> > >
On 5/24/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> -Original Message-
> From: Eric Arnold [mailto:[EMAIL PROTECTED]
> Sent: 23 May 2006 18:12
> To: Yakov Lerner
> Cc: Zdenek Sekera; vim-dev@vim.org
> Subject: Re: set readonly - strange?
>
> As far as
> -Original Message-
> From: Eric Arnold [mailto:[EMAIL PROTECTED]
> Sent: 23 May 2006 18:12
> To: Yakov Lerner
> Cc: Zdenek Sekera; vim-dev@vim.org
> Subject: Re: set readonly - strange?
>
> As far as I can tell, there are several instances where there are
> t
As far as I can tell, there are several instances where there are
transitory buffers as vim is starting, opening a new tab, probably
some in closing op.s.
I don't know if I used the right word by saying the buffer is
"undefined", but I don't think it it's guaranteed to be usable until a
certain p
On 5/23/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> create a file ~/.vimtest as follows:
>
> cat > .vimtest
> set nocompatible
> set readonly
>
>
> and execute (g)vim:
>
> vim .vimtest -u .vimtest
>
> try :set readonly? and you'll get 'noreadonly'.
The buffer does exist when initfile is exec
I wouldn't expect that to work. There is no defined loaded buffer
when the -u vimrc is run. 'readonly' is local to buffers only, so in
your example, it has no buffer to be applied to.
If you want everything to be readonly, try setting a BufEnter autocommand.
If you want just one file to be rea
18 matches
Mail list logo
