On Sun, Mar 30, 2014 at 5:50 PM, Paulus Tuerah <[email protected]> wrote:
> Thanks Stephan! It works perfectly! :) > BTW: --args FILENAME works for all commands. It gets intercepted in the very earliest steps of application startup. Right now I'm still testing my GUI. > And I found out that: > fossil gdiff --from "version1" --to "version2" "path/file.txt" > The filename is screwed up, instead of "file.txt" the filename is random > text, i.e: "N2RzE1tMFYWZK31" for version1 and "jcs3c2edtTUDs1g" for > version2. > After playing around a bit with it, i see what you mean. The random names are there for your protection, but yes, they are pretty useless for purposes of seeing the filename in the gdiff titlebar. i don't have a solution/workaround. Maybe someone else can propose one. > Also I found out strange thing for renaming a file: > fossil rename "file-a.txt" "file-b.txt" > The timeline only mention that file-a.txt is deleted, and about file-b.txt > is not mentioned: > DELETED file-a.txt > The timeline will show a rename: http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/timeline?n=20&c=2014-02-11+14:31:00&v Scroll down to the commit mat at 14:31 on 20130211 to see many examples. They also appear here: http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/info/e85b45eda2 (search for "name change") > Then the history of file-a.txt is gone: > fossil finfo --width 0 "file-a.txt" > => no history for file: file-a.txt > Because you've already made the commit and finfo with a filename works on the current checkout version. That file isn't in your checkout, so it's unknown. That's not very intuitive, but i don't currently see how fossil could reasonably behave otherwise. If I add a new file-a.txt that not related with the previous file-a.txt, if > I check the history: > fossil finfo --width 0 "file-a.txt" > => it will show all history of file-a.txt again > If I check history of file-b.txt, it is not going back to history > file-a.txt > finfo will stop the listing at the rename point, but the www UI shows a link to the original name. See the bottom of this for an example: http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/finfo?name=f-apps/f-sanity.c > The conclusion, renaming file is same like delete old.file, and add > new.file. > The history is not retained and linked between the old.file and new.file. > > Is true renaming in fossil is not implemented? > History and full rename info is retained. i think you're just confused by the finfo behaviour described above (which is arguable but would introduce ambiguities and irregularities in results if it behaved differently). > This Fossil GUI is made by Java, in theory should work on any system, but > I only test it in Windows. > And these are what implemented right now: > - new, clone, open > ...branch / merge is not implemented, because I never use it even in SVN. > Great! Post us a link and i'll try it on Linux. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
