> BTW: --args FILENAME works for all commands. It gets intercepted in the
> very earliest steps of application startup.
What do you mean by intercepted? Is it mean it override all the other
parameters?
I mean: fossil command -optiona -optionb --args filename
Means optiona and optionb is replaced?
For add, delete, revert, I've tried it and it works too, so everything is good
now :)
> try this as a workaround: fossil diff -tk --from ... --to ...
This is the output:
'tclsh' is not recognized as an internal or external command,
operable program or batch file.
This GUI I made don't use web at all.
What kind of protection is it in making random filename on gdiff?
I see, in the web ui the rename is working as expected.
But how can I get that information from the command line parameter?
fossil timeline only show the deleted file, not mention that it is renamed not
deleted.
I want to show the log all from my GUI, not using the fossil web ui at all.
My plan is the web ui is only for changing settings, wiki, ticket, bug tracker,
for the version control support everything is from my GUI.
Ok I'll post the link to try it out later after I do more tests.
Thanks,
-Paul
On Sunday, March 30, 2014 11:42 PM, Paulus Tuerah <[email protected]> wrote:
This is the main form.
>http://goldenstudios.no-ip.biz/user%20upload/fossilmain.JPG
>
>
>
>So far all features I need is completed.
>Starting to test with actual project.
>
>
>Regards,
>-Paul
>
>On Sunday, March 30, 2014 10:50 PM, Paulus Tuerah <[email protected]> wrote:
>
>Thanks Stephan!It works perfectly! :)
>>
>>
>>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.
>>
>>
>>If without version, the filename is correct:
>> fossil gdiff "path/file.txt"
>>
>>"file.txt~0" for baseline version and "file.txt" for working copy version.
>>
>>
>>Is this bugs, or is there a way to specify the filename?
>>
>>
>>
>>
>>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
>>
>>Then the history of file-a.txt is gone:
>>
>> fossil finfo --width 0 "file-a.txt"
>> => no history for file: file-a.txt
>>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
>>
>>
>>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?
>>
>>
>>
>>
>>Will do more tests later, if everything works as expected maybe I will
>>publish it if someone interested in using GUI.
>>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
>>- commit (add, delete, revert, rename, diff, push)
>>
>>- update (diff, pull)
>>- timeline / finfo
>>- undo / redo
>>- web ui
>>- annotate / blame
>>- rebuild
>>
>>
>>branch / merge is not implemented, because I never use it even in SVN.
>>
>>
>>Regards,
>>-Paul
>>
>>On Sunday, March 30, 2014 3:07 PM, Stephan Beal <[email protected]> wrote:
>>
>>
>>>
>>>
>>>
>>>
>>>On Sun, Mar 30, 2014 at 6:05 AM, Paulus Tuerah <[email protected]> wrote:
>>>
>>>Hi all,
>>>>I'm new to Fossil, and I'm coming from SVN world (using TortoiseSVN).
>>>>
>>>
>>>
>>>Welcome aboart!
>>>
>>>I want to try DVCS, and after review some DVCS, I like the simplicity of
fossil, especially the one file executable and one file repository.
>>>>But what prevent me to use fossil is: there is no usable Fossil GUI similar
>>>>like TortoiseSVN.
>>>>
>>>
>>>
>>>We're still a long way from having such a thing. There is a library
>>>interface for fossil in development, but i would guess (as its main
>>>developer) that we're a year or so away from being able to fully support an
>>>application like Tortoise.
>>>
>>>
>>>
>>>The problem is if there are many files, the command is too long (fossil
>>>commit a.txt b.txt c.txt ......) and got error.
>>>>If I commit partially it's
okay, but of course I can't commit partially.
>>>>
>>>
>>>
>>>That's a limit of Windows, unfortunately - most platforms have very large
>>>limits for command arguments.
>>>
>>>
>>>
>>>
>>>So is it possible for fossil commit to have new option --commit-file
>>>files.txt, similar like --message-file msg.txt?
>>>>Then the command would be:
>>>>fossil commit --commit-file files.txt
>>>>
>>>>Also the same case with fossil add, delete, diff, gdiff, revert
>>>>
>>>
>>>
>>>You can do that already using a little known feature:
>>>
>>>
>>>fossil ... --args FILENAME
>>>
>>>
>>>each line represents one filename or --key VALUE pair for the arguments list.
>>>
>>>
>>>--
>>>
>>>----- 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
