another example is the *.tst (regression tests) files in clisp, which are actually lisp files.

clisp uses custom preprocessors for C, so it keeps the sources in *.d files which actually contain C code. ohloh identifies then as written in "d programming language". I suggest a custom per-project ... [More] map identifying which files are in which labguage, similar to the existing cvs uid map. e.g., I should be able to specify that *.l in clocc is actually lisp and *.d in clisp is actually C. [Less]

clocc CVS has just been fixed. could you please retry? thanks!

PS. the Ohloh forum post notifications have http urls, not https ones...

are you saying that if I clear cache and start with https, the problem will go away?

why does https://www.ohloh.net/projects/clisp refer to CLISP but https://www.ohloh.net/projects/libffcall does not refer to libffcall? instead I have to use much less intuitive https://www.ohloh.net/projects/14288.

when I browse ohloh.net in https, the links in the black bottom of the page (e.g., about, faq, forums &c) are still http, so when I click there, I have to switch to https manually, which is a nuisance.

many (minor) contributions are done via sending patches to maintainers who commit them into cvs (necessarily under the maintainer's name, not the contributor's name). It might make sense to analyze ... [More] the ChangeLog files where those contributions are recorded under the correct name. [Less]

clisp is claimed to be written mostly in shell script due to a bunch of configure scripts. there should be a way to eliminate generated files from the count; at least the generated configure files have "Generated by GNU Autoconf" on the 4th line.

http://www.ohloh.net/projects/11537/enlistments :pserver:anonymous:@clocc.cvs.sourceforge.net:/cvsroot/clocc clocc CVS Step 1 of 3: Downloading source code history (Failed) the repository is ... [More] correct, valid, and working. why is it reported as "failed"? [Less]