emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: export to latex, make-backup-files, vc-make-backup-files
Date: Fri, 21 Jun 2019 13:22:48 -0400	[thread overview]
Message-ID: <87sgs2q2dz.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 8736k3ktwt.fsf@mat.ucm.es

Uwe Brauer <oub@mat.ucm.es> writes:

> Hi 
>
> The following kills me.
>
> I have set
>
> make-backup-files t, 
> vc-make-backup-files nil
>
> I am in a directory which is under version control (mercurial).
>
> The file test.org and test.tex are *both* under VC control.
>
> However when I export test.org to test.tex say twice
> the files 
>
> test.tex
> and 
>
> test.tex.~1~
>
> are generated and if I export once again I will have another backup
> file.
>
> ...
>
> But it does not help
>
> Is this a bug?
>

FWIW, I tried a set-up with git (I don't have mercurial available) and I cannot
reproduce this.

I'm not using numbered backups but the two variables you mention are set the
same way for me. Here's what I did:

- created a directory "foo" and cd'ed to it.
- `git init'
- create "test.org" and export to create "test.tex".
- `git add test.org test.tex'
- `git status' to check that everything looks good.
- modify test.org and export a few times.
- at every export, do `ls -la'. I always get this:

,----
| $ ls -la
| total 12
| drwxrwxr-x.  4 nick nick   62 Jun 21 13:04 .
| drwxrwxr-x. 14 nick nick 4096 Jun 21 13:03 ..
| drwxrwxr-x.  2 nick nick   21 Jun 21 13:04 auto
| drwxrwxr-x.  7 nick nick  132 Jun 21 13:04 .git
| -rw-rw-r--.  1 nick nick   67 Jun 21 13:04 test.org
| -rw-rw-r--.  1 nick nick  788 Jun 21 13:04 test.tex
`----

with no trace of backups.

Maybe try with git and see if you can reproduce the problem?
If not, I'd suspect either that the tex file is not under VC
or there is some incompatibility between mercurial and the
emacs vc package.

Also, there are two ways to make a backup (renaming and copying -
I use copying) and maybe the method you use is incompatible with
mercurial. Maybe you can try the other method: check the setting
of `make-backup-by-copying'.

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

  parent reply	other threads:[~2019-06-21 17:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 12:24 export to latex, make-backup-files, vc-make-backup-files Uwe Brauer
2019-06-21 14:54 ` Fraga, Eric
2019-06-21 15:22   ` Uwe Brauer
2019-06-21 16:23     ` Fraga, Eric
2019-06-21 17:22 ` Nick Dokos [this message]
2019-06-22 10:50   ` Uwe Brauer
2019-06-22 14:07   ` Uwe Brauer
2019-06-24 13:10     ` Nick Dokos
2019-06-24 16:53       ` Uwe Brauer
2019-06-22 14:15   ` [[Kludge]] (was: export to latex, make-backup-files, vc-make-backup-files) Uwe Brauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgs2q2dz.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).