cvscommand.vim : CVS integration plugin

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

cvscommand.vim : CVS integration plugin

Srinivas Rao. M
Hi,
Does any body have tried the latest version of "cvscommand.vim : CVS
integration plugin" version 1.69 ?. found at:

http://vim.sourceforge.net/scripts/script.php?script_id=90

The older version(1.68) seems to work properly for me except for ^M
characters coming into cvsvimdiff 's scratch buffer.

Has anyone tried any other scripts for integrating CVS commands with VIM
?
Thanks,
Srini...
--
website: http://www.geocities.com/saksblr
egroups: http://in.groups.yahoo.com/group/saksblr
--
RESPONSIBILITY starts with the willingness to experience yourself as
cause in the matter.
--


Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

Bob Hiestand
It was brought to my attention this morning that 1.69 requires a
recent VIM (6.2+) to work due to usage of try/finally.

Did you have any other issues with 1.69?

On 11/10/05, Srinivas Rao. M <[hidden email]> wrote:

> Hi,
> Does any body have tried the latest version of "cvscommand.vim : CVS
> integration plugin" version 1.69 ?. found at:
>
> http://vim.sourceforge.net/scripts/script.php?script_id=90
>
> The older version(1.68) seems to work properly for me except for ^M
> characters coming into cvsvimdiff 's scratch buffer.
>
> Has anyone tried any other scripts for integrating CVS commands with VIM
> ?
> Thanks,
> Srini...
> --
> website: http://www.geocities.com/saksblr
> egroups: http://in.groups.yahoo.com/group/saksblr
> --
> RESPONSIBILITY starts with the willingness to experience yourself as
> cause in the matter.
> --
>
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

A.J.Mechelynck
In reply to this post by Srinivas Rao. M
Srinivas Rao. M wrote:

> Hi,
> Does any body have tried the latest version of "cvscommand.vim : CVS
> integration plugin" version 1.69 ?. found at:
>
> http://vim.sourceforge.net/scripts/script.php?script_id=90
>
> The older version(1.68) seems to work properly for me except for ^M
> characters coming into cvsvimdiff 's scratch buffer.
>
> Has anyone tried any other scripts for integrating CVS commands with VIM
> ?
> Thanks,
> Srini...
> --
> website: http://www.geocities.com/saksblr
> egroups: http://in.groups.yahoo.com/group/saksblr
> --
> RESPONSIBILITY starts with the willingness to experience yourself as
> cause in the matter.
> --

^M bytes are usually due to mixed or misunderstood line endings. Unix
files usually have their lines terminated by a line feed (^J), Mac files
by a carriage return (^M), Dos files by both (^M^J).

If you try to read a Dos file on a Unix system, and 'fileformats' is
empty or set to "unix", every line will have a spurious ^M at the end.
In that case you should set 'fileformats' to "dos,unix" to recognise
this condition.

If you try to read a corrupt file, some of whose lines have Dos line
endings and others (especially at the beginning) Unix ones, you may find
yourself seeing ^M characters at the end of some lines but not all. If
you can nevertheless make Vim read that file in Dos format, it should be
OK (in Dos format, Vim accepts either CRLF or LF alone as an end-of-line
when reading but always writes CRLF when writing).

To eliminate carriage-returns (Ctrl-M bytes) at end of lines:

Method I
========
1. :set fileformats=
2. :e ++ff=dos filename
3. :w ++ff=unix filename
4. :e ++ff=dos filename

If some spurious ^M bytes are still present, either repeat steps 3 and
4, or change to Method II, which ought to always work.


Method II
=========
        :1,$s/\r*$//

This replaces zero or more carriage returns (as many as possible) by
nothing at end-of-line.

See
        :help 'fileformats'
        :help ++opt
        :help :s
        :help pattern-overview

HTH,
Tony.

Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

Vincent Wang-2
In reply to this post by Srinivas Rao. M

Srinivas Rao. M wrote:

>Has anyone tried any other scripts for integrating CVS commands with VIM
>?
>
>  
>
You can try cvsmenu.vim, it will help you if you prefer mouse clicking
than keyboard typing ;)


Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

adah
In reply to this post by Srinivas Rao. M
> Hi,
> Does any body have tried the latest version of "cvscommand.vim : CVS
> integration plugin" version 1.69 ?. found at:
>
> http://vim.sourceforge.net/scripts/script.php?script_id=90
>
> The older version(1.68) seems to work properly for me except for ^M
> characters coming into cvsvimdiff 's scratch buffer.
>
> Has anyone tried any other scripts for integrating CVS commands with
> VIM?

I would recommend cvsmenu.vim, of course:

http://vim.sourceforge.net/scripts/script.php?script_id=1245

Yes, its rating and download number are not very high.  However, you can
verify the precedent of this script (not maintained between 2002 and
2005) is rated and downloaded in the second place for cvs-related
scripts.  Not a bad result for a script not maintained for three years.
And after that I have made 37 CVS commits for this script.

Personally I feel menus and shortcuts make higher productivity.

Best regards,

Yongwei
Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

Srinivas Rao. M
In reply to this post by Bob Hiestand
Thanks all for the response. Please read below my response.


On Thu, 2005-11-10 at 21:51, Bob Hiestand wrote:
> It was brought to my attention this morning that 1.69 requires a
> recent VIM (6.2+) to work due to usage of try/finally.
>
> Did you have any other issues with 1.69?

Yeah, actually this issue was there in previous version also. Whenever i
do cvsvimdiff, the righhandside scratch buffer shows full of ^M
characters for each carriage return. As  Mechelynck, mentioned in the
earlier post, It is nothing to do with my file format. Everything is in
the same file format as they were created in CVS. Then also i am seeing
this issue.

Secondly there "Scroll binding" is not working in cvsvimdiff in 1.69
version. When you give cvsvimdiff, both the buffers are un-bound to each
other.

regards,
Srini...


> > --
> > website: http://www.geocities.com/saksblr
> > egroups: http://in.groups.yahoo.com/group/saksblr
> > --
> > RESPONSIBILITY starts with the willingness to experience yourself as
> > cause in the matter.

--
website: http://www.geocities.com/saksblr
egroups: http://in.groups.yahoo.com/group/saksblr
--
RESPONSIBILITY starts with the willingness to experience yourself as
cause in the matter.
--


Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

Bob Hiestand
In reply to this post by adah
On 11/11/05, [hidden email] <[hidden email]> wrote:

> > Hi,
> > Does any body have tried the latest version of "cvscommand.vim : CVS
> > integration plugin" version 1.69 ?. found at:
> >
> > http://vim.sourceforge.net/scripts/script.php?script_id=90
> >
> > The older version(1.68) seems to work properly for me except for ^M
> > characters coming into cvsvimdiff 's scratch buffer.
> >
> > Has anyone tried any other scripts for integrating CVS commands with
> > VIM?
>
> I would recommend cvsmenu.vim, of course:
>
> http://vim.sourceforge.net/scripts/script.php?script_id=1245
>
> Yes, its rating and download number are not very high.  However, you can
> verify the precedent of this script (not maintained between 2002 and
> 2005) is rated and downloaded in the second place for cvs-related
> scripts.  Not a bad result for a script not maintained for three years.
> And after that I have made 37 CVS commits for this script.
>
> Personally I feel menus and shortcuts make higher productivity.

... and I, of course, feel that keyboard shortcuts have always been
the most productive method.
Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

Bob Hiestand
In reply to this post by Srinivas Rao. M
On 11/11/05, Srinivas Rao. M <[hidden email]> wrote:

> Thanks all for the response. Please read below my response.
>
>
> On Thu, 2005-11-10 at 21:51, Bob Hiestand wrote:
> > It was brought to my attention this morning that 1.69 requires a
> > recent VIM (6.2+) to work due to usage of try/finally.
> >
> > Did you have any other issues with 1.69?
>
> Yeah, actually this issue was there in previous version also. Whenever i
> do cvsvimdiff, the righhandside scratch buffer shows full of ^M
> characters for each carriage return. As  Mechelynck, mentioned in the
> earlier post, It is nothing to do with my file format. Everything is in
> the same file format as they were created in CVS. Then also i am seeing
> this issue.
>
> Secondly there "Scroll binding" is not working in cvsvimdiff in 1.69
> version. When you give cvsvimdiff, both the buffers are un-bound to each
> other.

Please send me a list of all your settings, including platform
information, and I'll try to replicate it.  Scrollbind is working fine
for me.

Thank you,

Bob
Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

adah
In reply to this post by Srinivas Rao. M
Bob Hiestand wrote:

>> I would recommend cvsmenu.vim, of course:
>>
>> http://vim.sourceforge.net/scripts/script.php?script_id=1245
>>
>> Yes, its rating and download number are not very high.  However, you
>> can verify the precedent of this script (not maintained between 2002
>> and 2005) is rated and downloaded in the second place for cvs-related
>> scripts.  Not a bad result for a script not maintained for three
>> years.  And after that I have made 37 CVS commits for this script.
>>
>> Personally I feel menus and shortcuts make higher productivity.
>
> ... and I, of course, feel that keyboard shortcuts have always been
> the most productive method.

Maybe I misunderstood something, but I think cvscommand uses `commands'
instead of `shortcuts'.

E.g., what do you type to add a file to CVS?  In cvsmenu, one needs two
mouse clicks (_C_VS and then _A_dd), or three key-ins (`<alt-c>a' with
the menu shortcut, or the always usable `,ca' when the menu is
unavailable).  It is easy to learn and remember, and one need not
consult any documentation once the relationship between menus and
shortcuts are known.  That's why I think it is productive.

I do not advocate it because I am maintaining it.  No, I maintain it
because I find it useful and like it.  I hope more people will find its
usefulness.

Best regards,

Yongwei
Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

Bob Hiestand
On 11/14/05, [hidden email] <[hidden email]> wrote:

> Bob Hiestand wrote:
>
> >> I would recommend cvsmenu.vim, of course:
> >>
> >> http://vim.sourceforge.net/scripts/script.php?script_id=1245
> >>
> >> Yes, its rating and download number are not very high.  However, you
> >> can verify the precedent of this script (not maintained between 2002
> >> and 2005) is rated and downloaded in the second place for cvs-related
> >> scripts.  Not a bad result for a script not maintained for three
> >> years.  And after that I have made 37 CVS commits for this script.
> >>
> >> Personally I feel menus and shortcuts make higher productivity.
> >
> > ... and I, of course, feel that keyboard shortcuts have always been
> > the most productive method.
>
> Maybe I misunderstood something, but I think cvscommand uses `commands'
> instead of `shortcuts'.
>
> E.g., what do you type to add a file to CVS?  In cvsmenu, one needs two
> mouse clicks (_C_VS and then _A_dd), or three key-ins (`<alt-c>a' with
> the menu shortcut, or the always usable `,ca' when the menu is
> unavailable).  It is easy to learn and remember, and one need not
> consult any documentation once the relationship between menus and
> shortcuts are known.  That's why I think it is productive.

Adding a file in cvscommand has always been accomplished  through the
<mapleader>ca mapping.  All commands are available through such
mappings, as that is the intended usage.  The only commands which need
to be entered as colon commands are CVSReview, CVSVimDiff, and CVSLog,
and only then when entering specific version information (those
commands can be invoked for the common case directly with keyboard
mappings).

> I do not advocate it because I am maintaining it.  No, I maintain it
> because I find it useful and like it.  I hope more people will find its
> usefulness.

That's fine; however, I wish to prevent the spread of misinformation
about my own plugin.

Thank you,

Bob
Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

adah
In reply to this post by Srinivas Rao. M
Bob Hiestand wrote:

>>>> I would recommend cvsmenu.vim, of course:
>>>>
>>>> http://vim.sourceforge.net/scripts/script.php?script_id=1245
>>>>
>>>> Yes, its rating and download number are not very high.  However,
>>>> you can verify the precedent of this script (not maintained between
>>>> 2002 and 2005) is rated and downloaded in the second place for
>>>> cvs-related scripts.  Not a bad result for a script not maintained
>>>> for three years.  And after that I have made 37 CVS commits for
>>>> this script.
>>>>
>>>> Personally I feel menus and shortcuts make higher productivity.
>>>
>>> ... and I, of course, feel that keyboard shortcuts have always been
>>> the most productive method.
>>
>> Maybe I misunderstood something, but I think cvscommand uses
>> `commands' instead of `shortcuts'.
>>
>> E.g., what do you type to add a file to CVS?  In cvsmenu, one needs
>> two mouse clicks (_C_VS and then _A_dd), or three key-ins (`<alt-c>a'
>> with the menu shortcut, or the always usable `,ca' when the menu is
>> unavailable).  It is easy to learn and remember, and one need not
>> consult any documentation once the relationship between menus and
>> shortcuts are known.  That's why I think it is productive.
>
> Adding a file in cvscommand has always been accomplished  through the
> <mapleader>ca mapping.  All commands are available through such
> mappings, as that is the intended usage.  The only commands which need
> to be entered as colon commands are CVSReview, CVSVimDiff, and CVSLog,

May I ask I why special about these commands?  I do not know what
CVSReview does, but I do `cvs diff' with `,cd' (vertically split window
style), and `cvs log' with `,cl' (horizontally split new window).

> and only then when entering specific version information (those
> commands can be invoked for the common case directly with keyboard
> mappings).

[snipped]

Best regards,

Yongwei
Reply | Threaded
Open this post in threaded view
|

[OT] [cvs] menus and commands

Suresh Govindachar`
In reply to this post by Bob Hiestand
Hello,

  A recent thread has the exchange:

  MENU> Personally I feel menus and shortcuts make higher
  MENU> productivity.
  CMD>
  CMD>  ... and I, of course, feel that keyboard shortcuts
  CMD>  have always been the most productive method.

  My 2 cents is on: http://www.govindachar.com/eui/index.html

  --Suresh

Reply | Threaded
Open this post in threaded view
|

Re: cvscommand.vim : CVS integration plugin

adah
In reply to this post by Srinivas Rao. M
Bob Hiestand wrote:
> Adding a file in cvscommand has always been accomplished  through the
> <mapleader>ca mapping.  All commands are available through such
> mappings, as that is the intended usage.  The only commands which need
> to be entered as colon commands are CVSReview, CVSVimDiff, and CVSLog,
> and only then when entering specific version information (those
> commands can be invoked for the common case directly with keyboard
> mappings).

Really sorry for the foolish question this morning.  I should have read
more carefully.

Cvsmenu did it in a different way.  There are different menus (and thus
different shortcuts) for operations with and without revisions.  I was
stuck with this mind set.

Best regards,

Yongwei