On Wed, Jul 2, 2008 at 22:57, Amy Williams [EMAIL PROTECTED] wrote:
Gvim appears to have very slow scrolling for output from external commands.
This is an issue for me, particularly with :make and with spell checking.
To see the issue, run gvim, type a word, and then with the cursor over that
Omega Speedmaster Reduced Black Chronograph Mens Watch 3539.50, Best
Luxury Replica Watches (www.wholesale-watches.org)
Omega Speedmaster Reduced Black Chronograph Mens Watch 3539.50 Link :
http://www.wholesale-watches.org/wristwatch-3383.html
To Buy the cheapest Omega Speedmaster Reduced
On Tue, Jul 1, 2008 at 7:34 PM, Marc Haisenko [EMAIL PROTECTED] wrote:
As you can see, the UNIX way of handling output is severely broken and
always
has been because there's just no way that the terminal can tell the system
and/or application what it CAN support.
Wrong.
Vt* terminals,
Hello,
First of all, your patch for mbyte.c is totally different for this
thread. You could send it with different bug report.
It seems your patch for mbyte.c is fine to me though I test it not
much.
Added comment below is only for CursorIM problem.
mattn wrote:
On Thu, Jul 3, 2008 at 1:24
-Original Message-
From: vim_dev@googlegroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Christian MICHON
Sent: Wednesday, July 02, 2008 2:31 AM
To: vim_dev@googlegroups.com; vim-dev; Bram Moolenaar
Subject: A git from scratch repository of vim since vim-6.0
Hi Bram,
On Thu, Jul 3, 2008 at 10:34 AM, Yakov Lerner [EMAIL PROTECTED] wrote:
On Tue, Jul 1, 2008 at 7:34 PM, Marc Haisenko [EMAIL PROTECTED]
wrote:
As you can see, the UNIX way of handling output is severely broken and
always
has been because there's just no way that the terminal can tell the
Hi,
hangulin module only works with euc-kr.
If you want to use UTF-8, you are left with no choice but using XIM.
regards.
shawn.
2008. 06. 19, 오후 7:01, Kiwon Um 작성:
Hello there.
Because of some problems with XIM, I checked the hangulinput option.
But it doesn't seem to work well with
On Thu, Jul 3, 2008 at 13:12, Henrik Öhman [EMAIL PROTECTED] wrote:
The commit messages seem to be slightly broken in that they have hard line
breaks and indentation in text. It could perhaps be solved by removing any
line breaks except where the next word is Problem:, Solution: or
Files:,
On 03/07/08 15:20, Ben Fritz wrote:
Is there any particular reason that the 'revins' option only works in
insert mode, and not replace mode as well?
I would certainly find the option more useful if it did, but it isn't
really a big deal if it remains as-is.
Normally you shouldn't use it
Hi.
The updated gzip.vim looks all-right; just one rather subtle thing:
In case we're editing a file with a file name that starts with a dash,
the invocation of the compress program should use a double-dash to
signal the end of optional arguments.
Patch is attached.
Following my recent advisory on Vim vulnerabilities, here goes a followup: many
more vulnerabile statements in Netrw. Although Netrw has been updated with
the new fnameescape() and shellescape() functions, it doesn't use them
consistently. It is difficult *not* to find vulnerable code in Netrw.
Christian MICHON, 02.07.2008:
it took a while, but it's finally available...
That's great!
Keep in mind that:
- this is not upstream of course
With the only difference that it's inofficial, right?
- each release has its own branch (master=7.1)
- this will not include the betas, only
12 matches
Mail list logo
