Re: [Orgmode] Re: *.bak files in trunk?

[Bernt Hansen]

Daniel Mahler <address@hidden> writes:

> On Tue, Jun 29, 2010 at 6:27 AM, Carsten Dominik
> <address@hidden> wrote:
>>
>> On Jun 29, 2010, at 2:45 AM, Bernt Hansen wrote:
>>
>>> Daniel Mahler <address@hidden> writes:
>>>
>>>> Is this normal?
>>>>
>>>> mahler:~/ELISP/org-mode-git$ git status
>>>> # On branch master
>>>> nothing to commit (working directory clean)
>>>> mahler:~/ELISP/org-mode-git$ find . -name "*.bak"
>>>> ./lisp/ChangeLog.bak
>>>> ./lisp/babel/langs/ob-C.el.bak
>>>
>>> ...
>>>>
>>>> ./lisp/org-capture.el.bak.bak.bak.bak
>>>> ./lisp/org-macs.elc.bak.bak.bak.bak
>>>> ./lisp/org-publish.elc.bak.bak.bak.bak
>>>
>>> You can see untracked files with
>>>
>>> $ git ls-files -o
>>>
>>> $ git ls-files '*.bak'
>>> returns nothing for me so there are no files ending in '.bak' in the
>>> repository as far as I can tell.
>>
>> The bigger problem seems to be that something is creating these files.
>> Bu I have no idea what, noting in Org-mode I would think,
>> must be some utility or stuff in Daniel's setup.
>
> That is the weird thing. The only thing I really
> do in the org directory is "git pull" and make.
> Also not tool I use makes *.bak directories,
> emacs creates *~.
> That, and the fact that git status/diff did not report them,
> made me thing they were from the repository.
> (I do not normally use git)
>

You might want to look at the dates those files were created to see if
you can get any extra information about who creates them.  They look to
me like broken editor backup files :) but that's just a guess.

The easiest way to get rid of them is to have git clean them out --
you need to tell it to clean out files and include ignored files which
is what the -x switch does.  Make sure you specify the '*.bak' pattern
otherwise it will clean out _everything_ that is not tracked which
includes all of your compiled files.

$ git clean -x '*.bak'

HTH,
Bernt