spaces

target: dependencies command1 command2 On my system (Mac OS X), make seems to require that that Makefiles have a tab character preceding the the content of each command line, or it throws a syntax error. This is an annoyance when creating or editing Makefiles because I have my editor set up to be all-spaces-all-the-time. Can you make valid Makefiles without tab characters? Alok Singhal This is a syntax oddity/requirement of make , it has nothing to do with Mac OS X. Unfortunately, there's nothing you can do about it if you are going to use make . Edit : GNU Make now supports a custom recipe

How can I convert tabs to spaces in every file of a directory (possibly recursively)? Also, is there a way of setting the number of spaces per tab? Martin Beckett Warning: This will break your repo. This will corrupt binary files , including those under svn , .git ! Read the comments before using! find . -type f -exec sed -i.orig 's/\t/ /g' {} + The original file is saved as [filename].orig . Downsides: Will replace tabs everywhere in a file. Will take a long time if you happen to have a 5GB SQL dump in this directory. Simple replacement with sed is okay but not the best possible solution. If

I'm facing the next problem in MinGW shell under windows. I have in my /etc/profile the next expression: export GIT_SSH="/c/Program Files/TortoiseGit/bin/TortoisePlink.exe" This doesn't work when I use git fetch on the local repository. But if I do it like (old dos way) this it works: export GIT_SSH="/c/Progra~1/TortoiseGit/bin/TortoisePlink.exe" My question is: How can I make it work using spaces in the variable? For testing purpose you can simulate something like this (any example is good): export VAR="/c/Program Files/TortoiseGit/bin/TortoisePlink.exe" # and try to execute like this $VAR Is

I've gone through some similar SOQ's and have not seen an adequate solution for this case. I've noticed that in many files there is a dirty mix of tabs and spaces used for indenting. The coding standard we follow uses 4 spaces for a tab currently. Although this should have been addressed when it happened, I need to consider it now and would like to fix the files I come across. The issue is that there are two teams using different branches of code and we will eventually have to merge those branches. What will happen if we change all the files of our branch to be the correct formatting and try

Do I have to take out all the spaces in the file name to import it, or is there some way of telling import that there are spaces? You should take the spaces out of the filename. Because the filename is used as the identifier for imported modules (i.e. foo.py will be imported as foo ) and Python identifiers can't have spaces, this isn't supported by the import statement. If you really need to do this for some reason, you can use the __import__ function: foo_bar = __import__("foo bar") This will import foo bar.py as foo_bar . This behaves a little bit different than the import statement and you