[asdf-devel] How about a tabs versus spaces policy for asdf?
Robert P. Goldman
rpgoldman at sift.info
Thu Dec 3 14:24:14 UTC 2009
Only .lisp and .asd sounds sufficient to me, but Gary wrote a lot of
shell scripts I haven't really looked at. I don't have a strong
opinion about the documentation source (perhaps surprisingly).
On Dec 2, 2009, at 20:54, Daniel Herring <dherring at tentpost.com> wrote:
> On Wed, 2 Dec 2009, Faré wrote:
>> 2009/12/2 Robert Goldman <rpgoldman at sift.info>:
>>> I should actually have been specific about something else:
>>> If we prefer spaces to tabs (and I will not attempt to stack my
>>> eloquence and vituperation against jwz's), we should probably
>>> stick the
>>> git-equivalent of a pre-commit-hook into the repo to refuse to
>>> accept tabs.
>>> Daniel --- is your git fu strong enough for this task?
> It could be. This would require putting the proper hooks/pre-commit
> file in a .git directory. Should it check all files in the project,
> or only lisp sources?
>> In either case, git-fu is nice. And if git-fu there be, can we also
>> eliminate trailing whitespace?
> See core.whitespace in the git-config manpage; by default git warns
> about trailing whitespace. Commands that apply patches (e.g. git-
> apply and git-am) have an option to control this; --whitespace=error
> or --whitespace=fix might be what you want. This choice can be made
> permanent by something like
> # git config apply.whitespace error
> Also look at the gitattributes manpage.
> - Daniel
> asdf-devel mailing list
> asdf-devel at common-lisp.net
More information about the asdf-devel