$ cd /director/with/your/file
$ find . -type f -exec perl -pi -e 's/\r\n?/\n/g' {} \;
$ perl -pi -e 's/\r\n?/\n/g' filename.txt
]]>def show_sku_message
sprintf("%-8s %-5s %-5s", value1, value2, value3 ).gsub(' ', ' ')
end
#include <iostream>
int main( int argc, char** args, char** env )
{
int i = 0;
while( env[i] != NULL )
{
std::cout << env[i] << std::endl;
i++; }
return 0;
}
No teacher or book ever mentioned that main() can take more than two arguments. My guess is that this is OS dependent. Which would explain why it is never mentioned or explained in books.
I don't immediately see how browsing through the environment variables could be useful, but then I never knew it was possible before... maybe I'll think of a use for it later.What else is out there? How about another NULL terminated list? It looks like this is the command that was called - but why again, this is normally in argv[0]?
#include <iostream>Windows also supports the extra arguments in main.]]>
int main( int argc, char** args, char** env, char** whatisthis )
{
int i = 0;
while( whatisthis[i] != NULL )
{
std::cout << whatisthis[i] << std::endl;
i++; }
return 0;
}
C:\Documents and Settings\<username>\Application Data\Subversion\configUnder the [tunnels] section, I added the line:
ssh = plink -P 1234 -l username -i D:/Path/to/key.ppkWhere key.ppk is the private key that you want to use to authenticate. Make sure you use the -l option, on unix you wouldn't need this, but plink will get confused if it isn't there, even when logging in with key authorization. Be sure to use forward slashes in your paths!! Make sure that plink.exe is in your PATH, otherwise use
ssh=C:/path/to/plink.exe -P 1234 -l username -i D:/Path/to/key.ppkUse pscp to copy your public key to the server. This is likely the key you saved without the .ppk extension.Login to your server.PuttyGen doesn't save the keys the way that OpenSSH expects them. You can use PuttyGen to export the key to OpenSSH or you can simply use vi to do this - I elected to use vi. Delete the headers and the trailing footer line, then get rid of each newline character so that the key is one long string. Before the key, type
command="/path/to/your/svnserve -t -r /repos/pathfollowed by a space. Then type
ssh-dssfollowed by a space. If your key is not a DSA key, like mine, figure out what you need instead of ssh-dss. Finally, after your key string type a space followed by
username@domainThis should be something meaning full to you. Typically, you would use this to figure out which key to delete if the need arises but it isn't necessary.Append your key file onto your authorized_keys2 file using:
cat key-filename >> ~/.ssh/authorized_keys2Logout of your server.Test your connection from the windows client:
plink -l username -P 1234 -i D:\path\to\key.ppk server_ipYou should see
( success ( 1 2 ( ANONYMOUS EXTERNAL ) ( edit-pipeline ) ) )This means your connection is working and you are ready to use Subversion. Note that you won't get a command prompt because we configured SSH to run svnserve when the session is authenticated using this key. If you still want command line access, login without this key using Putty or ssh.List the contents of your project:
svn list svn+ssh://serverIP/project]]>