[RFC] Splitting VC interface for RCP to a distinct file.

[Daniel Pittman]

It seems to me, on consideration, that the VC integration of RCP could
very well be split out into a separate file from the main body of the
code, and automatically loaded if/when VC is.

This makes sense to me because, aside from anything else, it seems
awfully rude to (require 'vc) at the top of the file.

So, are there any objections[1] to my doing this? If not, I intend to do
it tomorrow evening at about this time...

Daniel

Footnotes: 
[1]  I have a patch that will be irritated by it counts...

-- 
Every man who knows how to read has it in his power to magnify himself, to
multiply the ways in which he exists, to make his life full, significant and
interesting.
-- Aldous Huxley

Re: [RFC] Splitting VC interface for RCP to a distinct file.

[Kai Großjohann]

Daniel Pittman [EMAIL PROTECTED] writes:

 It seems to me, on consideration, that the VC integration of RCP could
 very well be split out into a separate file from the main body of the
 code, and automatically loaded if/when VC is.

In principle, this is not a bad idea, but changes in this area are
afoot.  Hm.

Yes, let's separate the VC integration, and then we can have two
files, one for the old VC and one for the new VC.

Thanks, Daniel.

kai
-- 
I like BOTH kinds of music.