Re: WARNING! Don't update your local svn repository now!

[Edward L. Fox]

On 5/12/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:


Nicolas Weber wrote:

> > The directories structure of the Subversion repository has been
> > changed. Please use this command to checkout the latest sources:
> >
> > svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
> >
> > If you had checked out a copy of the sources before, please run this
> > command in your source root directory to switch into the current
> > branch:
> >
> > svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1
>
> Can someone update http://www.vim.org/subversion.php to reflect these
> changes?

I was still discussing what should actually be there, and making sure
that SVN contains that.

In my opinion "vim7" should get you the latest stable version.  So far
that is 7.0.243, thus 7.0 with patches.  As soon as Vim 7.1 is out of
beta then "vim7" should get you Vim 7.1.

"vim7.1" should get you the latest version of Vim 7.1.  So far that is
the beta version.  After the release it will be the stable version, thus
the same as "vim7".

Still need to check that it actually works this way.


It's already this way.


There might also be other ways to get one of these, but that is less
relevant.

In my opinion we should keep it easy for the downloader to select one of
the available versions.  The download page would only need one or two
alternatives.

I have never maintained a SVN repository, thus have no idea how
difficult or easy these things are!


I've found an easy way to solve that problem. So now can we can announce?


--
In a world without walls and borders, who needs windows and gates?

 /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

Re: comments after brackets with vim?

[A.J.Mechelynck]

Simon Butler wrote:


On May 11, 2007, at 4:48 PM, A.J.Mechelynck wrote:


Simon Butler wrote:
[...]
maybe i'm missing something here. my objective is not to write the 
comments by hand. they should appear automatically after the 
brackets, thats how skill mode in emacs is setup and i'd like to be 
able to do the same thing in vim

[...]

ah. I suppose it could be done by means of a lot of mappings, but it 
would not be easy. Unless a plugin for that kind of thing already 
exists at vim-online ("Search for Scripts" at 
http://www.vim.org/search.php ), I personally don't think it wouyld be 
worth the trouble of writing and debugging that kind of plugin. Of 
course, YMMV.




i'm an emacs user considering moving to vim and this is something that 
would i would definitely miss.


skill/lisp has a lot of brackets and commenting which bracket closes 
which statement is very useful when debugging...





Vimscript has much less brackets, so that's one reason why that kind of 
comments is less necessary. There have been threads on this list recently 
discussing automatic pairing of brackets; and in Vim placing the cursor on any 
bracket (by default () [] {} but it's configurable: e.g. I've added the &; 
pair in an "after-plugin" for HTML) you see it and its mate highlighted, by 
default with a light-cyan background. You may if you want define (e.g. for C) 
mappings like the following:


:imap   (   ()
:imap   [   []
:imap   {   {

Also, if the cursor is on a bracket, hitting % moves it to its mate, scrolling 
the text if necessary. The "matchit" plugin extends this functionality to 
paired words of more than one character, like if... elseif... else... endif, 
try... catch... finally... endtry, while... enwhile, function... endfunction, 
or HTML paired tags.


To repeat a function name or an if-condition in a comment you would have to 
write a function asking the user the name and writing it in twice, once at the 
cursor and once in a command after the ":endfunction" or ":endif" that it 
would write on the next line; and you would have to remap (or maybe define 
abbreviations for)


if
while
try
function
for

and maybe others (these are those which immediately come to mind). It is 
doable, but I'm not convinced that it's better than adding the comments by 
hand where they're actually needed (in a three-line if they probably wouldn't 
be). You may want to look at $VIMRUNTIME/vimrc_example.vim (in a Vim 
installation, and from within Vim) for a "typical" Vim script.


Now if you want to write Lisp (which Vim doesn't use for its inner workings) 
that's a different matter. It might even be easier, by remapping only the left 
bracket and finding what's before it, but I don't know Lisp well enough to be 
sure.



Best regards,
Tony.
--
You will think of something funnier than this to add to the fortunes.

Re: comments after brackets with vim?

[Simon Butler]

On May 11, 2007, at 4:48 PM, A.J.Mechelynck wrote:


Simon Butler wrote:
[...]
maybe i'm missing something here. my objective is not to write the  
comments by hand. they should appear automatically after the  
brackets, thats how skill mode in emacs is setup and i'd like to  
be able to do the same thing in vim

[...]

ah. I suppose it could be done by means of a lot of mappings, but  
it would not be easy. Unless a plugin for that kind of thing  
already exists at vim-online ("Search for Scripts" at http:// 
www.vim.org/search.php ), I personally don't think it wouyld be  
worth the trouble of writing and debugging that kind of plugin. Of  
course, YMMV.




i'm an emacs user considering moving to vim and this is something  
that would i would definitely miss.


skill/lisp has a lot of brackets and commenting which bracket closes  
which statement is very useful when debugging...

Re: comments after brackets with vim?

[A.J.Mechelynck]

Simon Butler wrote:
[...]
maybe i'm missing something here. my objective is not to write the 
comments by hand. they should appear automatically after the brackets, 
thats how skill mode in emacs is setup and i'd like to be able to do the 
same thing in vim

[...]

ah. I suppose it could be done by means of a lot of mappings, but it would not 
be easy. Unless a plugin for that kind of thing already exists at vim-online 
("Search for Scripts" at http://www.vim.org/search.php ), I personally don't 
think it wouyld be worth the trouble of writing and debugging that kind of 
plugin. Of course, YMMV.



Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
229. You spend so much time thinking what to add on this list.

Re: comments after brackets with vim?

[Simon Butler]

On May 11, 2007, at 4:26 PM, A.J.Mechelynck wrote:


Simon Butler wrote:

Hi Tony, thx for getting back to me, my comments below:
On May 11, 2007, at 3:42 PM, A.J.Mechelynck wrote:

Simon Butler wrote:
hi, when i write this skill (cadence extension language)  
fragment in emacs i get the following:

procedure( vscCheckpointHier( @key lib cell view message inclibs )
let(( ddCVs )
vscPrint0(sprintf( nil "Hierarchy for %s,%s,%s ..." lib  
cell view ))
when( ddCVs = vscGetHierarchyDDs( ?lib lib ?cell cell ? 
view view

  ?inclibs inclibs )
vscPrint0(sprintf( nil "  %d cellviews." length 
(ddCVs) ))

vscCheckpoint( ddCVs ?message message)
); when ddCVs
); let
); procedure vscCheckpointHier
Notice all the comments placed on the closing brackets. Is there  
a way to make vim do this?

TIA


In Vimscript, IIUC what you mean, a comment starts with a double  
quote. Most statements accept a comment after them; a few don't,  
because they see the quote as part of their arguments. See  
":help :quote".
There is a workaround to add comments even after the commands  
(such as :map) which don't accept them (see ":help :comment"):


exe 'map  ' |" find tag under cursor


So you could do (not sure whether I read emacs syntax correctly,  
but the following should give you a notion of what is possible):


function vscCheckpointHere(key, lib, cell, view, message, inclibs)
let ddCVS = vscPrint0(printf("Hierarchy for %s, %s, %s ...",
\ a:lib, a:cell, a:view))
if ddCVS == vscGetHierarchyDDs(a:lib, a:cell, a:view, a:inclibs)
let ddCVS = vscPrint0(printf("  %d cellviews.", length 
(ddCVS))

call vsCheckpoint(a:message)
endif " ddCVS
" endfunction vsCheckpointHere
endfunction

(I'm not sure whether or not a comment is allowed after  
":endfunction", see ":help :endfunction")



how do i set this up? do i need something in my .vimrc?


The ability to use comments in vimscript (including in your vimrc)  
is part of Vim. You don't need to set up anything, except maybe  
write the comments when you write the code.




maybe i'm missing something here. my objective is not to write the  
comments by hand. they should appear automatically after the  
brackets, thats how skill mode in emacs is setup and i'd like to be  
able to do the same thing in vim



If your vim code is properly indented, you might also have less  
need for this kind of comments.


the indenting was correct when i send the email but the formatting  
changed by the time it made it to the list i guess

thx!


I mean: the differences between a C-like language like vimscript  
and a lisp-like language like emacs-script might perhaps make this  
kind of comments less necessary if the code is properly indented.




ok, but the code was properly indented. i still find the comments  
useful personally



thx again

Re: comments after brackets with vim?

[A.J.Mechelynck]

Simon Butler wrote:


Hi Tony, thx for getting back to me, my comments below:

On May 11, 2007, at 3:42 PM, A.J.Mechelynck wrote:


Simon Butler wrote:
hi, when i write this skill (cadence extension language) fragment in 
emacs i get the following:

procedure( vscCheckpointHier( @key lib cell view message inclibs )
let(( ddCVs )
vscPrint0(sprintf( nil "Hierarchy for %s,%s,%s ..." lib cell 
view ))

when( ddCVs = vscGetHierarchyDDs( ?lib lib ?cell cell ?view view
  ?inclibs inclibs )
vscPrint0(sprintf( nil "  %d cellviews." length(ddCVs) ))
vscCheckpoint( ddCVs ?message message)
); when ddCVs
); let
); procedure vscCheckpointHier
Notice all the comments placed on the closing brackets. Is there a 
way to make vim do this?

TIA


In Vimscript, IIUC what you mean, a comment starts with a double 
quote. Most statements accept a comment after them; a few don't, 
because they see the quote as part of their arguments. See ":help 
:quote".
There is a workaround to add comments even after the commands (such as 
:map) which don't accept them (see ":help :comment"):


exe 'map  ' |" find tag under cursor


So you could do (not sure whether I read emacs syntax correctly, but 
the following should give you a notion of what is possible):


function vscCheckpointHere(key, lib, cell, view, message, inclibs)
let ddCVS = vscPrint0(printf("Hierarchy for %s, %s, %s ...",
\ a:lib, a:cell, a:view))
if ddCVS == vscGetHierarchyDDs(a:lib, a:cell, a:view, a:inclibs)
let ddCVS = vscPrint0(printf("  %d cellviews.", length(ddCVS))
call vsCheckpoint(a:message)
endif " ddCVS
" endfunction vsCheckpointHere
endfunction

(I'm not sure whether or not a comment is allowed after 
":endfunction", see ":help :endfunction")




how do i set this up? do i need something in my .vimrc?


The ability to use comments in vimscript (including in your vimrc) is part of 
Vim. You don't need to set up anything, except maybe write the comments when 
you write the code.




If your vim code is properly indented, you might also have less need 
for this kind of comments.




the indenting was correct when i send the email but the formatting 
changed by the time it made it to the list i guess


thx!




I mean: the differences between a C-like language like vimscript and a 
lisp-like language like emacs-script might perhaps make this kind of comments 
less necessary if the code is properly indented.



Best regards,
Tony.
--
The rain it raineth on the just
And also on the unjust fella,
But chiefly on the just, because
The unjust steals the just's umbrella.

Re: comments after brackets with vim?

[Simon Butler]

Hi Tony, thx for getting back to me, my comments below:

On May 11, 2007, at 3:42 PM, A.J.Mechelynck wrote:


Simon Butler wrote:
hi, when i write this skill (cadence extension language) fragment  
in emacs i get the following:

procedure( vscCheckpointHier( @key lib cell view message inclibs )
let(( ddCVs )
vscPrint0(sprintf( nil "Hierarchy for %s,%s,%s ..." lib  
cell view ))
when( ddCVs = vscGetHierarchyDDs( ?lib lib ?cell cell ? 
view view

  ?inclibs inclibs )
vscPrint0(sprintf( nil "  %d cellviews." length(ddCVs) ))
vscCheckpoint( ddCVs ?message message)
); when ddCVs
); let
); procedure vscCheckpointHier
Notice all the comments placed on the closing brackets. Is there a  
way to make vim do this?

TIA


In Vimscript, IIUC what you mean, a comment starts with a double  
quote. Most statements accept a comment after them; a few don't,  
because they see the quote as part of their arguments. See  
":help :quote".
There is a workaround to add comments even after the commands (such  
as :map) which don't accept them (see ":help :comment"):


exe 'map  ' |" find tag under cursor


So you could do (not sure whether I read emacs syntax correctly,  
but the following should give you a notion of what is possible):


function vscCheckpointHere(key, lib, cell, view, message, inclibs)
let ddCVS = vscPrint0(printf("Hierarchy for %s, %s, %s ...",
\ a:lib, a:cell, a:view))
if ddCVS == vscGetHierarchyDDs(a:lib, a:cell, a:view, a:inclibs)
let ddCVS = vscPrint0(printf("  %d cellviews.", length(ddCVS))
call vsCheckpoint(a:message)
endif " ddCVS
" endfunction vsCheckpointHere
endfunction

(I'm not sure whether or not a comment is allowed after  
":endfunction", see ":help :endfunction")




how do i set this up? do i need something in my .vimrc?

If your vim code is properly indented, you might also have less  
need for this kind of comments.




the indenting was correct when i send the email but the formatting  
changed by the time it made it to the list i guess


thx!

Re: comments after brackets with vim?

[A.J.Mechelynck]

Simon Butler wrote:


hi, when i write this skill (cadence extension language) fragment in 
emacs i get the following:



procedure( vscCheckpointHier( @key lib cell view message inclibs )
let(( ddCVs )
vscPrint0(sprintf( nil "Hierarchy for %s,%s,%s ..." lib cell 
view ))

when( ddCVs = vscGetHierarchyDDs( ?lib lib ?cell cell ?view view
  ?inclibs inclibs )
vscPrint0(sprintf( nil "  %d cellviews." length(ddCVs) ))
vscCheckpoint( ddCVs ?message message)
); when ddCVs
); let
); procedure vscCheckpointHier


Notice all the comments placed on the closing brackets. Is there a way 
to make vim do this?


TIA



In Vimscript, IIUC what you mean, a comment starts with a double quote. Most 
statements accept a comment after them; a few don't, because they see the 
quote as part of their arguments. See ":help :quote".


There is a workaround to add comments even after the commands (such as :map) 
which don't accept them (see ":help :comment"):


exe 'map  ' |" find tag under cursor


So you could do (not sure whether I read emacs syntax correctly, but the 
following should give you a notion of what is possible):


function vscCheckpointHere(key, lib, cell, view, message, inclibs)
let ddCVS = vscPrint0(printf("Hierarchy for %s, %s, %s ...",
\ a:lib, a:cell, a:view))
if ddCVS == vscGetHierarchyDDs(a:lib, a:cell, a:view, a:inclibs)
let ddCVS = vscPrint0(printf("  %d cellviews.", length(ddCVS))
call vsCheckpoint(a:message)
endif " ddCVS
" endfunction vsCheckpointHere
endfunction

(I'm not sure whether or not a comment is allowed after ":endfunction", see 
":help :endfunction")


If your vim code is properly indented, you might also have less need for this 
kind of comments.




Best regards,
Tony.

comments after brackets with vim?

[Simon Butler]

hi, when i write this skill (cadence extension language) fragment in  
emacs i get the following:



procedure( vscCheckpointHier( @key lib cell view message inclibs )
let(( ddCVs )
vscPrint0(sprintf( nil "Hierarchy for %s,%s,%s ..." lib cell  
view ))
when( ddCVs = vscGetHierarchyDDs( ?lib lib ?cell cell ?view  
view

  ?inclibs inclibs )
vscPrint0(sprintf( nil "  %d cellviews." length(ddCVs) ))
vscCheckpoint( ddCVs ?message message)
); when ddCVs
); let
); procedure vscCheckpointHier


Notice all the comments placed on the closing brackets. Is there a  
way to make vim do this?


TIA

Re: WARNING! Don't update your local svn repository now!

[Bram Moolenaar]

Nicolas Weber wrote:

> > The directories structure of the Subversion repository has been
> > changed. Please use this command to checkout the latest sources:
> > 
> > svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
> > 
> > If you had checked out a copy of the sources before, please run this
> > command in your source root directory to switch into the current
> > branch:
> > 
> > svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1
> 
> Can someone update http://www.vim.org/subversion.php to reflect these
> changes?

I was still discussing what should actually be there, and making sure
that SVN contains that.

In my opinion "vim7" should get you the latest stable version.  So far
that is 7.0.243, thus 7.0 with patches.  As soon as Vim 7.1 is out of
beta then "vim7" should get you Vim 7.1.

"vim7.1" should get you the latest version of Vim 7.1.  So far that is
the beta version.  After the release it will be the stable version, thus
the same as "vim7".

Still need to check that it actually works this way.

There might also be other ways to get one of these, but that is less
relevant.

In my opinion we should keep it easy for the downloader to select one of
the available versions.  The download page would only need one or two
alternatives.

I have never maintained a SVN repository, thus have no idea how
difficult or easy these things are!

-- 
In a world without walls and borders, who needs windows and gates?

 /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

Re: Vim and email quoting

[Timothy Knox]

Somewhere on Shadow Earth, at Fri, May 11, 2007 at 09:37:05PM +0200, Andy 
Wokula wrote:
> Timothy Knox schrieb:
> >I use vim to write my outgoing email, and for the most part, it rocks. 
> >Thanks to
> >all the folks who have written modules and provided tips that make it the 
> >best
> >thing for writing email since mailx .
> >
> >That said, there is one small annoyance I find: When replying to an email, 
> >I
> >like to intersperse the original email with my commentary. When I am on 
> >the last
> >line of a paragraph I wish to respond to, I hit "o" to open a new line. 
> >All well
> >and good, save that something recognises the leading "> " of the previous
> >paragraph, and adds one to my new line. Can somebody tell me how to make it
> >stop? ;-)
> >
> >Many thanks to you all. :-)
> 
> Add the following line to ~/.vim/after/ftplugin/mail.vim :
> 
>setlocal fo-=o
> 
> Create the path or file if it doesn't exist.

Thanks, Andy, and thanks to those who responded offlist, especially Alan Isaac,
whose aimail.vim is filled with neat stuff to plunder.

-- 
Timothy Knox  
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
-- Bjarne Stroustrup, creator of the C++ programming language

Re: Vim and email quoting

[Andy Wokula]

Timothy Knox schrieb:

I use vim to write my outgoing email, and for the most part, it rocks. Thanks to
all the folks who have written modules and provided tips that make it the best
thing for writing email since mailx .

That said, there is one small annoyance I find: When replying to an email, I
like to intersperse the original email with my commentary. When I am on the last
line of a paragraph I wish to respond to, I hit "o" to open a new line. All well
and good, save that something recognises the leading "> " of the previous
paragraph, and adds one to my new line. Can somebody tell me how to make it
stop? ;-)

Many thanks to you all. :-)


Add the following line to ~/.vim/after/ftplugin/mail.vim :

   setlocal fo-=o

Create the path or file if it doesn't exist.

--
Regards,
Andy

EOM

Vim and email quoting

[Timothy Knox]

I use vim to write my outgoing email, and for the most part, it rocks. Thanks to
all the folks who have written modules and provided tips that make it the best
thing for writing email since mailx .

That said, there is one small annoyance I find: When replying to an email, I
like to intersperse the original email with my commentary. When I am on the last
line of a paragraph I wish to respond to, I hit "o" to open a new line. All well
and good, save that something recognises the leading "> " of the previous
paragraph, and adds one to my new line. Can somebody tell me how to make it
stop? ;-)

Many thanks to you all. :-)

-- 
Timothy Knox  
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
-- Bjarne Stroustrup, creator of the C++ programming language

Re: WARNING! Don't update your local svn repository now!

[Nicolas Weber]

Hi,

> The directories structure of the Subversion repository has been
> changed. Please use this command to checkout the latest sources:
> 
> svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
> 
> If you had checked out a copy of the sources before, please run this
> command in your source root directory to switch into the current
> branch:
> 
> svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1

Can someone update http://www.vim.org/subversion.php to reflect these changes?

Thanks,
Nico
-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

rst syntax file: grid tables not handled

[Alan G Isaac]

The rst syntax file of 2006-04-19 does not recognize
the end of grid tables.  Is there an update that
fixes this?

Thank you,
Alan Isaac

Re: FC6 gvim version 7.0.235 question

[Sean Hubbell]

Thanks Tim. I'll check it out,

Sean

Tim Chase wrote:
  I am running gvim version 7.0.235 on FC6. I have a slight problem 
where everytime I open a gvim session, the gvim window is placed behind 
all of my terminals. Would anyone have an idea why this is happening and 
how I may correct it?



While I don't know enough about your setup to give exact answers,
I suspect this might be a window-manager issue.  I have Fluxbox
(my window manager here) set to control the Z-depth of various
windows so that some windows/apps always appear above or below
other apps.  I don't know if somehow you've toggled such an
option for either you gvim (a "bottom layer" setting) or for your
terminals (an "above normal layer" setting), but that's where I'd
start looking.  This might have even been changed accidentally in
one or the other by a keystroke you didn't know changed the
z-depth.  My "keys" file in Fluxbox allows me to map a keychord
to "raise" and "lower" the current window (currently Win+PgUp and
Win+PgDn).  You may have unknowingly hit such a keychord in your
window manager.

-tim





  



--
Sean Hubbell
dBSTM Product Manager / Technical Director
deciBel Research Inc.
(256) 489-6198 (Work)
(256) 426-8957 (Cell)

Re: FC6 gvim version 7.0.235 question

[Tim Chase]

>   I am running gvim version 7.0.235 on FC6. I have a slight problem 
> where everytime I open a gvim session, the gvim window is placed behind 
> all of my terminals. Would anyone have an idea why this is happening and 
> how I may correct it?

While I don't know enough about your setup to give exact answers,
I suspect this might be a window-manager issue.  I have Fluxbox
(my window manager here) set to control the Z-depth of various
windows so that some windows/apps always appear above or below
other apps.  I don't know if somehow you've toggled such an
option for either you gvim (a "bottom layer" setting) or for your
terminals (an "above normal layer" setting), but that's where I'd
start looking.  This might have even been changed accidentally in
one or the other by a keystroke you didn't know changed the
z-depth.  My "keys" file in Fluxbox allows me to map a keychord
to "raise" and "lower" the current window (currently Win+PgUp and
Win+PgDn).  You may have unknowingly hit such a keychord in your
window manager.

-tim

FC6 gvim version 7.0.235 question

[Sean Hubbell]

Hello,

 I am running gvim version 7.0.235 on FC6. I have a slight problem 
where everytime I open a gvim session, the gvim window is placed behind 
all of my terminals. Would anyone have an idea why this is happening and 
how I may correct it?


Thanks in advance,

Sean