[darcs-devel] [issue1416] put log files in tempdir instead of in working dir

[Eric Kow]

Eric Kow <kowey at darcs.net> added the comment:

On 27 March 2014 at 19:25:50, Guillaume Hoffmann (guillaumh at gmail.com) wrote:
> >>
> >> Here is an excerpt from the help of hg commit:
> >>
> >> If no commit message is specified, Mercurial starts your
> >> configured editor where you can enter a message. In case your
> >> commit fails, you will find a backup of your message in
> >> ``.hg/last-message.txt``.
> >
> >
> > Sort of thing that should only happen after a failure
>
> Maybe. Mercurial leaves it there all the time. In fact, it first edits
> some random-named file in /tmp/ then copies it to
> .hg/last-message.txt.

OH, as for the file creation, no comment.
I was just thinking about the wall of text we might emit, my thinking
being that we should be fairly terse (while still trying to be
helpful) and not say stuff if it's just going to be ignored, or
confuse people

> > One motivation maybe is that temp files can build up over multiple
> > executions of darcs if the user does not delete them
>
> A point for overwriting a single file.
>
> (In fact I'm feeling currently more inclined towards that solution.)

Is that safe? For example, if I am running multiple darcsen
concurrently (due to absent-mindedness)…

On 27 March 2014 20:56, Guillaume Hoffmann <bugs at darcs.net> wrote:
>
> Guillaume Hoffmann <guillaumh at gmail.com> added the comment:
>
>>>
>>> Here is an excerpt from the help of hg commit:
>>>
>>>    If no commit message is specified, Mercurial starts your
>>>    configured editor where you can enter a message. In case your
>>>    commit fails, you will find a backup of your message in
>>>    ``.hg/last-message.txt``.
>>
>>
>> Sort of thing that should only happen after a failure
>
> Maybe. Mercurial leaves it there all the time. In fact, it first edits
> some random-named file in /tmp/ then copies it to
> .hg/last-message.txt.
>
> Git, on the other hand, directly edits (and always leaves) the file
> .git/COMMIT_EDITMSG .
>
>
>> Perhaps worthwhile to just try the simplest thing. If you want to bucket,
>> bucket with ISO dates, but simpler would be a good start
>
> Simpler is what we have, with increasing numbers :-)
>
> Even simpler is (like hg or git) overwriting the same file over and over,
>
>> One motivation maybe is that temp files can build up over multiple
>> executions of darcs if the user does not delete them
>
> A point for overwriting a single file.
>
> (In fact I'm feeling currently more inclined towards that solution.)
>
>>> Finally darcs9599-new_3c63... comes from another place (getting?
>>> pulling?) and should be investigated separately.
>>
>> This is where I see the most clutter
>
> I've created a new ticket for them: http://bugs.darcs.net/issue2362
>
> __________________________________
> Darcs bug tracker <bugs at darcs.net>
> <http://bugs.darcs.net/issue1416>
> __________________________________
> _______________________________________________
> darcs-devel mailing list
> darcs-devel at darcs.net
> http://lists.osuosl.org/mailman/listinfo/darcs-devel



-- 
Eric Kow <http://erickow.com>

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue1416>
__________________________________