From: Dan Nicolaescu <dann@ics.uci.edu>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: VC commit missing ChangeLog message
Date: Tue, 11 Nov 2008 17:11:06 -0800 (PST) [thread overview]
Message-ID: <200811120111.mAC1B6h1005596@mothra.ics.uci.edu> (raw)
In-Reply-To: <86od0mgcz5.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 11 Nov 2008 15:38:22 -0600")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Tue, 11 Nov 2008 11:45:32 -0800 (PST) Dan Nicolaescu <dann@ics.uci.edu> wrote:
>
> DN> Ted Zlatanov <tzz@lifelogs.com> writes:
> >> On Tue, 11 Nov 2008 08:58:34 -0800 (PST) Dan Nicolaescu <dann@ics.uci.edu> wrote:
>
> DN> It could and it should, just nobody has done the work yet to do it...
> DN> If you are interested, it can be done `vc-checkin' by initializing the
> DN> `initial-contents' parameter before the call to `vc-start-log-entry'.
> >>
> >> Wouldn't it be easier to do it by calling the function directly?
>
> DN> Not sure what your question is... What I described is one way to
> DN> initialize the contents of the *VC-log* buffer.
>
> There's a function that will do it (`C-c C-a' ==
> log-edit-insert-changelog), I'm trying to find out if it's easier to
> always call that function when setting up the *VC-log* buffer than use
> initial-contents as you suggested. It seems so to me, and Stefan
> suggested it too.
Sorry, I don't know which version would be easier.
If you are interested in improving this area, please also look at one of
the TODO items in vc.el:
;; - When vc-next-action calls vc-checkin it could pre-fill the
;; *VC-log* buffer with some obvious items: the list of files that
;; were added, the list of files that were removed. If the diff is
;; available, maybe it could even call something like
;; `diff-add-change-log-entries-other-window' to create a detailed
;; skeleton for the log...
;;
> >> Or do you mean I can insert the commented lines I suggested as well
> >> that way?
>
> DN> If you add those comments, you'd need to add some post-processing to
> DN> make sure they get removed before checking in, so it might not be the
> DN> best idea.
>
> It's for user convenience, so I think it's a good idea. It's just
> modifying log-edit-done at the beginning--it already does removal of
> trailing empty lines, so this is pretty easy. Simply go to point-min
> and then remove all the lines that match "^;;;". I can write and test
> it unless you or someone else think it's a problem.
If you are going to add the ChangeLog entries by default, then why
bother with adding the text ?
IMO adding text is inconvenient to users: they either have to read it,
or they might think they have to delete it so that it does not get
checked in.
It would be nice to be able to insert text that is not part
of the buffer, like in the header line, but that is a single line
unfortunately :-(
next prev parent reply other threads:[~2008-11-12 1:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 14:41 VC commit missing ChangeLog message Ted Zlatanov
2008-11-11 14:49 ` Alfred M. Szmidt
2008-11-11 16:25 ` Stefan Monnier
2008-11-11 16:43 ` Ted Zlatanov
2008-11-11 16:58 ` Dan Nicolaescu
2008-11-11 19:11 ` Ted Zlatanov
2008-11-11 19:45 ` Dan Nicolaescu
2008-11-11 21:38 ` Ted Zlatanov
2008-11-12 1:11 ` Dan Nicolaescu [this message]
2008-11-12 17:17 ` Ted Zlatanov
2008-11-12 19:42 ` Stefan Monnier
2008-11-12 19:59 ` Dan Nicolaescu
2008-11-12 20:57 ` Stefan Monnier
2008-11-12 21:47 ` Ted Zlatanov
2008-11-13 1:56 ` Stefan Monnier
2008-11-12 19:56 ` Dan Nicolaescu
2008-11-12 21:42 ` Ted Zlatanov
2008-11-13 7:09 ` Dan Nicolaescu
2008-11-13 14:47 ` Ted Zlatanov
2008-11-13 15:12 ` Dan Nicolaescu
2008-11-12 2:38 ` Stefan Monnier
2008-11-11 17:41 ` Stefan Monnier
2008-11-11 19:09 ` Ted Zlatanov
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=200811120111.mAC1B6h1005596@mothra.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.com \
/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.