all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: 17970@debbugs.gnu.org
Subject: bug#17970: log-edit creates unwanted ChangeLog buffers
Date: Wed, 09 Jul 2014 03:09:23 -0400	[thread overview]
Message-ID: <9u61j79ffg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <f6egxwtw5g.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 07 Jul 2014 22:35:39 -0400")

Glenn Morris wrote:

> C-x v v
[...]
>   -> Now there is an empty, unwanted "/tmp/foo/ChangeLog" buffer.

It looks like this has the same cause as http://debbugs.gnu.org/17884,
namely the fact that vc-next-action now calls log-edit with SETUP = t.
This runs log-edit-hook, which runs log-edit-insert-changelog, which
ends up running log-edit-changelog-entries, which visits the ChangeLog
files, even if they don't exist.

Perhaps log-edit-changelog-entries should not bother visiting
non-existent files. (Could it use invisible buffers?)





  reply	other threads:[~2014-07-09  7:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  2:35 bug#17970: log-edit creates unwanted ChangeLog buffers Glenn Morris
2014-07-09  7:09 ` Glenn Morris [this message]
2014-07-09 13:55   ` Eli Zaretskii
2014-07-09 15:41     ` Glenn Morris
2014-07-09 16:28       ` Eli Zaretskii
2014-07-09 16:39         ` Glenn Morris
2014-07-09 16:54           ` Eli Zaretskii
2014-07-09 20:17             ` Glenn Morris
2014-07-10  3:09     ` Stefan Monnier
2014-07-10 14:59       ` Eli Zaretskii
2014-07-10 16:45         ` Stefan Monnier
2014-07-10 16:54           ` Glenn Morris
2014-07-10 17:18             ` Stefan Monnier
2014-07-10 17:22               ` Eli Zaretskii
2014-07-10 17:46               ` Glenn Morris
2014-07-10 18:19                 ` Stefan Monnier
2014-07-09 18:54 ` Stefan Monnier
2014-07-09 20:19   ` Glenn Morris
2014-07-09 22:22     ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=9u61j79ffg.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=17970@debbugs.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.