Hi
Vim 7.2, gtk2, Linux x86_64, I get no crashes, just the register not
showing if the size is 262,034 or more. At 512 MB there was a long
delay before nothing showed, and 1 GB rendered the whole system
unusable, thrashing badly, and after 5 minutes I hit the reset button.
Regards, John
--~--~-
On Fri, Aug 22, 2008 at 3:32 AM, Matt Wozniski wrote:
> Not sure what's going on here, but I've found a crash that's easy to
> reproduce. First, open two X11 enabled vim (not gvim) processes. In
> the first, do:
> :let @+ = repeat('a', 1024*1024)
> in order to store 1MB of data to the clipboard
On 22/08/08 03:13, Bram Moolenaar wrote:
>
> Marvin Renich wrote:
[...]
>> I would have expected :helptags to use the current value of 'fencs',
>> which, if encoding=utf-8, defaults to ucs-bom,utf-8,default,latin1,
>> which should favor utf-8 over latin1.
>
> No, because the help files encoding do
Peter Prohaska wrote:
> :help right-justify
> """There is no command in Vim to right justify text. [...]"""
"Justify" means to insert variable-width spacing throught the entire line so the
left and right margins are aligned. That's how most books and newspaper articles
appear.
"Right-align" mean
Hi,
the docs tell me that...
:help right-justify
"""There is no command in Vim to right justify text. [...]"""
:help :right
"""Right-align lines in [...]"""
Doesn't that mean, that at least 'gq' followd by ':right' would "right-
justify"
whatever text object?
Not sure if i'm missing some subtle
On 22/08/08 03:13, Bram Moolenaar wrote:
[...]
> Looks like this is a leftover from when ther was a "Find" toolbar item.
> I'll remove "tmenu ToolBar.Find".
>
Rather than that, I've added a Find toolbar item (duplicating the
Edit=>Find... menu the way Toolbar=>Replace duplicates Edit=>Find and
R
On Fri, Aug 15, 2008 at 2:02 AM, Matt Wozniski wrote:
> synIDattr() currently does not support the ability to read a 'guisp'
> attribute from a highlight group, even though the underlying C
> function it exposes does support it. I've attached a patch to update
> the interface and docs to allow an
Not sure what's going on here, but I've found a crash that's easy to
reproduce. First, open two X11 enabled vim (not gvim) processes. In
the first, do:
:let @+ = repeat('a', 1024*1024)
in order to store 1MB of data to the clipboard. The exact amount is
irrelevant, but the larger the size, the m
Tony Mechelynck wrote:
> In $VIMRUNTIME/menu.vim (dated 2008 Jun 30) a tooltip is defined for a
> ToolBar.Find menu which does not exist:
>
> lines 981-988
> > if !has("gui_athena")
> > an 1.95 ToolBar.-sep3-
> > an 1.100 ToolBar.Replace :promptrepl
>
Marvin Renich wrote:
> * Bram Moolenaar <[EMAIL PROTECTED]> [080821 00:55]:
> >
> > Tony Mechelynck wrote:
> >
> > > >> E670: Mix of help file encodings within a language:
> > > >> /usr/local/share/vim/vimfiles/doc/hicolors.txt
> > > >>
> > > >> The error is given by the :helptags command.
> >
On 2008-08-22, bjrn <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This may not be the right place for this post, but it seems like I've
> come across a bug so I am posting here.
>
> If I type
>
> :args file1.m file1.h file2.m
>
> then I expect the arglist to have the file appear in the order I
> specif
Hi,
This may not be the right place for this post, but it seems like I've
come across a bug so I am posting here.
If I type
:args file1.m file1.h file2.m
then I expect the arglist to have the file appear in the order I
specified, but instead the arglist is in this order:
file1.m file2.m file1
In $VIMRUNTIME/menu.vim (dated 2008 Jun 30) a tooltip is defined for a
ToolBar.Find menu which does not exist:
lines 981-988
> if !has("gui_athena")
> an 1.95 ToolBar.-sep3-
> an 1.100 ToolBar.Replace :promptrepl
> vunmenu ToolBar.Replace
> vnoremenu Tool
On 20/08/08 16:16, Robert Webb wrote:
> Hi,
>
> What's the best way (on Windows) to open a file from vim in whatever
> Windows normally uses to open that file? For example, :!% will open
> the current file, but it leaves a DOS window handing around while the
> file is open, which requires a hit-e
On 21/08/08 14:42, Marvin Renich wrote:
[...]
> I would have expected :helptags to use the current value of 'fencs',
> which, if encoding=utf-8, defaults to ucs-bom,utf-8,default,latin1,
> which should favor utf-8 over latin1.
>
> Tony, what was fencs when you ran helptags?
just what you said abo
On 21/08/08 06:55, Bram Moolenaar wrote:
> Tony Mechelynck wrote:
[...]
>> But, is UTF-8 with BOM different from UTF-8 without BOM? And how does
>> ":helptags" detect the encoding used by a file?
>
> Right, that should work. But ASCII is not utf-8, and I think (without
> looking at the code) that
On 21/08/08 08:25, Matt Wozniski wrote:
[...]
> In that vein, perhaps using the shell should be an option... but
> doubtless the best default behavior is to use system(3) for places
> like :! where shell expansion is good,and execlp() for those places
> where we decidedly don't want any shell expa
On Thu, Aug 21, 2008 at 1:05 PM, Tony Mechelynck wrote:
>
> On 21/08/08 08:25, Matt Wozniski wrote:
> [...]
>> In that vein, perhaps using the shell should be an option... but
>> doubtless the best default behavior is to use system(3) for places
>> like :! where shell expansion is good,and execlp(
On 20/08/08 13:09, Matt Wozniski wrote:
> On Wed, Aug 20, 2008 at 4:33 AM, Tony Mechelynck wrote:
>> On 20/08/08 09:47, Jan Minář wrote:
>>> The above will of course not work. The following will:
>>>
>>> /* We use an obscure glibc function -- check out the man page! */
>>> clockface =
On 21-Aug-08 16:15, Robert Webb wrote:
> Ag. D. Hatzimanikas:
>
>>> I could also use readfile(), which would probably suffice, but is this
>>> more or less efficient than loading a file into a vim buffer. I will
>>> still need to read the whole file either way since I don't know how
>>> far thro
Ag. D. Hatzimanikas:
> > I could also use readfile(), which would probably suffice, but is this
> > more or less efficient than loading a file into a vim buffer. I will
> > still need to read the whole file either way since I don't know how
> > far through the file I will need to look.
> >
> >
Ingo Karkat wrote:
> > What's the best way (on Windows) to open a file from vim in whatever
> > Windows normally uses to open that file? For example, :!% will open
> > the current file, but it leaves a DOS window handing around while the
> > file is open, which requires a hit-enter to get rid of
* Bram Moolenaar <[EMAIL PROTECTED]> [080821 00:55]:
>
> Tony Mechelynck wrote:
>
> > >> E670: Mix of help file encodings within a language:
> > >> /usr/local/share/vim/vimfiles/doc/hicolors.txt
> > >>
> > >> The error is given by the :helptags command.
> > >>
> > >> Bug or feature?
> > >> 1. Wh
Hi Bram,
While skimming through the various vim readme's, I noticed some mismatched
references to various vim versions.
Thanks
From 860f3b562da22f15f53c8a848dd50cfa49370236 Mon Sep 17 00:00:00 2001
From: Michael Wookey <[EMAIL PROTECTED]>
Date: Thu, 21 Aug 2008 20:28:03 +1000
Subject: [PATCH] Min
24 matches
Mail list logo
