I am trying to --watch for changes from scss files from one directory that I am #importing in another directory.
Is there any way to do this?
The imported files are being changed in their respective directory but are not being updated because (I presume) sass is looking for changes only from the directory I am watching from?
Related
I have a directory full of markdown (.md) files I want to render into a website so I can see what it will look like. I installed Jekyll which I've used a number of times, cd'd into the directory and executed Jekyll serve.
Jekyll created the _site directory and instead of processing my .md files into .html files, it just copied them into the _site directory.
I'm at a bit of a loss as to why it's not processing the markdown. Anyone know why?
Jekyll only processes files with Front Matter.. otherwise, those files are designated as "static files" and simply copied verbatim to the destination directory.
How can I ignore the files inside the folder but keeping the folder in mercurial?
I tried in this way but also folder is ignored.
syntax: glob
photos/*.jpg
photos/*.gif
photos/thumbs/*.jpg
photos/thumbs/*.gif
Thanks
Create an empty file named .keep in the folder and add it to your repository.
touch photos/.keep
hg add photos/.keep
This way the folder will be still tracked, even if its contents and the folder itself are in .hgignore.
Can I change the directory Jekyll uses for it's temporary building?
I'm using Jekyll on a gh-pages branch and when I switch back to my Ember project on master, it puts new files in /tmp. This causes problems with Jekyll's build, and forces me to delete the dir each time I switch back to gh-pages.
Yes, you can.
You have a few ways of doing this, in your local folder, where _config.yml is located (Jekyll site root directory):
A. Editing _config.yml to have a destination for site generation:
In _config.yml, add the following:
destination: /tmp/jekyll_site/
This will tell jekyll you want temporary sites generated in the /tmp/jekyll_site folder.
B. Passing the destination via terminal
jekyll serve -d /tmp/jekyll_site/
OR jekyll serve -destination /tmp/jekyll_site/
This flag will have Jekyll generate files in the specified folder.
More information on the configuration options and flags used by Jekyll can be found here in the documentation. :)
I've created my very first Mercurial repo on my machine. I used the hg init command on the directory.
Now I'm trying to use this ignore file, before uploading to BitBucket:
Mercurial .hgignore for Visual Studio 2008 projects
Where would I post Even Mien's configuration file? I can't find an hgignore file anywhere.
Thanks
Just make one in the top-level directory of the repository (the same place where the .hg folder is).
Just create a new text file named .hgignore at the root folder of your project and paste the content into it.
I have a project, which is in the Mercurial repository. In the root folder there is a .hgignore file, which states, that the "Bin" folder should be ignored (and also some other files and folders).
Now I want to clone this repository but in a way, that ALL folders and files should be cloned, also the original ignored ones. If I just clone the repository, than I get only the files, which are included in the repository thus my bin folder is missing.
How can I get cloned repository with all files in it? I want to merge these two repositories together in a while...
PS - I am working on a legacy application which has a lot of external dll-s in the bin folder of the application. I know I should put them to a seperate folder, but that's another story.
Just copy it.
Copy the whole tree from point a to point b, and the new copy will function perfectly as a repository. The only thing that would be different from a clone is the lack of hardlinks and that the default pull/push path will be set-up to be the same as the original, rather than pointing to the original. That's easy to change by editing .hg/hgrc if you want to.
An ignored file is not in your repository, so it will not be cloned. You should copy these files by hand after you have cloned the repository.
When you copy those files, I think it won't be a problem if you overwrite other files that are in your repository (they're essentially the same files after all), so as long as you don't copy the .hg folder in the root of your checkout, you'll probably be fine.