Closed vyzo closed 11 months ago
Name | Link |
---|---|
Latest commit | af443c8eb9bb513e24730a4b26cadce7c3096532 |
Latest deploy log | https://app.netlify.com/sites/elastic-ritchie-8f47f9/deploys/651ef3f3b05ea00008e5bebd |
Deploy Preview | https://deploy-preview-979--elastic-ritchie-8f47f9.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Could TAGS generation be part of the install process?
I think not, as the user may want vim tags.
Better let them generate on their own.
also minus some 30s from the build time!
Could we add a subcommand to gxtags
that generates generates tags for PWD
along with the system tags based on GERBIL_PREFIX
or GERBIL_HOME
?
Not necessarily now, but I think it would make it a bit easier to generate TAGS for a project.
It already supports that, you can -a
to append to an existing TAGS file and you can give it any list of directories as arguments.
This installs the sources as part of the installation script, with the structure mimicking the exact logical package structure. It also stops creating TAGS as they are now useless to install (they index the build source layout) and let's the user build them by themselves; this also saves some build time.
Closes #965