environment

Almost all the .exe's I use via command line have a help function that gets called by the "--help" command. How do I implement this in C#? Is it as simple as checking whether or not the parameter in args[] is the string "--help"?? A C# snippet for processing the command line across multiple cultures is... string[] args = Environment.GetCommandLineArgs(); if (args.Length == 2) { if (args[1].ToLower(CultureInfo.InvariantCulture).IndexOf("help", System.StringComparison.Ordinal) >= 0) { // give help } } The detection logic can be combined with "?" or "/?" or any other combination that covers all

I've written a data collection script for Cacti in Ruby and it runs fine from the command line but Cacti runs the script via "env -i" which strips the environment so Ruby can't find the rubygems library ("in `require': no such file to load -- rubygems (LoadError)"). How might I work around this? #!/bin/sh #export LOAD_PATH=whatever #export RUBYLIB=whatever #export RUBYOPT=whatever #export RUBYPATH=whatever #export RUBYSHELL=whatever #export PATH=$PATH:whatever exec ruby -x. $0 "$@" #!/usr/bin/ruby require 'rubygems' require 'open4' # or whatever # rest of ruby script here This is a shell

I've been working on a Processing project for a while, and now want to move it into Eclipse. I've installed Proclipse with my Eclipse environment. I've a lot of files with the extension of ".pde". However the Proclipse files all ends with ".java". And there's a lot of dependency issues with all the pde files. How should I convert my project? =============== Thanks everyone! There doesn't seem to be a one-button solution, I refactored all the code following an approach similar to George's answer. Plus changing all the file extensions from ".pde" to ".java". Jose's advice is pretty good.

I am writing Ansible playbooks to setup and install our applications on Solaris servers. The problem is that the (bash) scripts which I need to execute all assume that a certain directory lies on the PATH, namely /data/bin - which would normally not be a problem were it not for Ansible ignoring all the .profile and .bashrc config. Now, I know that you can specify the environment for shell tasks via the environment flag, for example like this: - shell: printenv environment: PATH: /usr/bin:/usr/sbin:/data/bin This will properly path the /data/bin folder, and the printenv command will correctly

My application is currently storing settings in an INI file under the current user's profile ( C:\Documents and Settings\<CurrentUser>\Application Data\MyApplication\MySettings.ini under WinXP). But I've realised some of these settings are unique to the machine not the user and thus want (actually need) to save them in a single location for all users. Is there a folder location on Windows XP (and up) where I can store user independent settings? NOTE: I don't want to store them in the same folder as my application nor do I want to store them in the registry. I notice there is an "All Users"

I need help drawing the relevant portions of the environment model diagram when evaluating this code: Scheme>(define x 10) Scheme> ((lambda (x y) (+ (y 3) x)) 6 (lambda (w) (* x 9))) I need to make sure and write each lambda body next to the environment in which it is being evaluated. Okay I know that there is only one define so most of the work will be done by “anonymous” or “nameless” functions and these will still show up in various ways in the environment model diagram In addition to the answers already given, the 6.001 course at MIT has two very comprehensive lectures on the environment

Questions : What does the kernel do if you stick a shell-script into the shebang line? How does the Kernel know which interpreter to launch? Explanation : I recently wanted to write a wrapper around /usr/bin/env because my CGI Environment does not allow me to set the PATH variable, except globally (which of course sucks!). So I thought, "OK. Let's set PREPENDPATH and set PATH in a wrapper around env.". The resulting script (here called env.1 ) looked like this: #!/bin/bash /usr/bin/env PATH=$PREPENDPATH:$PATH $* which looks like it should work. I checked how they both react, after setting