[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: commit-msg hook
From: |
Eli Zaretskii |
Subject: |
Re: commit-msg hook |
Date: |
Sat, 11 Apr 2015 18:17:59 +0300 |
> Date: Sat, 11 Apr 2015 18:13:31 +0300
> From: Dmitry Gutov <address@hidden>
> CC: address@hidden, address@hidden
>
> > (We only need _some_ Emacs, not the latest one.)
>
> The one that would be in PATH is the master build, but if it breaks, I'd
> still like to be able to commit... I think.
How is this different from a broken Gawk?
> Overall, I think porting the whole commit-msg script from awk (scary!)
> to Elisp would be nice, but it will create this new complication.
I'm not sure the complication is new. I think we can rely on Emacs
being available no less than we rely on Gawk and Perl nowadays.
> At the very least, it will involve a new configuration step, to somehow
> tell Git which Emacs build to use.
I think we could just rely on its being on PATH. All we need is Emacs
23.1 or later.
- commit-msg hook, Eli Zaretskii, 2015/04/10
- Re: commit-msg hook, Johan Bockgård, 2015/04/10
- Re: commit-msg hook, Paul Eggert, 2015/04/10
- Re: commit-msg hook, Eli Zaretskii, 2015/04/11
- Re: commit-msg hook, Eli Zaretskii, 2015/04/11
- Re: commit-msg hook, Eli Zaretskii, 2015/04/11
- Re: commit-msg hook, Dmitry Gutov, 2015/04/11
- Re: commit-msg hook, Eli Zaretskii, 2015/04/11
- Re: commit-msg hook, Dmitry Gutov, 2015/04/11
- Re: commit-msg hook,
Eli Zaretskii <=
- Re: commit-msg hook, Stefan Monnier, 2015/04/11
- Re: commit-msg hook, chad, 2015/04/12
- Re: commit-msg hook, Paul Eggert, 2015/04/11
- Re: commit-msg hook, Eli Zaretskii, 2015/04/11
- Re: commit-msg hook, Paul Eggert, 2015/04/11
- Re: commit-msg hook, Eli Zaretskii, 2015/04/12
- Re: commit-msg hook, Eli Zaretskii, 2015/04/13
- Re: commit-msg hook, Paul Eggert, 2015/04/13
- Re: commit-msg hook, Eli Zaretskii, 2015/04/13
- Re: commit-msg hook, Paul Eggert, 2015/04/13