Hi Bram,
Updated patch attached.
Thanks in advance.
Kind regards,
James.
On 18 March 2011 13:18, Bram Moolenaar b...@moolenaar.net wrote:
James Hunt wrote:
Hi Thedward,
Thanks for the suggestion! Updated patch attached.
I actually don't like changing 'iskeyword' in a syntax file, it
Hi Bram,
Hopefully the final update based on Thilos comment and also added in
support for recognizing user jobs in filetype.vim.
Kind regards,
James
On 18 March 2011 13:18, Bram Moolenaar b...@moolenaar.net wrote:
James Hunt wrote:
Hi Thedward,
Thanks for the suggestion! Updated patch
Hi all,
Here is what to do (tried on windows only):
1. gvim.exe -u NONE -U NONE -N
2. i(oge)esc
3. :se iscr
4. /(oge)^f
5. Now just go up/down, left/right and there will be weird highlightings
everywhere
Version: 7.3, 1-138
PS: Sorry if this has already been reported
Dimitar Dimitrov
On 21/03/2011 00:57, Gary Johnson wrote:
On 2011-03-21, Andy Wokula wrote:
Am 18.03.2011 15:33, schrieb Mike Williams:
The Win32 file search functions search both the long and short versions of
file names. When the short version of a file name is created any extension
is limited to 3
Ah, confirmed. I can now reproduce it too on Linux
with Vim-7.3.138 in the terminal as well as with gvim (gtk2) with:
$ vim -u NONE -c 'set lazyredraw'
... then typing :verCR does not show anything.
I just came here to say the same thing. :messages and probably other
commands are also
backspace -- backslash
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
# HG changeset patch
# Parent ea399ac2c1b963b068beed88bfaff7620d345333
diff --git
Hi,
We are facing a severe problem on using :g on our machines at work. On
two different dell machines this command causes problems after
updating to x64 Windows 7 or Windows Server 2008.
The scenario is as follows:
* Logfile ~100Mb opened
* execute :%g!/xxx/d to remove some lines
* PC is
Hi Philipp,
if you are just trying of eliminate stuff, but then you don't
need to really undo your changes, since you will not save
back the files at the end, I suggest you:
:set ul=-1
This should speed up things a lot.
Please, let me know if it solves your problem
All the best, Antonio
On
On Mar 21, 5:48 am, pmehrwald phil_mehrw...@yahoo.com wrote:
Hi,
We are facing a severe problem on using :g on our machines at work. On
two different dell machines this command causes problems after
updating to x64 Windows 7 or Windows Server 2008.
The scenario is as follows:
* Logfile
On Mon, Mar 21, 2011 at 13:48, pmehrwald phil_mehrw...@yahoo.com wrote:
Hi,
We are facing a severe problem on using :g on our machines at work. On
two different dell machines this command causes problems after
updating to x64 Windows 7 or Windows Server 2008.
The scenario is as follows:
*
On Fri, 2011-03-18 at 18:35 -0400, James Vega wrote:
The default vimrc is no vimrc.
...except on Windows...
There's an example vimrc that the installer installs to $VIM (which
one can change through the Advanced install options).
Part of the confusion, IMO, is that, on Windows, Vim treats
On Fri, 2011-03-18 at 10:46 -0700, Ben Fritz wrote:
On Mar 18, 12:35 pm, Ben Fritz fritzophre...@gmail.com wrote:
http://vim.wikia.com/wiki/Running_diff#Vim_distribution_from_Cream
It looks like some changes have been made since the wiki article
was written, I'm not sure if issues
On Mon, Mar 21, 2011 at 08:24:05PM -0400, Steve Hall wrote:
On Fri, 2011-03-18 at 18:35 -0400, James Vega wrote:
The default vimrc is no vimrc.
...except on Windows...
That's an implementation detail of the installer which can be disabled
by the user. There's no requirement for there to
13 matches
Mail list logo
