-
Notifications
You must be signed in to change notification settings - Fork 26
templates – add default-skeleton keyword #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
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.
|
(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.
|
the last commits add possibility to rewrite file names (with the very same rules used in the files) |
|
@inaimathi Does your work obsolete this, or is it complementary? |
|
It's a conflicting change. Looks like this is an approach that keeps code-defined generators for the I'm not entirely clear on how this lets you have a file named |
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).