From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: VC commit missing ChangeLog message
Date: Tue, 11 Nov 2008 13:09:53 -0600 [thread overview]
Message-ID: <86r65ihyf2.fsf@lifelogs.com> (raw)
In-Reply-To: jwv7i7anovj.fsf-monnier+emacs@gnu.org
On Tue, 11 Nov 2008 12:41:13 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
>> I wonder if it could:
>> 1) always be called on opening the *VC-log* buffer, since it's harmless
SM> M-x customize-variable RET log-edit-hook RET
I know how to do it for myself, of course. I think it should be done
for everyone.
>> 2) give an informative message about why it didn't find a ChangeLog
>> entry, if it's invoked manually and it couldn't find an entry
SM> It's kind of difficult: currently, it builds a regexp and searches
SM> for it. If it's not found, all it knows is that it's not found, but not
SM> which part of the regexps could have matched if it weren't for some
SM> other part.
Maybe that can be improved. I have not looked at the code so I don't
want to speculate, but will do so if you and others think it's a good
idea.
Ted
prev parent reply other threads:[~2008-11-11 19:09 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
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 [this message]
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=86r65ihyf2.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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 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).