unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: ndame <emacsuser@freemail.hu>
To: "37223@debbugs.gnu.org" <37223@debbugs.gnu.org>,
	Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#37223: 26.2; vc does not honor backup-directory-alist
Date: Sat, 14 Sep 2019 19:20:25 +0000 (GMT)	[thread overview]
Message-ID: <Ax3GUg.mpdvm2HvOh7s.6anC4Cbf6L6bQWcdQriv@freemail.hu> (raw)
In-Reply-To: <630e610c-bc5e-b3be-22d7-d1a998f1e917@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

> 
> >
> > These are backup files, the vc function uses that name too
> > (vc-version-backup-file-name), so their placements should honor
> > backup-directory-alist which is currently ignored.
> 
> I don't know if they should. The current behavior is a long-standing
> one.  But more opinions are welcome.

The main problem is the user may not want these files at all.

I usually look at a particular version then close the buffer, I don't
want a file created and having such files polluting the directory. I
just want to see the contents.

I'd say more people use log to look up something in a certain version
than actually wanting to get a certain version on disk.

So there's two possible solutions:

1. Add an option to control if backup-directory-alist is honored by
these files and this can be off by default to keep current default
behavior.

2. Do not create files at all on disk, just read the selected
version's contents into a new buffer. The user can decide if he wants
to just look at the file and then close the buffer, or if he wants the
given version on disk then he can save the buffer.

The 2nd option seems better, since it gives control to the user to do
with the buffer as he wishes.

[-- Attachment #2: Type: text/html, Size: 1467 bytes --]

  reply	other threads:[~2019-09-14 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 19:55 bug#37223: 26.2; vc does not honor backup-directory-alist ndame
2019-09-14  0:40 ` Dmitry Gutov
2019-09-14 19:20   ` ndame [this message]
2019-09-19 20:22     ` Juri Linkov
2019-11-13 20:47       ` Juri Linkov

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=Ax3GUg.mpdvm2HvOh7s.6anC4Cbf6L6bQWcdQriv@freemail.hu \
    --to=emacsuser@freemail.hu \
    --cc=37223@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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.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).