Is it on the to-do list to make diffoff restore from previous values rather
than default ones, or is there already an option somewhere that toggles the
behaviour?
AFAIK you have to save the options before starting diff mode and
restore them later. At least, that is the answer to the
On Thu, Oct 12, 2006 at 10:50:31PM +0200, A.J.Mechelynck wrote:
(i.e., 3 nonempty lines and one empty line). You may add more headers,
and/or fill them in. Then your body text will be after the first
empty line, and it will not be regaded as headers.
Interesting. The subject is checked for
Dnia piątek, 13 października 2006 02:16, David Fishburn napisał:
Instead of simply grouping everything under variables, should we
distinguish between different types?
let forms#form = {
\ 'title': 'Address Entry Form',
\ 'fields': [],
\ 'defaultbutton': 'ok',
\
On Fri, Oct 13, 2006 at 10:47:33AM +0100, Vigil wrote:
Is it on the to-do list to make diffoff restore from previous values
rather
than default ones, or is there already an option somewhere that toggles
the
behaviour?
AFAIK you have to save the options before starting diff mode and
Anthony Campbell wrote:
On 12 Oct 2006, A.J.Mechelynck wrote:
Tom Purl wrote:
[...]
That's weird. I use Gvim to edit web mail via the Mozex extension. I
can place this is a tset at line one in my message after executing the
`set filetype=mail` command, and it will be spell-checked. I don't
Anthony Campbell wrote:
I know, I have subscribed, but my posts never appear. (This is not new;
it's been like that for many months.) I've tried unsubscribing and
resubscribing, but no luck.
Did you receive the confirmation email which was sent to you as an
auto-reply when you sent a mail
:hi
I did the following mappings:
map F12 ESC:tab e ~/.vimrcCRC-W_
map S-F12 ESC:tab e ~/.zshrcCRC-W_
I start vim without any argument and press
F12
. ${HOME}/.vimrc opens but does not create an entry in the tab pages
line at the top of my Vim window -- so far so
Hari Krishna Dara wrote:
I faced a problem, though it is with netrw, not with vim syntax file. I
tried to open the download link from Vim, and got the below error:
Error detected while processing function netrw#NetRead:
line 275:
http://mysite.verizon.net/astronaut/vim/syntax/vim.vim.gz;
Anthony Campbell wrote:
On 13 Oct 2006, A.J.Mechelynck wrote:
Anthony Campbell wrote:
On 13 Oct 2006, A.J.Mechelynck wrote:
Anthony Campbell wrote:
I'm sorry; I can't post to the list, although I can read it. (Feel free
to forward it.)
Just to say that I don't get spelling checked with html
-Original Message-
From: Peter Hodge [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 12, 2006 11:24 PM
To: David Fishburn; vim@vim.org
Subject: Re: VimL and Exuberant tags - Suggestions please
Hello David,
Can I suggest support for these commands:
Meino Christian Cramer wrote:
:hi
I did the following mappings:
map F12 ESC:tab e ~/.vimrcCRC-W_
map S-F12 ESC:tab e ~/.zshrcCRC-W_
I start vim without any argument and press
F12
. ${HOME}/.vimrc opens but does not create an entry in the tab pages
line at the
hdrtag (available at http://mysite.verizon.net/astronaut/src) creates
tags for *.vim files.
Currently, it supports tags for syntax, match, region, c luster,
keyword, function, command, and maps.
Regards,
Chip Campbell
On Fri, 13 Oct 2006 at 11:43am, David Fishburn wrote:
-Original Message-
From: Peter Hodge [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 12, 2006 11:24 PM
To: David Fishburn; vim@vim.org
Subject: Re: VimL and Exuberant tags - Suggestions please
Hello David,
Can I
Am Freitag, 13. Oktober 2006 17:22 schrieben Sie:
function mydict.len() dict
let var_in_func = 2
let s:script_var_in_func = 2
return len(self.data)
endfunction
This syntax is only suitable for what is called an Meta-Class or a
Singelton-Pattern. It is not suitable for real OO
Netrw comes with a few supported formats, and the format is deduced by
the extension of the file, which is fair, but is there anyway to
configure netrw such that it will recognize new extensions as one of the
supported filetypes? E.g., there are several archives that are
compatible/same as zip
When you use ins-completion, Vim starts scanning all the buffers for
matches, and this results in several messages, one for each of the
buffer. I am wondering if these need to go into the :messages list. If
you have several buffers loaded, one completion could potentially take
all the existing
Hari Krishna Dara wrote:
Netrw comes with a few supported formats, and the format is deduced by
the extension of the file, which is fair, but is there anyway to
configure netrw such that it will recognize new extensions as one of the
supported filetypes? E.g., there are several archives that
Hari Krishna Dara wrote:
Netrw comes with a few supported formats, and the format is deduced by
the extension of the file, which is fair, but is there anyway to
configure netrw such that it will recognize new extensions as one of the
supported filetypes? E.g., there are several archives that
Hari Krishna Dara wrote:
When you use ins-completion, Vim starts scanning all the buffers for
matches, and this results in several messages, one for each of the
buffer. I am wondering if these need to go into the :messages list. If
you have several buffers loaded, one completion could
On Fri, 13 Oct 2006 at 3:16pm, Charles E Campbell Jr wrote:
Hari Krishna Dara wrote:
Netrw comes with a few supported formats, and the format is deduced by
the extension of the file, which is fair, but is there anyway to
configure netrw such that it will recognize new extensions as one of
In the below code, I find that the curly-brace for the method is indented
incorrectly. The first line in the method is also indented incorrectly.
I verified this with gvim starting with -u NONE option and with
:filetype on and :filetype indent on.
public class A
{
public static void
Am Freitag, 13. Oktober 2006 02:16 schrieb David Fishburn:
I have taken over maintenance of the VimL exuberant tags component.
Just VimL or the hole of ctags? The ctags Patch list list [1] not been worked
on for ages. Parsers for Ada, Ruby, PHP, Haskel are Open and waiting for
integration for
On 10/13/06, Martin Krischik [EMAIL PROTECTED] wrote:
The ctags Patch list list [1] not been worked on for ages.
I wonder why no one has taken over development/forked this project
yet. It seems obvious that the current maintainer has given up
interest.
nikolai
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nikolai Weibull
Sent: Friday, October 13, 2006 2:48 PM
To: Martin Krischik
Cc: vim-dev; vim@vim.org
Subject: Re: VimL and Exuberant tags - Suggestions please
On 10/13/06, Nikolai Weibull [EMAIL
Hi Benji,
On 10/12/06, Benji Fisher [EMAIL PROTECTED] wrote:
On Sat, Oct 07, 2006 at 12:37:33AM +0800, Yongwei Wu wrote:
This is a report of what I have already achieved. If you are dealing
with more encodings than the fileencodings option can handle, esp. if
you read and write Simplified
In another thread, Yakov Lerner wrote:
4) You can use tip http://www.vim.org/tips/tip.php?tip_id=1285
to remap :w to :up :
cabbrev w c-R=(getcmdtype()==':' getcmdpos()==1 ? 'up' : 'w')cr
Why cabbrev rather than cmap?
--Suresh
Yongwei Wu wrote:
Hi Benji,
On 10/12/06, Benji Fisher [EMAIL PROTECTED] wrote:
On Sat, Oct 07, 2006 at 12:37:33AM +0800, Yongwei Wu wrote:
This is a report of what I have already achieved. If you are dealing
with more encodings than the fileencodings option can handle, esp. if
you read and
Suresh Govindachar wrote:
In another thread, Yakov Lerner wrote:
4) You can use tip http://www.vim.org/tips/tip.php?tip_id=1285
to remap :w to :up :
cabbrev w c-R=(getcmdtype()==':' getcmdpos()==1 ? 'up' : 'w')cr
Why cabbrev rather than cmap?
--Suresh
For one thing, a cabbrev will
Hi all,
I have developed a generic Vim tree control (non-GUI) plugin. This
control can be used by other Vim plugins to display information in
a tree control. The tree control is similar to the one used by
the taglist plugin. The tree control will work only in Vim version 7.0
and above.
The tree
Hi,
Would it be possible to make Vim overwrite a backup file only if
the buffer was actually modified? Look at the following scenario:
1. I edit file foobar.txt, make some change and save it.
- the backup file foobar.txt~ is created
2. I edit again foobar.txt, but this time I don't make any
On 10/13/06, David Schweikert [EMAIL PROTECTED] wrote:
Would it be possible to make Vim overwrite a backup file only if
the buffer was actually modified? Look at the following scenario:
1. I edit file foobar.txt, make some change and save it.
- the backup file foobar.txt~ is created
2. I
While replying to a post on the vim users' list, I noticed a slight
problem. The diff commands set some options, but this is not reported
with verbose set. For example
:e foo.txt
:set fdm=marker
:diffsplit bar.txt
:wincmd wback to foo.txt
:verbose set fdm?
foldmethod=diff
:only
Benji Fisher wrote:
While replying to a post on the vim users' list, I noticed a slight
problem. The diff commands set some options, but this is not reported
with verbose set. For example
:e foo.txt
:set fdm=marker
:diffsplit bar.txt
:wincmd wback to foo.txt
:verbose set fdm?
-Original Message-
From: David Fishburn [mailto:[EMAIL PROTECTED]
Sent: 13 October 2006 02:16
To: vim@vim.org
Subject: VimL and Exuberant tags - Suggestions please
I have taken over maintenance of the VimL exuberant tags component.
That's excellent news, thanks for doing it,
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Benji Fisher wrote:
While replying to a post on the vim users' list, I noticed a slight
problem. The diff commands set some options, but this is not reported
with verbose set. For example
:e foo.txt
:set fdm=marker
:diffsplit
Yakov Lerner wrote:
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Benji Fisher wrote:
While replying to a post on the vim users' list, I noticed a
slight
problem. The diff commands set some options, but this is not reported
with verbose set. For example
:e foo.txt
:set
Hi,
I got a report on the Cygwin mailing list that the following message
appears when trying to open /etc/hosts in vim:
E303: Unable to open swap file for /etc/hosts, recovery impossible
What happens is this:
/etc/hosts is by default a symbolic link which points to the hosts file
in the
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Benji Fisher wrote:
While replying to a post on the vim users' list, I noticed a
slight
problem. The diff commands set some options, but this is not reported
On Oct 13 21:16, Bram Moolenaar wrote:
Corinna Vinschen wrote:
I got a report on the Cygwin mailing list that the following message
appears when trying to open /etc/hosts in vim:
E303: Unable to open swap file for /etc/hosts, recovery impossible
What happens is this:
On Oct 13 21:33, Corinna Vinschen wrote:
On Oct 13 21:16, Bram Moolenaar wrote:
Corinna Vinschen wrote:
[...]
Below is a patch which works for me, though I'm not sure if it's
complete enough to catch all cases. There's code for OS2 in os_unix.c
which I reused, plus a new definition
On 10/13/06, Corinna Vinschen [EMAIL PROTECTED] wrote:
Hi,
I got a report on the Cygwin mailing list that the following message
appears when trying to open /etc/hosts in vim:
E303: Unable to open swap file for /etc/hosts, recovery impossible
What happens is this:
/etc/hosts is by default a
Corinna Vinschen wrote:
On Oct 13 21:33, Corinna Vinschen wrote:
On Oct 13 21:16, Bram Moolenaar wrote:
Corinna Vinschen wrote:
[...]
Below is a patch which works for me, though I'm not sure if it's
complete enough to catch all cases. There's code for OS2 in os_unix.c
which I reused, plus a
On Oct 13 21:53, Yakov Lerner wrote:
On 10/13/06, Corinna Vinschen [EMAIL PROTECTED] wrote:
Hi,
I got a report on the Cygwin mailing list that the following message
appears when trying to open /etc/hosts in vim:
E303: Unable to open swap file for /etc/hosts, recovery impossible
What
Yakov Lerner wrote:
[...]
I mean, I tried 'ls c:\windows' in cygwin and it does not work ..
strange is it issue of version of cygwin ? I saw even
weirder differences in cygwin behaviour ... fat32 vs ntfs differences...
Maybe this is because \ have a special meaning for bash or some
On Fri, Oct 13, 2006 at 09:38:16PM +0200, Corinna Vinschen wrote:
Interesting enough it works in 6.4 without doing anything similar to my
patch does to os_unix.c. What's different in swap file handling between
6.4 and 7.0 so that it works in the former but doesn;t in the latter?
memline.c was
On Oct 13 22:02, A.J.Mechelynck wrote:
Corinna Vinschen wrote:
Interesting enough it works in 6.4 without doing anything similar to my
patch does to os_unix.c. What's different in swap file handling between
6.4 and 7.0 so that it works in the former but doesn;t in the latter?
Is your 6.4
On Oct 13 16:06, James Vega wrote:
On Fri, Oct 13, 2006 at 09:38:16PM +0200, Corinna Vinschen wrote:
Interesting enough it works in 6.4 without doing anything similar to my
patch does to os_unix.c. What's different in swap file handling between
6.4 and 7.0 so that it works in the former
On 2006-10-13, Corinna Vinschen [EMAIL PROTECTED] wrote:
On Oct 13 21:53, Yakov Lerner wrote:
On 10/13/06, Corinna Vinschen [EMAIL PROTECTED] wrote:
Hi,
I got a report on the Cygwin mailing list that the following message
appears when trying to open /etc/hosts in vim:
E303:
On Fri, Oct 13, 2006 at 10:34:40PM +0200, Corinna Vinschen wrote:
On Oct 13 16:06, James Vega wrote:
On Fri, Oct 13, 2006 at 09:38:16PM +0200, Corinna Vinschen wrote:
Interesting enough it works in 6.4 without doing anything similar to my
patch does to os_unix.c. What's different in swap
Am Freitag, 13. Oktober 2006 02:16 schrieb David Fishburn:
I have taken over maintenance of the VimL exuberant tags component.
Just VimL or the hole of ctags? The ctags Patch list list [1] not been worked
on for ages. Parsers for Ada, Ruby, PHP, Haskel are Open and waiting for
integration for
On 10/13/06, Martin Krischik [EMAIL PROTECTED] wrote:
The ctags Patch list list [1] not been worked on for ages.
I wonder why no one has taken over development/forked this project
yet. It seems obvious that the current maintainer has given up
interest.
nikolai
On 10/13/06, Nikolai Weibull [EMAIL PROTECTED] wrote:
On 10/13/06, Martin Krischik [EMAIL PROTECTED] wrote:
The ctags Patch list list [1] not been worked on for ages.
I wonder why no one has taken over development/forked this project
yet. It seems obvious that the current maintainer has
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nikolai Weibull
Sent: Friday, October 13, 2006 2:48 PM
To: Martin Krischik
Cc: vim-dev; vim@vim.org
Subject: Re: VimL and Exuberant tags - Suggestions please
On 10/13/06, Nikolai Weibull [EMAIL
53 matches
Mail list logo