* marc chantreux wrote:
> jamessan@... wrote:
> > You can get vim7 pacakges by adding the following line to your
> > sources.list:
> >
> > deb http://people.debian.org/~nobse/vim7 ./
>
> sorry, but i failed to use this source :
>
> deb http://people.debian.org/~nobse/vim7 ./
> added to /etc/apt/sources.list
>
> apt-get update && apt-get upgrade
>
> i've tried pinning : people.debian.org has 999 now
>
> but i'm unable to update to vim7 :(

What's the result of 'apt-cache policy vim'?

Norbert

>>i've tried pinning : people.debian.org has 999 now
>>but i'm unable to update to vim7 :(
> What's the result of 'apt-cache policy vim'?

well ... shame on me : there was a syntax error in my apt/preferences

works fine now. thanks !

regards

mc

Hi,

I'm trying to use Intellisense for VIM.
(http://www.vim.org/scripts/script.php?script_id=747)

I 've done all what is set in the intellisense.txt.

One thing that I did different was to set the $VIM_INTELLISNESE as described.
I did take a look at the intellisense.vim file and added it that way in my
_vimrc

I have the following in my _vimrc file:
[start of _vimrc]
set nocompatible
source $VIMRUNTIME/vimrc_example.vim
source $VIMRUNTIME/mswin.vim
behave mswin
let g:intellisense_root_dir=expand('$VIM/Intellisense')

[... personal mappings...]

{end of _vimrc]

I have removed all other plugins to exclude the change that they could vim
scripts interferring.


When I press <C-Space-a> it does select everything (like CTRL-A in windows), iso
showing the pop-up windows
When I press <C-Space-f> it does nothing.

Any help is a appreciated.

Best rgds,

Eric Leenman


Disclaimer:
De informatie verzonden met deze e-mail is uitsluitend bestemd voor de
geadresseerde. Gebruik van deze informatie door anderen dan de geadresseerde is
verboden. Greefa accepteert, mede gezien het onveilige karakter van berichten
via internet, geen enkele juridische aansprakelijkheid voor de inhoud van dit
bericht.
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
entity to whom it is addressed and others authorized to receive it. Use of this
information , in whatever way, by others is strictly prohibited and may be
unlawful. Greefa does not accept legal responsibility for this e-mail message
due to the insecure nature of internet communications.

YankRing.vim : Maintains a history of previous yanks and deletes
http://www.vim.org/scripts/script.php?script_id=1234

description
Vim already maintains a list of numbered registers containing the last 9
deletes.  These previous deletes can be referenced using [register]p, so "1p
will paste the last delete, "2p the 2nd last delete.  For more information
see |quote_number|.

Vim does not provide any mechanism to reference previous yanked text.  In
Emacs this feature is called the "kill ring".

The yankring plugin allows the user to configure the number of yanked and
deleted text.  After text has been pasted, it can be replaced with a
previous value from the yankring.


New features and bug fixes for this version:

NF: The yankring now respects the cpoptions setting, if 'y' is included and
you press '.', the previous yank command is executed and added to the
yankring.  You can also add this behaviour by setting this in your |vimrc|:
        let g:yankring_dot_repeat_yank = 1

NF: Duplicates will not be added to the yankring by default.  If a duplicate
is found, the element will be moved to the top of the yankring.  This can be
controlled by setting this in your |vimrc|:
        let g:yankring_ignore_duplicate = 0 (1 is default)

BF: Regression from version 1.4, the '.' operator may incorrectly insert
garbage.


Thanks to Alexei Alexandrov for his suggestions and bug reports.


Enjoy.
Dave

I have mappings:

inoremap  { {<CR>}<C-O>O
inoremap [ []<LEFT>
inoremap ( ()<LEFT>
inoremap " ""<LEFT>
inoremap ' ''<LEFT>

...in my .vimrc. This all works fine with regular vim but with gvim the
{ doesn't give me the closing }. Also in gvim If I insert ' I get ''
but then when I want to delete the first ' and hit backspace (in insert
mode right after typing ') it just won't do that. This is just with
gvim, vim works correctly.

I would also like to know if it's possible to make the scrollbar only
scroll where there is some content (gvim). Now it scrolls as far as
half-screen down with empty lines (marked as ~ ). What I really want is
that the scroll bar would act as usual scrollbars do: the longer the
text the smaller the scrollbar, without showing the empty lines. Now
it's allways the same size.

The OS is macosx, if it matters...

--antti

I have a file that I want to do a search and replace for any lines that
start with two (and only two) spaces followed by a non-space character
and replace it with two spaces, an asterisk, a space, then the non-space
character. For example, I want to replace this:
   Some Text
   and some more text
with
   * Some Text
   * and some more text

I tried this command
:%s/^  ([\S])/  * \1/g

but it just tells me the search pattern was not found. Can anybody help
me find the right expression?

Cory

> I tried this command
> :%s/^  ([\S])/  * \1/g

So close, yet just enough to mess things up.  You *either* want
"\S" or "[^ ]".  Your current expression would find lines
starting with two spaces followed by a capital S only (and maybe
a backslash).

Try

	 :%s/^  \(\S\)/  * \1

HTH,

-tim

Cory Riddell wrote:

>I have a file that I want to do a search and replace for any lines that
>start with two (and only two) spaces followed by a non-space character
>and replace it with two spaces, an asterisk, a space, then the non-space
>character. For example, I want to replace this:
>  Some Text
>  and some more text
>with
>  * Some Text
>  * and some more text
>
>I tried this command
>:%s/^  ([\S])/  * \1/g
>
>but it just tells me the search pattern was not found. Can anybody help
>me find the right expression?
>
>Cory
>
>
>
>
>________________________________________________________________________
>nexatechnologies.com - Inbound email scanned for viruses by MessageLabs.
>
>
>
Cory,

Take out the square brakets and add backslashes on the parens in other
words:

:%s/^  \(\S\)/  * \1/g

Scott LaBounty
Nexa Technologies, Inc.

________________________________________________________________________
This nexatechnologies.com email has been scanned for all viruses by the
MessageLabs Email Security System.

On Fri, 2005-04-01 at 17:51 +0000, Cory Riddell wrote:
> I have a file that I want to do a search and replace for any lines that
> start with two (and only two) spaces followed by a non-space character
> and replace it with two spaces, an asterisk, a space, then the non-space
> character. For example, I want to replace this:
>   Some Text
>   and some more text
> with
>   * Some Text
>   * and some more text
>
> I tried this command
> :%s/^  ([\S])/  * \1/g

You have to escape ( and ) used for submatching (unless there is some
option I'm not aware of).  The brackets around the non-space specifier
are not needed, either.  Since the expression can only match once per
line because of the beginning of line anchor, the 'g' option is not
needed either.

:%s/^  \(\S\)/  * \1/

--
t. scott urban <scottu@...>

Thanks all for the amazingly quick replies.

Cory

antti wrote:
> I have mappings:
>
> inoremap  { {<CR>}<C-O>O
> inoremap [ []<LEFT>
> inoremap ( ()<LEFT>
> inoremap " ""<LEFT>
> inoremap ' ''<LEFT>
>
> ...in my .vimrc. This all works fine with regular vim but with gvim the
> { doesn't give me the closing }. Also in gvim If I insert ' I get '' but
> then when I want to delete the first ' and hit backspace (in insert mode
> right after typing ') it just won't do that. This is just with gvim, vim
> works correctly.

check the 'backspace' (and 'compatible') options.
>
> I would also like to know if it's possible to make the scrollbar only
> scroll where there is some content (gvim). Now it scrolls as far as
> half-screen down with empty lines (marked as ~ ). What I really want is
> that the scroll bar would act as usual scrollbars do: the longer the
> text the smaller the scrollbar, without showing the empty lines. Now
> it's allways the same size.
>
> The OS is macosx, if it matters....
>
> --antti

It is a Vim constant that the scrollbar allows scrolling until the
_bottom_ line of the file is at the _top_ of the window. That is, AFAIK,
not changeable. Screen lines beyond the end of the file (also when the
file is too short to fill the window) are indicated by tildes, usually
in blue. It is not possible to scroll the _top_ line of the file lower
than the top of the window.

In my W32 gvim, the scrollbar thumb shows what percentage of the total
(file size + one window height - 1) is visible in the window (down to a
certain minimum size: AFAICT, it never reduces to less than a millimeter
or so). The thumb is the whole height of the window when there is only
one line in the file.

What kind of GUI do you use? (Mac Classic [is that what is called
Carbon? I'm not sure], or on X11 for MacOsX: X11 with GTK+1, X11/Athena,
X11/Motif, X11/GTK+2, ...) The answer to the ":version" command should
tell you, there are two lines near the top with the word "version" in
them: one of them (usually the second line) says for which OS family
this Vim was compiled; another one (usually fourth or fifth) gives which
set of features (from tiny to huge) was included and, for X11 gvim,
which particular GUI interface. How scrollbars react may be a function
of which particular GUI was included at compile-time, and for which
particular OS.

Best regards,
Tony.

Things have definitely gotten better!  Thanks!

A couple more items that I just noticed are the use of repeat (using
'.') commands of i, I, a, or A.  As common behavior is seen between all
stated commands, I will only provide a single example.  Take the lines
below.

One
Two
Three
Four

Move to Two
Type 'a' to enter insert mode after the T.  Enter the word 'FIVE'.  Hit
escape.

One
TFIVEwo
Three
Four

Move to Four.  Hit '.'  Nothing happens.
It should insert FIVE just after the F in Four.
As noted above, similar (lack of) behavior is seen for i, I, a, and A.

One other quick thing to note is that the o and O commands don't repeat
properly.  For the most part, the problem is analagous to that seen for
i, I, a, and A.  The exception is when 'o' is used simply to create a
new blank line (Typing 'o' and immediately hitting escape).
Repeating this operation does open a new line, but leaves you in insert
mode.  It should simply create a new blank line below  your current
line and leave you in normal mode.

Brent



On Apr 1, 2005, at 6:36 AM, David Fishburn wrote:

>
>
> YankRing.vim : Maintains a history of previous yanks and deletes
> http://www.vim.org/scripts/script.php?script_id=1234
>
> description
> Vim already maintains a list of numbered registers containing the last
> 9
> deletes.  These previous deletes can be referenced using [register]p,
> so "1p
> will paste the last delete, "2p the 2nd last delete.  For more
> information
> see |quote_number|.
>
> Vim does not provide any mechanism to reference previous yanked text.
> In
> Emacs this feature is called the "kill ring".
>
> The yankring plugin allows the user to configure the number of yanked
> and
> deleted text.  After text has been pasted, it can be replaced with a
> previous value from the yankring.
>
>
> New features and bug fixes for this version:
>
> NF: The yankring now respects the cpoptions setting, if 'y' is
> included and
> you press '.', the previous yank command is executed and added to the
> yankring.  You can also add this behaviour by setting this in your
> |vimrc|:
>        let g:yankring_dot_repeat_yank = 1
>
> NF: Duplicates will not be added to the yankring by default.  If a
> duplicate
> is found, the element will be moved to the top of the yankring.  This
> can be
> controlled by setting this in your |vimrc|:
>        let g:yankring_ignore_duplicate = 0 (1 is default)
>
> BF: Regression from version 1.4, the '.' operator may incorrectly
> insert
> garbage.
>
>
> Thanks to Alexei Alexandrov for his suggestions and bug reports.
>
>
> Enjoy.
> Dave
>

I've failed to see the reply :-(

Thumbs up, Jürgen! Vielen Dank.

--- Jürgen Krämer <jkr@...> wrote:

>
> Hai,
>
> John Doe wrote:
> > > John Doe wrote:
> > >
> > > > Check this out:
> > > > echo "09" + 0
> > > >
> > > > seems vim is unable to handle leading zeros.
> > >
> > > because you try to add a string and a number,
> VIM has to convert the
> > > string into a number first. Strings with leading
> zeroes are
> > > considered to be octal numbers, but 09 is not a
> valid octal number.
> > > Therefore "09" is converted to 0, leading to 0 +
> 0 which is 0.
> >
> > Well it most definetly is problematic as
> > strftime("%H") returns decimal strings like "09"
> "04",
> > etc.. String->number conversions break when it's
> nine o'clock.
>
> then remove those leading zeroes first:
>
>   echo substitute(strftime('%H'), '^0*\(.\)', '\1',
> '') + 0




__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

>  > Now if you would find a workaround that would
> enable one
>  > to set the insert mode from within an event
> handler
>  > immediately ...
>
> I'm not sure what you mean by this.

If I write startinsert out of an autocommand (timing)
handler, the insert mode will not kick in immediately,
only after pressing a key.




__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs

Hello,

I am new to this list, but not to Vim (however I still have much to
learn). I have a problem making a syntax plugin for Redcode assembly
files.

I have a problem to separate operators (+, -) from the sign of a number
(positive or negative). In this example both are marked in Vim as
operators, but one is an operator and the other a sign:

mov 0, dst+1  -- an addition operator
mov 0, -1     -- a negative sign

I use in my syntax file:

syntax match redcodeNumber /[-+]\?[0-9]\d*/
syntax match redcodeExprArithOp /+\|-\|\/\|\*\|%/

How can I solve this?

NOTE: the number constants can be preceded by the following modifiers: #
$ @ * < > { }. Like: "add #-3, dst".

Thanks and Best Regards,
Ale

> -----Original Message-----
> From: Eric Leenman [mailto:ELeenman@...]
> Sent: Friday, April 01, 2005 6:30 AM
> To: sravishankar@...; madhanganesh@...; vim@...
> Subject: How to get get Intellisense for GVIM working.
>
> Hi,
>
> I'm trying to use Intellisense for VIM.
> (http://www.vim.org/scripts/script.php?script_id=747)
>
> I 've done all what is set in the intellisense.txt.
>
> One thing that I did different was to set the
> $VIM_INTELLISNESE as described.
> I did take a look at the intellisense.vim file and added it
> that way in my _vimrc
>
> I have the following in my _vimrc file:
> [start of _vimrc]
> set nocompatible
> source $VIMRUNTIME/vimrc_example.vim
> source $VIMRUNTIME/mswin.vim
> behave mswin
> let g:intellisense_root_dir=expand('$VIM/Intellisense')
>
> [... personal mappings...]
>
> {end of _vimrc]
>
> I have removed all other plugins to exclude the change that
> they could vim scripts interferring.
>
>
> When I press <C-Space-a> it does select everything (like
> CTRL-A in windows), iso showing the pop-up windows When I
> press <C-Space-f> it does nothing.

Sorry, meant to respond this morning.

What language are you trying complete?
  Java
C++
C#
JSP
XML
HTML
SQL

By <C-Space-a> and <C-Space-f> I am assuming you are using the SQL
Intellisense plugin.

So first thing to check:
1.  Restart Vim and check if there are any messages displayed.
gvim dave.sql
:mess

2.  What version of Intellisense are you using:
vim\vimfiles\plugin\intellisense.vim
" Version : 1.??

3.  Look in this directory
> let g:intellisense_root_dir=expand('$VIM/Intellisense')

You should have a:
sqlft.dll
sqlft <directory>

In sqlft<directory>
14,112  sqlall.txt
  8,210  sqlfunctions.txt
  1,390  sqlkeywords.txt
    152  sqloperators.txt
  3,258  sqloptions.txt
    812  sqlstatements.txt
    290  sqltypes.txt


4.  > let g:intellisense_root_dir=expand('$VIM/Intellisense')
Since that is the default, this is not necessary.


Dave

9u049u89gh89fsdpokofkdpbm3ß4i

Dnia pi±tek, 1 kwietnia 2005 22:44, Alejandro Pulver napisa³:
> Hello,
>
> I am new to this list, but not to Vim (however I still have much to
> learn). I have a problem making a syntax plugin for Redcode assembly
> files.
>
> I have a problem to separate operators (+, -) from the sign of a number
> (positive or negative). In this example both are marked in Vim as
> operators, but one is an operator and the other a sign:
>
> mov 0, dst+1  -- an addition operator
> mov 0, -1     -- a negative sign

Put space in syntax definition here (maybe zero-width)
>
> I use in my syntax file:
>
> syntax match redcodeNumber /[-+]\?[0-9]\d*/
                               ^ \s\@<=

And you can replace [0-9]\d* with \d\+
Note: I am never sure which zero-width operator is good, so check :h /\@
before writing 'this is not working' :)

> syntax match redcodeExprArithOp /+\|-\|\/\|\*\|%/

Here also you could add: \s\@<! before elements or explicitly
[$@*<>{}]\@<! .

m.

--
LaTeX + Vim = http://vim-latex.sourceforge.net/
Vim-list(s) Users Map: (last change 12 Feb)
  http://skawina.eu.org/mikolaj/vimlist
CLEWN - http://clewn.sf.net

On Sat, 2 Apr 2005 12:27:10 +0200
Mikolaj Machowski <mikmach@...> wrote:

> Dnia pi±tek, 1 kwietnia 2005 22:44, Alejandro Pulver napisa³:
> > Hello,
> >
> > I am new to this list, but not to Vim (however I still have much to
> > learn). I have a problem making a syntax plugin for Redcode assembly
> > files.
> >
> > I have a problem to separate operators (+, -) from the sign of a
> > number(positive or negative). In this example both are marked in Vim
> > as operators, but one is an operator and the other a sign:
> >
> > mov 0, dst+1  -- an addition operator
> > mov 0, -1     -- a negative sign
>
> Put space in syntax definition here (maybe zero-width)
> >
> > I use in my syntax file:
> >
> > syntax match redcodeNumber /[-+]\?[0-9]\d*/
>                               ^ \s\@<=
>
> And you can replace [0-9]\d* with \d\+
> Note: I am never sure which zero-width operator is good, so check :h
> /\@ before writing 'this is not working' :)
>
> > syntax match redcodeExprArithOp /+\|-\|\/\|\*\|%/
>
> Here also you could add: \s\@<! before elements or explicitly
> [$@*<>{}]\@<! .
>
> m.
>

Hello,

Thank you for your reply.

I ended up with the following to match numbers (is it fine? can it be
optimized?):

/[ \t#$@*<>{},]\@<=[-+]\?\d\+\|\d\+/

And this to match the - and + operators (can it be optimized?):

/[ \t\s#$@*<>{},]\@<![+-]\|[ \s\t][+-][ \s\t]/

Thanks and Best Regards,
Ale

Hi,

   I would like to know how to tell vim that the STDIN will
never end, so don't bother displaying

    Vim: Reading from stdin...

  but rather display immediately whatever you get, and keep
getting more input (at least every half a second or so), in
order to display whichever line I want to see.

    In this aspect, the effect would be similar to standard
less behavior, except that I would still have syntax
hiliting and searches and all the goodies of vim.

    Thanks,

      JJ

I've got the latest taglist plugin installed on a debian box along with
exuberant-ctags and vim 6.3.

For a typical source code file, when :Tlist is invoked, the window
splits and I can see the current file, but no tags.

But when I vim into the actual taglist.vim file itself and invoke
:Tlist, I get all of the taglist.vim vars and functions, etc.  Works
great.

So it's working great on itself, but not on any other source files.

Separately, from the command line, if I run:

ctags  -f - --format=2 --excmd=pattern --fields=nks   some-source-file

... ctags displays all the tags nicely.

Anyone been down this path before?

Thanks,
Kevin

--

Hi,

On Apr 2, 2005 10:02 AM, Kevin Coyner <kevin@...> wrote:
>
> I've got the latest taglist plugin installed on a debian box along with
> exuberant-ctags and vim 6.3.
>
> For a typical source code file, when :Tlist is invoked, the window
> splits and I can see the current file, but no tags.
>
> But when I vim into the actual taglist.vim file itself and invoke
> :Tlist, I get all of the taglist.vim vars and functions, etc.  Works
> great.
>
> So it's working great on itself, but not on any other source files.
>
> Separately, from the command line, if I run:
>
> ctags  -f - --format=2 --excmd=pattern --fields=nks   some-source-file
>
> ... ctags displays all the tags nicely.
>
> Anyone been down this path before?
>

Did you try the steps mentioned in the following page?

http://www.geocities.com/yegappan/taglist/faq.html

- Yegappan

Dnia sobota, 2 kwietnia 2005 18:46, Alejandro Pulver napisał:
> I ended up with the following to match numbers (is it fine? can it be
> optimized?):
>
> /[ \t#$@*<>{},]\@<=[-+]\?\d\+\|\d\+/
>
> And this to match the - and + operators (can it be optimized?):
>
> /[ \t\s#$@*<>{},]\@<![+-]\|[ \s\t][+-][ \s\t]/

\s matches any white-space character including tabs, so [ \s\t] can be
replaced by just \s.

m.

On Sat, 2 Apr 2005 20:23:46 +0200
Mikolaj Machowski <mikmach@...> wrote:

> Dnia sobota, 2 kwietnia 2005 18:46, Alejandro Pulver napisał:
> > I ended up with the following to match numbers (is it fine? can it
> > be optimized?):
> >
> > /[ \t#$@*<>{},]\@<=[-+]\?\d\+\|\d\+/
> >
> > And this to match the - and + operators (can it be optimized?):
> >
> > /[ \t\s#$@*<>{},]\@<![+-]\|[ \s\t][+-][ \s\t]/
>
> \s matches any white-space character including tabs, so [ \s\t] can be
> replaced by just \s.
>
> m.
>

Hello,

Thank you for your reply.

I tried /[#$@*<>{},\s]\@<=[-+]\?\d\+\|\d\+/ (\s instead of [ \t\s]) but
if I have:

dst: dat #0, # -3

The '-' is not marked as a number. But if I have:

dst: dat #0, #-3

It is marked as a number.

What is happening?

Thanks and Best Regards,
Ale

P.S.: is there a way to define a group of atoms for using in a regular
expression? Like grouping all the modifiers in one "variable" or "group"
and put the group name in the regular expressions.

On Sat, Apr 02, 2005 at 10:12:18AM -0800, Yegappan Lakshmanan wrote......

> > Separately, from the command line, if I run:
> >
> > ctags  -f - --format=2 --excmd=pattern --fields=nks   some-source-file
> >
> > ... ctags displays all the tags nicely.
> >
> > Anyone been down this path before?
> >
>
> Did you try the steps mentioned in the following page?
>
> http://www.geocities.com/yegappan/taglist/faq.html
>
> - Yegappan


Thanks.

Yes, I started there.  That's where I found the ctags command listed
above, which works just fine.  And like I mentioned earlier, taglist is
working fine when I open up $HOME/.vim/plugin/taglist.vim.  I can see
all of its functions and vars.

When taglist runs, does it need permissions to write temp files
anywhere?

--
Kevin Coyner  GnuPG key: 1024D/8CE11941  http://rustybear.com/pubkey.php

Dnia sobota, 2 kwietnia 2005 20:48, Alejandro Pulver napisał:
> Hello,
>
> Thank you for your reply.
>
> I tried /[#$@*<>{},\s]\@<=[-+]\?\d\+\|\d\+/ (\s instead of [ \t\s]) but

You cannot use \s (or any other class) inside of []
> if I have:
>
> dst: dat #0, # -3

Here catches operator rule. [] is always one char. Try
/\([#$@*<>{},]\s*\)\@<=[-+]\?\d\+\|\d\+/

> P.S.: is there a way to define a group of atoms for using in a regular
> expression? Like grouping all the modifiers in one "variable" or "group"
> and put the group name in the regular expressions.

You could try to put it into variable and resolve them in syntax file
with exe (:h :exe) but this is tricky and can significantly slow down
Vim.

m.


--
[`] 2005-04-02 21:37

I have been using Ispell from the command line for some time
now. Today I put in the vimspell plugin.  Now I need to learn
how to use it. For example when I click on the plugin menu, and
then alternative, I get a list of alternatives. If i key a
number on the numeric keypad only,(nice little gotcha) it
selects that alternative and substitutes it.

Since the A in Alternative is underlined I presume that is a
shortcut key. But how do I activate it? I have tried a, A,
<Ctl>A and so on.

The help on vimspell talks about using the backslash key as a
"leader" to a command sequence. It doesn't seem to work either.

I tried reading the help in the vimspell.vim file itself but it
was folded. I forget how to unfold.

The Oualline book covers none of these topics.

--
John Culleton
Able Indexers and Typesetters
http://wexfordpress.com

Sometime around Sun, Apr 03, 2005 at 12:42:00AM +0000, John R. Culleton said:
> I have been using Ispell from the command line for some time
> now. Today I put in the vimspell plugin.  Now I need to learn
> how to use it. For example when I click on the plugin menu, and
> then alternative, I get a list of alternatives. If i key a
> number on the numeric keypad only,(nice little gotcha) it
> selects that alternative and substitutes it.
>
> Since the A in Alternative is underlined I presume that is a
> shortcut key. But how do I activate it? I have tried a, A,
> <Ctl>A and so on.
>
> The help on vimspell talks about using the backslash key as a
> "leader" to a command sequence. It doesn't seem to work either.
>
> I tried reading the help in the vimspell.vim file itself but it
> was folded. I forget how to unfold.
>
> The Oualline book covers none of these topics.
>
> --
> John Culleton
> Able Indexers and Typesetters
> http://wexfordpress.com
>

Not sure about the vimspell thing, but to unfold all the folds in a file, do
zR

Godspeed,

Brett

--
Brett Kelly
inkedmn@...
http://inkedmn.com:8000
GPG Public Key: http://inkedmn.com:8000/stuff/inkedmn.asc

h200@... wrote:
>
>  Hi,
>
>   I would like to know how to tell vim that the STDIN will
> never end, so don't bother displaying
>
>    Vim: Reading from stdin...
>
>  but rather display immediately whatever you get, and keep
> getting more input (at least every half a second or so), in
> order to display whichever line I want to see.
>
>    In this aspect, the effect would be similar to standard
> less behavior, except that I would still have syntax
> hiliting and searches and all the goodies of vim.
>
>    Thanks,
>
>      JJ
>
>
>
I may be wrong, but I believe it's not possible. IIUC, Vim's editing
"strategy" is to read the whole file into memory, then display it and
allow the user to edit it. If the editfile is a device which will
produce endless data without an end-of-file signal (such as, but not
limited to, /dev/zero on Unix), Vim will never reach the end of its
input reading and will, IIUC, either have to be killed manually, or
terminate when reaching the end of available memory size (system memory
or 'maxmem'/'maxmemtot' memory, whichever is smaller; the latter will
not go higher than 2 GB, at least not on systems with 32-bit longint
format -- it's not clear to me [conflict between ":help 'maxmemtot'" and
":help limits"] whether it will go higher on 64-bit machines).

Best regards,
Tony.

On Sunday 03 April 2005 14:36, A. J. Mechelynck wrote:
> I may be wrong, but I believe it's not possible. IIUC, Vim's editing
> "strategy" is to read the whole file into memory, then display it and
> allow the user to edit it. If the editfile is a device which will
> produce endless data without an end-of-file signal (such as, but not
> limited to, /dev/zero on Unix), Vim will never reach the end of its
> input reading and will, IIUC, either have to be killed manually, or
> terminate when reaching the end of available memory size (system memory
> or 'maxmem'/'maxmemtot' memory, whichever is smaller; the latter will
> not go higher than 2 GB, at least not on systems with 32-bit longint
> format -- it's not clear to me [conflict between ":help 'maxmemtot'" and
> ":help limits"] whether it will go higher on 64-bit machines).
>
> Best regards,
> Tony.

Though your statement is essentially true (to my knowledge) you do not
have to manually kill your vim in such a case. You can also ^C to
terminate the reading from stdin.
You can try
   yes|vim -
But ... don't wait too long to hit ^C, "yes" will produce it's output
rather quickly

HTH, Michael