Great, then it seems like the easiest choice. My last concern is if
appending to a file using ">>" is portable enough on all platforms. I'll
make some experiments and let you know if I get some resuilts.
I made a ticket:
http://www.fossil-scm.org/fossil/tktview/09b0f742287f3e97b42ab14764ae3a6b7d6c
On Wed, Jan 23, 2013 at 9:06 AM, Petr P wrote:
>
> Is fossil_system() safe to use for invoking another instance of "fossil"?
> Is this idea used already in some command?
>
The fossil_system() function was created for the purpose of running
instances of fossil recursively and to do so correctly a
2013/1/23 Richard Hipp
>
>
> On Wed, Jan 23, 2013 at 5:56 AM, Petr P wrote:
>
>> Hi, when commiting with fossil, I miss git's "git commit -v" feature that
>> appends the diff of changes being commited to the file where I edit a
>> commit message. This way, I can see what exactly I'm commiting wh
On Wed, Jan 23, 2013 at 5:56 AM, Petr P wrote:
> Hi, when commiting with fossil, I miss git's "git commit -v" feature that
> appends the diff of changes being commited to the file where I edit a
> commit message. This way, I can see what exactly I'm commiting when typing
> the message. It saved m
Hi, when commiting with fossil, I miss git's "git commit -v" feature that
appends the diff of changes being commited to the file where I edit a
commit message. This way, I can see what exactly I'm commiting when typing
the message. It saved me from a wrong commit a few times. Of course, I
could cal
5 matches
Mail list logo