Thanks, reporting vim.org problems here is good, or direct to
Bram, or direct to me and I will arrange with Bram.
Speaking of the site, does it also make sense to remove tip search in Search
for Vim Tips section? Probably a link to the wiki would be enough.
--
You received this message
On Mon, Nov 19, 2012, at 0:28, Ben Fritz wrote:
On Sunday, November 18, 2012 4:23:29 PM UTC-6, Nick Gravgaard wrote:
I am aware that elastic tabstops is not something many people use
(yet). Still, for me it is a very nice feature to use with a gedit
plugin, but since my favourite
On Monday, November 19, 2012 7:43:32 AM UTC-6, Nick Gravgaard wrote:
But maybe there could be 2 new features that could combine together to
create the ability to do things like elastic tabstops or tables in the
middle of text nicely, without backwards-incompatible changes and keeping
On Sun, 18 Nov 2012 16:28:19 -0800 (PST), Ben Fritz
fritzophre...@gmail.com wrote:
1. Implement variable-width tabstops by allowing a comma-separated list to be
used as a value for 'tabstop'. For example, setting ts=4,2,8 would have the
first tab in the line stop at column 4, the next stop
On Mon, November 19, 2012 17:21, Matthew Winn wrote:
On Sun, 18 Nov 2012 16:28:19 -0800 (PST), Ben Fritz
fritzophre...@gmail.com wrote:
1. Implement variable-width tabstops by allowing a comma-separated list
to be used as a value for 'tabstop'. For example, setting ts=4,2,8 would
have the
Hi,
Attached is an update for MzScheme interface. It features:
* Improved interaction with garbage collector in newer versions of
Racket: leaving SIGSEGV to GC, references to buffer/windows are now
truly uncollectable.
* Simplified and cleaned up macros: now Vim uses the latest API and
On 19 November 2012 18:02, Christian Brabandt cbli...@256bit.org wrote:
On Mon, November 19, 2012 17:21, Matthew Winn wrote:
I implemented a patch to do this a few years ago, when I was out of
work and decided to grab something off the TODO list to keep me busy.
(It's since been taken over by
Hello!
I've attached a patch which allows subdirectories with help. Actually,
the tags system already permitted subdirectories; what this patch does
is extend helptags to search through subdirectories, creating
appropriate tags.
The patch is experimental, and I've only tested it under Linux
Bram, it came up on vim_use (
https://groups.google.com/d/topic/vim_use/XnKfkjc9bSY/discussion ) that the
mail.vim filetype plugin does not currently set the 'comments' option.
I think you should add:
setl comments+=n:
to the mail.vim ftplugin you maintain in case the user or another ftplugin
Hi Ben!
On Mo, 19 Nov 2012, Ben Fritz wrote:
Bram, it came up on vim_use (
https://groups.google.com/d/topic/vim_use/XnKfkjc9bSY/discussion ) that the
mail.vim filetype plugin does not currently set the 'comments' option.
I think you should add:
setl comments+=n:
to the mail.vim
Hi Lech!
On Mo, 19 Nov 2012, Lech Lorens wrote:
On 19 November 2012 18:02, Christian Brabandt cbli...@256bit.org wrote:
On Mon, November 19, 2012 17:21, Matthew Winn wrote:
I implemented a patch to do this a few years ago, when I was out of
work and decided to grab something off the TODO
On 19 November 2012 19:50, Christian Brabandt cbli...@256bit.org wrote:
Hi Lech!
On Mo, 19 Nov 2012, Lech Lorens wrote:
It might be me that Matt is referring to as a person that took over
maintaining the feature. In fact I only updated the patch to be
applicable to the source code of Vim as
John Beckett wrote:
So8res wrote:
On the vim patches page [1] the link to vim_dev mailinglist
patches [2] is broken.
More generally, where should such website bugs be reported
and how are they fixed?
[1] http://www.vim.org/patches.php
[2]
The substitute() function already can take the 'g' flag which causes the
substitution to be global. There's no way to force the search to be case
(in)sensitive, though. This means that plugins must either save restore
ignorecase before using substitute() or be OK with the case sensitivity of
Hi So8res!
On Mo, 19 Nov 2012, So8res wrote:
The substitute() function already can take the 'g' flag which causes
the substitution to be global. There's no way to force the search to
be case (in)sensitive, though. This means that plugins must either
save restore ignorecase before using
I think functions with [range] should preserve the cursor line. Assume you have:
function RangeTest() range
echo line('.')
endfunction
And you put the cursor on line 2 and :%call RangeTest()
This function will echo 1, because the cursor is moved to the beginning of the
range *before*
Bram Moolenaar wrote:
Bram: Do you want me to remove the Other Vim patches
section from [1] (and email you when done)? I don't think the
list was established elsewhere, so it needs to be removed?
I thought we copied the patches to somewhere...
If we don't have this list somewhere I think we
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 94 by shlo...@gmail.com: Better support is needed for DocBook 5
in filetype.vim and filetype/docbk.vim
http://code.google.com/p/vim/issues/detail?id=94
What steps will reproduce the problem?
1. Try opening a DocBook/XML 5
Am 19.11.2012 22:52, schrieb So8res:
I think functions with [range] should preserve the cursor line.
Don't break scripts that count on this.
Assume you have:
function RangeTest() range
echo line('.')
endfunction
And you put the cursor on line 2 and :%call RangeTest()
This function will
On Mon, Nov 19, 2012, at 16:21, Matthew Winn wrote:
On Sun, 18 Nov 2012 16:28:19 -0800 (PST), Ben Fritz
fritzophre...@gmail.com wrote:
1. Implement variable-width tabstops by allowing a comma-separated list to
be used as a value for 'tabstop'. For example, setting ts=4,2,8 would have
Am 19.11.2012 22:52, schrieb So8res:
I think functions with [range] should preserve the cursor line. Assume
you have:
function RangeTest() range
echo line('.')
endfunction
And you put the cursor on line 2 and :%call RangeTest()
This function will echo 1, because the cursor is moved to the
That's a nifty command and mapping, but I had no trouble with getting a
custom command to use the range correctly. (You can just use -range, pass
line1 and line2 to the function, and have the function do winsaveview()
and winrestview(), which is what I do now.)
Then you can also default to the
Am 20.11.2012 01:29, schrieb Nate Soares:
That's a nifty command and mapping, but I had no trouble with getting a
custom command to use the range correctly. (You can just use -range, pass
line1 and line2 to the function, and have the function do winsaveview()
and winrestview(), which is what I
On Mon, November 19, 2012 22:52, So8res wrote:
I think functions with [range] should preserve the cursor line. Assume you
have:
function RangeTest() range
echo line('.')
endfunction
And you put the cursor on line 2 and :%call RangeTest()
This function will echo 1, because the cursor is
24 matches
Mail list logo
