Skip to content

Conversation

@dkochmanski
Copy link
Contributor

I've noticed, that there is no way to get rid of the default skeleton
with files README.txt, {name}.asd, {name}.lisp and package.lisp.

This will be useful, because thanks to that user will be able to create his own custom templates from scratch (indirectly fixes #2).

Don't create the default skeleton, if the `default-skeleton` keyword is
NIL (by default to preserve a backward compatibility it is T).
If default-skeleton set to NIL causes skipping the creation of default
skeleton files.
@dkochmanski
Copy link
Contributor Author

dkochmanski commented Aug 27, 2016

(and it extracts default-skeleton implementation from the quickproject.lisp into default-template.lisp)

Other two variables have a full qualifier and start/end marker aren't
used more than one time.
This is necessary to be able to create templates with files named as a
system, for instance quux.asd . Quicklisp could have problems with
system.asd containing quux system.
@dkochmanski
Copy link
Contributor Author

the last commits add possibility to rewrite file names (with the very same rules used in the files)

@xach
Copy link
Owner

xach commented Dec 20, 2017

@inaimathi Does your work obsolete this, or is it complementary?

@inaimathi
Copy link
Contributor

It's a conflicting change. Looks like this is an approach that keeps code-defined generators for the README.txt, {project}.asd and {project}.lisp file. It looks like there are changes that let you override these with a template you can write.

I'm not entirely clear on how this lets you have a file named {project}.asd and {project}.lisp (short of fiddling with your template per generated project), and I'm not sure I like having the default templates defined in code using format (instead of the way users would have to define theirs), but it seems otherwise equivalent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow for user configurable templates.

3 participants