From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: trunk r115265: * lisp/vc/vc-dispatcher.el (vc-log-edit): Setup the Summary&Author headers.
Date: Fri, 29 Nov 2013 12:04:05 -0500 [thread overview]
Message-ID: <jwveh5zcfm3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5298AA77.4060009@yandex.ru> (Dmitry Gutov's message of "Fri, 29 Nov 2013 16:53:43 +0200")
>> The intention was to remind people that they should think about who's
>> the author. Indeed, it's particularly useful for us but less so for
>> many other projects.
> Isn't it too late to remind when the log-edit buffer is open? Normally, you
> create ChangeLog entries first (and they should include the right author),
> only then open the vc-dir buffer, mark the files and then see the
> log-edit buffer.
I think of this "reminding" as a process rather than a one-time event,
so I'm not too worried about it being "too late".
It's not perfect, but it's better than nothing, I think.
>> Maybe we can set it as a .dir-locals.el customization.
> It would be better, but since dir-locals overrides personal customizations,
> it wouldn't be ideal either, as far as I'm concerned.
Having an extra empty "Author:" field might hurt your aesthetic
sensibility, but I don't see how it could be really harmful, so I think
it's perfectly OK even if it's hard to override (and of course, it can
still be overridden, if you're sufficiently motivated).
>> The RFC822 format does add features, since there are a few other special
>> headers (Author, Fixes, Amend, maybe a few more).
> True. But is it relevant to the question of whether to include the Summary
> and Author headers by default?
What would you include, instead?
> Another problem with Summary, I believe, is that it's often unused in Emacs
> commit messages.
IIUC that's a problem in Emacs's commit messages, not in vc-log-edit,
and the presence of the "Summary:" header might actually encourage
people to change their habit.
>> We should also use some of the message-mode commands to move inside the
>> header, as was suggested here recently.
> Not sure which thread, or which commands you mean. But `C-e' works well
> enough for moving after "Summary:".
C-a could move to "right after the :".
>> Indeed, that needs to be fixed. It's easy to fix when we kill the
>> *vc-log* buffer, but it might be trickier to fix when you just
>> bury-it :(
> Since bury-buffer doesn't have a default binding in log-edit, I think that's
> not much of a problem. But we can follow Magit's (and message-mode's)
> example and create a command that would do the burying the smart way (and
> bind it to C-c C-k).
Sounds good.
>> Maybe log-edit-show-files shouldn't be in the default log-edit-hook.
> I'd rather we fix it than hide it.
OK.
> Another approach would be to instead of creating a separate buffer and
> window, output its text at the bottom of the log-edit buffer. And
> either make it a read-only-not-real text, or comment it out somehow
> and remove that section before the commit is made.
These could work as well, indeed.
Stefan
next prev parent reply other threads:[~2013-11-29 17:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1VlqjS-0006O3-Fn@vcs.savannah.gnu.org>
2013-11-29 4:39 ` trunk r115265: * lisp/vc/vc-dispatcher.el (vc-log-edit): Setup the Summary&Author headers Dmitry Gutov
2013-11-29 13:33 ` Stefan Monnier
2013-11-29 14:53 ` Dmitry Gutov
2013-11-29 17:04 ` Stefan Monnier [this message]
2013-11-29 22:37 ` Dmitry Gutov
2013-11-30 2:29 ` Stefan Monnier
2013-11-30 16:02 ` Dmitry Gutov
2013-12-01 21:10 ` Stefan Monnier
2013-12-02 2:40 ` Dmitry Gutov
2013-12-02 13:53 ` Stefan Monnier
2013-12-02 23:02 ` Dmitry Gutov
2013-12-03 0:56 ` Leo Liu
2013-12-03 3:06 ` Stefan Monnier
2013-12-04 0:38 ` Dmitry Gutov
2013-12-03 2:17 ` Dmitry Gutov
2013-12-03 3:09 ` Stefan Monnier
2013-12-04 0:43 ` Dmitry Gutov
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=jwveh5zcfm3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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.