Currently my repo has:

    darcs-amend-record-0
    darcs-amend-record-0.~1~
    darcs-amend-record-1
    darcs-amend-record-1.~1~
    darcs-amend-record-2
    darcs-amend-record-2.~1~
    darcs-record-0 darcs-temp-mail-0
    darcs-temp-mail-0.~1~
    darcs-temp-mail-0.~2~
    darcs-temp-mail-0.~3~
    darcs-temp-mail-1
    darcs-temp-mail-1.~1~
    darcs.cabal-darcs-backup0
    darcs9599-new_3c63f32f823ff92f99d802c48a9ddd0a
    darcs9603-new_fe335076796c541830bc54310d35cec7

So incidentally, I think that -darcs-backupN should instead be .~N+1~,
the standard GNU and CVS style for numbered backups.

I've copied msg7851 over from issue1416.  The particular point was that
files like
    darcs.cabal-darcs-backup0
    darcs.cabal-darcs-backup1
should really be called
    darcs.cabal-darcs-backup.~0~
    darcs.cabal-darcs-backup.~1~
and so forth...

It doesn't look like it could hurt to follow such a defacto convention.

According to http://www.gnu.org/software/emacs/manual/html_node/elisp/Numbered-
Backups.html

Files like
    darcs.cabal-darcs-backup0
    darcs.cabal-darcs-backup1
should really be called
    darcs.cabal.~1~
    darcs.cabal.~2~
and so forth...

On Thu, 23 Feb 2012 22:42:30 -0700, Michael Hendricks <bugs@darcs.net>  
wrote:

>
> Michael Hendricks <michael@ndrix.org> added the comment:
>
> According to 
> http://www.gnu.org/software/emacs/manual/html_node/elisp/Numbered-
> Backups.html
>
> Files like
> darcs.cabal-darcs-backup0
> darcs.cabal-darcs-backup1
> should really be called
> darcs.cabal.~1~
> darcs.cabal.~2~
> and so forth...

Why should darcs merge-conflict backups match the naming scheme of other  
projects?

This can cause confusion and conflicts between the tools.

-- 
Archi

Attachments

• unnamed

Archi wrote:
> Why should darcs merge-conflict backups match the naming scheme of
> other projects?

So existing tools will recognize they ARE backups, without having to
be told about Darcsisms.  Note foo.~1~ is the convention for GNU
coreutils as well as Emacs.  The simpler suffix ~ is also use for many
other GNU tools, e.g. tar, sed.

I've added this to http://wiki.darcs.net/Sprints/2012-03
Help finding nice items to work on from the ProbablyEasy pile would be 
welcome

The following patch sent by miguel.pagano+darcs@gmail.com updated issue issue1812 with
status=resolved;resolvedin=2.8.0 HEAD

* resolve issue1812: follow emacs convention for backup files 
Ignore-this: 984be9d50dd8d782a76a1acff2778ea9

The following patch sent by miguel.pagano+darcs@gmail.com updated issue issue1812 with
status=has-patch

* resolve issue1812: follow emacs convention for backup files 
Ignore-this: 984be9d50dd8d782a76a1acff2778ea9