Re: [A-A-P-develop] Bug in :copy; question about bug tracker
Brought to you by:
vimboss
From: Bram M. <Br...@mo...> - 2003-10-05 11:30:02
|
Cory Dodt wrote: > I'm using version 1.032 on Debian 3.0. With the following short recipe > I get the traceback below. > ____________________________________________ > all: > temp=/tmp/orig > other=/tmp/other > :mkdir {f} $(temp) $(temp)/x $(other) > :pushdir $(temp) > :copy {r} . $(other) > > :print Copied successfully. > ____________________________________________ [...] > line 581, in remote_copy_move > if fscheme != '': > UnboundLocalError: local variable 'fscheme' referenced before assignment > > error: Aborted > ____________________________________________________ > > A trivial patch to fix this is to add > fscheme='' > to the top of remote_copy_move in CopyMove.py. That's one way. I think a better way is not to call remote_copy_move() recursively for an empty directory. See the patch below. > Now my question about the bug tracker. A couple of months ago I used the > bug tracker here: > http://sourceforge.net/tracker/?group_id=46523&atid=446418 . The lonely > bug presently there is mine. I'm not one to complain about the length of > time it takes to fix bugs; if it takes a long time to fix then it takes a > long time to fix. The fact that there are no other bugs in the tracker > and my bug hasn't received any responses yet leads me to believe that > nobody even looks there, and that this list is the best place to report > bugs. > > If that is indeed the case, and nobody uses the tracker, I suggest > disabling it on SourceForge so future bugs don't get lost there. :-) > FWIW, I'm on the Twisted dev team and we've been pretty happy with Roundup > for bug tracking. I can certainly understand if nobody likes the sf > tracker. :-P Well, the intention was to use the bug tracker on Sourceforge, since it has advantages. Such as that everybody can see the bugs and fix them. In practice most things are done through the maillist. I also have the todo list on the web site, that confuses the situation even more: http://www.a-a-p.org/aaptodo.html I don't see an obvious choice for how to avoid the confusion. *** CopyMove.py~ Thu Aug 21 15:02:57 2003 --- CopyMove.py Sun Oct 5 13:01:41 2003 *************** *** 416,433 **** from Commands import dir_contents flist = map(lambda x: {"name": x}, dir_contents(fpath)) ! # Remove the "keepdir" attribute, the directory name is ! # already in "destpath" now. ! if optiondict.has_key("keepdir"): ! opt = optiondict.copy() ! del opt["keepdir"] ! else: ! opt = optiondict ! f = remote_copy_move(rpstack, recdict, copy, flist, ! {"name": destpath}, opt, 0, errmsg) ! if f: ! failed.extend(f) elif not copy or optiondict.get("preserve"): shutil.copy2(fpath, destpath) else: --- 416,434 ---- from Commands import dir_contents flist = map(lambda x: {"name": x}, dir_contents(fpath)) ! if flist: ! # Remove the "keepdir" attribute, the directory ! # name is already in "destpath" now. ! if optiondict.has_key("keepdir"): ! opt = optiondict.copy() ! del opt["keepdir"] ! else: ! opt = optiondict ! f = remote_copy_move(rpstack, recdict, copy, flist, ! {"name": destpath}, opt, 0, errmsg) ! if f: ! failed.extend(f) elif not copy or optiondict.get("preserve"): shutil.copy2(fpath, destpath) else: -- From "know your smileys": 2B|^2B Message from Shakespeare /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// |