* Re: ediff in RCS [not found] <mailman.2307.1182121306.32220.help-gnu-emacs@gnu.org> @ 2007-06-17 23:14 ` Hadron 2007-06-18 0:38 ` Drew Adams 0 siblings, 1 reply; 8+ messages in thread From: Hadron @ 2007-06-17 23:14 UTC (permalink / raw) To: help-gnu-emacs "Drew Adams" <drew.adams@oracle.com> writes: >> I have downloaded to my lisp path the following >> >> vc+.el vc-.el vc-ediff.el vc-hooks+.el >> >> (I can find no documentation on them or installation guides but ran >> across them from the emacs wiki) >> >> I have added >> >> (require 'vc-hooks+) >> >> to my init files. >> >> Now ediff (as opposed to diff) comes up from "C-x v =" (C-x v = runs the >> command vc-ediff) but other keys now dont work e.g >> >> ,---- >> | vc-register: Symbol's function definition is void: vc-admin >> | Symbol's function definition is void: vc-admin >> `---- >> >> Has anyone used this stuff? Is there a full "package" of all related >> files somewhere? It's like some giant jigsaw at the moment :-; > > This is my fault ;-). > > I wrote vc-.el, vc+.el, and vc-hooks+.el long, long ago. I doubt that they > work well or even work at all with recent Emacs versions. I leave the code > on the wiki in case it helps someone, but there are no guarantees associated > with it. Thanks for the prompt reply. Possibly a good idea to comment them as such? The copyright indicates 2007 so I assumed the code was maintained and working :( > > If I were you, I would try doing whatever you need to do without using those > libraries. If you cannot do what you need, and if you see something in those > libraries that looks like it might help, then you can try to adapt it for > use with recent Emacs versions. Again, no guarantees of anything. I'm not a lisp programmer. I did find this: http://xemacs.seanm.ca/lisp/vc-ediff.el ^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: ediff in RCS 2007-06-17 23:14 ` ediff in RCS Hadron @ 2007-06-18 0:38 ` Drew Adams 2007-06-18 9:00 ` Hadron 0 siblings, 1 reply; 8+ messages in thread From: Drew Adams @ 2007-06-18 0:38 UTC (permalink / raw) To: Hadron, help-gnu-emacs > Possibly a good idea to comment them as such? Yes, perhaps. But I have no idea that there are any problems (though your report might be related). I haven't used change control much since I started using Windows ;-). I just haven't felt like installing it. > The copyright indicates > 2007 so I assumed the code was maintained and working :( Bad assumption. Even a recent change-log entry (though there are none in these files) wouldn't necessarily mean that the library was working on that log date. The change could just be something as simple as updating the address of the FSF in the free-software declaration. Checking for a recent change-log entry and reading what it says can help, but again, there are no guarantees. Sorry for any inconvenience. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ediff in RCS 2007-06-18 0:38 ` Drew Adams @ 2007-06-18 9:00 ` Hadron 2007-06-18 20:10 ` Andreas Röhler 0 siblings, 1 reply; 8+ messages in thread From: Hadron @ 2007-06-18 9:00 UTC (permalink / raw) Cc: help-gnu-emacs, Hadron "Drew Adams" <drew.adams@oracle.com> writes: >> Possibly a good idea to comment them as such? > > Yes, perhaps. But I have no idea that there are any problems (though your > report might be related). I haven't used change control much since I started > using Windows ;-). I just haven't felt like installing it. > >> The copyright indicates >> 2007 so I assumed the code was maintained and working :( > > Bad assumption. Yup - I wasted a lot of time. Easy way to address it of course and take "assumption" out of the equation is to just add a "old and not maintained and unlikely to work" comment :-; > > Even a recent change-log entry (though there are none in these files) > wouldn't necessarily mean that the library was working on that log date. The > change could just be something as simple as updating the address of the FSF > in the free-software declaration. Checking for a recent change-log entry and > reading what it says can help, but again, there are no guarantees. > > Sorry for any inconvenience. > No worries - it was educational. -- ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ediff in RCS 2007-06-18 9:00 ` Hadron @ 2007-06-18 20:10 ` Andreas Röhler 2007-06-24 16:39 ` Tom Tromey 0 siblings, 1 reply; 8+ messages in thread From: Andreas Röhler @ 2007-06-18 20:10 UTC (permalink / raw) To: help-gnu-emacs Cc: Tom Tromey, Michael Olson, Richard Stallman, Stefan Monnier Am Montag, 18. Juni 2007 11:00 schrieb Hadron: > "Drew Adams" <drew.adams@oracle.com> writes: > >> Possibly a good idea to comment them as such? > > > > Yes, perhaps. But I have no idea that there are any problems (though your > > report might be related). I haven't used change control much since I > > started using Windows ;-). I just haven't felt like installing it. > > > >> The copyright indicates > >> 2007 so I assumed the code was maintained and working :( > > > > Bad assumption. > > Yup - I wasted a lot of time. > Hi Drew and all, as that kind of bugs happens with third-party-programs, not just with yours, much more often than with core-emacs-files: What about to have a joined repository for third-party-stuff in a VC-system. Maybe Git, SVN, whatever. Together with a joined discussion of bugs as it takes place with the core-files? The wiki is not bad, but not as suitable for developing as a VC-System - no checkout of versions etc. This pertains too for repositories as emacs-lisp-list, Tom Tromeys ELPA and probably other collections I ignore. The problem seems in so far serious, as core-emacs can't grow eternal bigger and bigger. Rather I conceive a future, were independent packages are loaded as needed into a quick and stable core. Today already you may run into serious trouble, if your work depends on third-party-stuff, which for some reasons is no longer or not properly maintained (the latter is more or less inevitable with one-person-acts, as we all are making errors every day). At the other side the vast amount of third-party-stuff is very important and part of the strength of Emacs itself. So far Andreas Roehler ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ediff in RCS 2007-06-18 20:10 ` Andreas Röhler @ 2007-06-24 16:39 ` Tom Tromey 0 siblings, 0 replies; 8+ messages in thread From: Tom Tromey @ 2007-06-24 16:39 UTC (permalink / raw) To: Andreas Röhler Cc: help-gnu-emacs, Michael Olson, Richard Stallman, Stefan Monnier >>>>> "Andreas" == Andreas Röhler <andreas.roehler@online.de> writes: Andreas> What about to have a joined repository for Andreas> third-party-stuff in a VC-system. Maybe Git, SVN, Andreas> whatever. Together with a joined discussion of bugs as Andreas> it takes place with the core-files? Andreas> This pertains too for repositories as emacs-lisp-list, Andreas> Tom Tromeys ELPA and probably other collections I Andreas> ignore. FWIW I wasn't planning to set up any sort of version control system for ELPA. I do want to move it to a hosting service like savannah eventually, so that other people can help maintain it. I don't have a firm plan for when this will happen, I suppose whenever ELPA seems "popular enough". Anyway, source control seems like a bit too much process for this, at least right now. Andreas> The problem seems in so far serious, as core-emacs can't Andreas> grow eternal bigger and bigger. Rather I conceive a Andreas> future, were independent packages are loaded as needed Andreas> into a quick and stable core. Andreas> Today already you may run into serious trouble, if your Andreas> work depends on third-party-stuff, which for some Andreas> reasons is no longer or not properly maintained (the Andreas> latter is more or less inevitable with one-person-acts, Andreas> as we all are making errors every day). Andreas> At the other side the vast amount of third-party-stuff Andreas> is very important and part of the strength Andreas> of Emacs itself. FWIW I don't mind having a maximal Emacs including everything -- I rather like it, actually. But at the same time Emacs has a very long and irregular release cycle, and some sub-packages may benefit from decoupling a bit. As for maintaining dependencies -- ELPA can only help with the mechanics of this. If a package becomes unmaintained, or forks into incompatible versions, that is not really something ELPA is intended to solve. There are other ways to solve this though: get code into Emacs, or have a way to hand off maintainership from one person to the next to ensure package integrity. Tom ^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <mailman.2312.1182127247.32220.help-gnu-emacs@gnu.org>]
* Re: ediff in RCS [not found] <mailman.2312.1182127247.32220.help-gnu-emacs@gnu.org> @ 2007-06-18 17:33 ` don provan 0 siblings, 0 replies; 8+ messages in thread From: don provan @ 2007-06-18 17:33 UTC (permalink / raw) To: help-gnu-emacs "Drew Adams" <drew.adams@oracle.com> writes: >> The copyright indicates >> 2007 so I assumed the code was maintained and working :( > > Bad assumption. Are you suggesting it's reasonable for the year to be updated in the copyright notice of code that has not been changed in years? -don ^ permalink raw reply [flat|nested] 8+ messages in thread
* ediff in RCS @ 2007-06-17 22:12 Hadron 2007-06-17 23:00 ` Drew Adams 0 siblings, 1 reply; 8+ messages in thread From: Hadron @ 2007-06-17 22:12 UTC (permalink / raw) To: help-gnu-emacs I have downloaded to my lisp path the following vc+.el vc-.el vc-ediff.el vc-hooks+.el (I can find no documentation on them or installation guides but ran across them from the emacs wiki) I have added (require 'vc-hooks+) to my init files. Now ediff (as opposed to diff) comes up from "C-x v =" (C-x v = runs the command vc-ediff) but other keys now dont work e.g ,---- | vc-register: Symbol's function definition is void: vc-admin | Symbol's function definition is void: vc-admin `---- Has anyone used this stuff? Is there a full "package" of all related files somewhere? It's like some giant jigsaw at the moment :-; Any help appreciated. ^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: ediff in RCS 2007-06-17 22:12 Hadron @ 2007-06-17 23:00 ` Drew Adams 0 siblings, 0 replies; 8+ messages in thread From: Drew Adams @ 2007-06-17 23:00 UTC (permalink / raw) To: Hadron, help-gnu-emacs > I have downloaded to my lisp path the following > > vc+.el vc-.el vc-ediff.el vc-hooks+.el > > (I can find no documentation on them or installation guides but ran > across them from the emacs wiki) > > I have added > > (require 'vc-hooks+) > > to my init files. > > Now ediff (as opposed to diff) comes up from "C-x v =" (C-x v = runs the > command vc-ediff) but other keys now dont work e.g > > ,---- > | vc-register: Symbol's function definition is void: vc-admin > | Symbol's function definition is void: vc-admin > `---- > > Has anyone used this stuff? Is there a full "package" of all related > files somewhere? It's like some giant jigsaw at the moment :-; This is my fault ;-). I wrote vc-.el, vc+.el, and vc-hooks+.el long, long ago. I doubt that they work well or even work at all with recent Emacs versions. I leave the code on the wiki in case it helps someone, but there are no guarantees associated with it. If I were you, I would try doing whatever you need to do without using those libraries. If you cannot do what you need, and if you see something in those libraries that looks like it might help, then you can try to adapt it for use with recent Emacs versions. Again, no guarantees of anything. ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2007-06-24 16:39 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <mailman.2307.1182121306.32220.help-gnu-emacs@gnu.org> 2007-06-17 23:14 ` ediff in RCS Hadron 2007-06-18 0:38 ` Drew Adams 2007-06-18 9:00 ` Hadron 2007-06-18 20:10 ` Andreas Röhler 2007-06-24 16:39 ` Tom Tromey [not found] <mailman.2312.1182127247.32220.help-gnu-emacs@gnu.org> 2007-06-18 17:33 ` don provan 2007-06-17 22:12 Hadron 2007-06-17 23:00 ` Drew Adams
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).