I'm currently working on a tool that calls to Fossil.exe to do some
work. In regards to some commands that take a list of files on the
command line (like 'commit') I would like to support any number of files
without worrying about the length of the command line (maximum 8191
characters on Windows XP+). For calling Fossil from the command line by
hand, that is something unlikely to have to worry about -- but with a
GUI app around Fossil, it could lead to annoyances.
One trick is to use a [temp] file to store the list of strings and
specifying the path to this file by starting it with a special
character, usually a '@' as an indirection.
For example:
fossil commit -M "C:\temp\commit_msg.txt" "@C:\temp\tmp_file_list.txt"
Would have the commit message (via the already existing -M) come from
C:\temp\commit_msg.txt
and the list of files come from the file C:\temp\tmp_file_list.txt, with
each line representing an individual file.
What's the opinion of such a change?
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
