Home > Uncategorized > daily 12/22/2013

daily 12/22/2013

  • If you only ask God for small things, you won’t see Him do great things. Be bold and pray God-sized prayers.

  • O come all ye whiskey
    Bourbons, ryes, and scotches
    Come all ye brown liquors
    It’s whisssssskey time

  • We’re counting down the best OneNote moments of 2013. First up, save time with #OneNote Shortcuts: http://t.co/EFuOJMexkP #BestOf2013

    tags: OneNote BestOf2013

  • The interim coach onside kick is the equivalent of Tokyo drifting in a rental car.

    • The Whole Foods decision marks another blow to Chobani, a New York company that was once the darling of Greek-style yogurt lovers. But in September, its star faded amid a flurry of complaints from customers over bloated and exploding containers, foul taste and even illnesses.
    • I think I created and switched between 3 or 4 branches, testing modifications and merges, in less than 5 minutes. In a command line window. Not in an IDE. This is really freaking cool.
    • So github is a bit like Facebook for hackers, without all the Mafia Wars and Farmville requests. Exploring the world of code waiting out there ready to be “forked with” is a little overwhelming, but to know there are so many folks out there making so many things with software is comforting. Coming from a guy who sees making machines do things as an end in an of itself, there is a lot of ends to explore here.
    • Why is the Powershell Environment PATH different to the System Environment PATH?
    • Powershell will inherit the environment of the process that launched it (which depends on how you launch it). This is usually the interactive shell (explorer.exe). When you modify the environment from computer properties, you modify the environment of explorer.exe, so if you launch powershell from explorer.exe, (for example from the start menu) you should see the new environment.
    • Test-Path will return True if the folder exists and False if the folder doesn’t exist. See? Test-Path might be obscure, but it’s far from useless.
    • What we’ve done here is tack on the –pathType parameter and assign the parameter the value container. That means that we want to know if the specified object (C:\Scripts\Archive) is a container: that is, is it capable of containing other objects. (Needless to say, a folder is capable of containing other objects.) Alternatively, we could have used the value leaf to determine if Archive was a leaf object (an object not capable of containing other objects):
    • This command displays or sets a search path for executable files. This command is an alias for SET PATH.

         

       

    • Type “PATH ;" to clear all search-path settings and to direct the command processor to search only in the current directory.

       

      Use PATH without parameters to display the current path.

    • PATH is an environment variable on Unix-like operating systems, DOS, OS/2, and Microsoft Windows, specifying a set of directories where executable programs are located. In general, each executing process or user session has its own PATH setting.
    • On POSIX and Unix-like operating systems, the $PATH variable is specified as a list of one or more directory names separated by colon (:) characters.[1][2]

       

      The /bin, /usr/bin, and /usr/local/bin directories are typically included in most users’ $PATH setting (although this varies from implementation to implementation). The current directory (.) is sometimes included as well,

    • allowing programs residing in the current working directory to be executed directly.
    • Superuser (root) accounts as a rule do not include it in $PATH, however, in order to prevent the accidental execution of scripts residing in the current directory. Executing such a program requires the deliberate use of a directory prefix (./) on the command name.
    • On DOS, OS/2, and Windows operating systems, the %PATH% variable is specified as a list of one or more directory names separated by semicolon (;) characters.[3]
    • When a command is entered in a command shell or a system call is made by a program to execute a program, the system first searches the current working directory and then searches the path, examining each directory from left to right, looking for an executable filename that matches the command name given. Executable programs have filename extensions of EXE or COM, and batch scripts have extensions of BAT or CMD. Other executable filename extensions can be registered with the system as well.
    • The PATH variable makes it easy to run commonly used programs located in their own folders. If used unwisely, however, the value of the PATH variable can slow down the operating system by searching too many locations, or invalid locations.
    • First things first – you need to create a place for your environment. This does it:
    • Now that you are there, you can edit your profile. You can see what file is going to be edited using:

       

      PS> $profile C:\Users\Adrian\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
    • There is a different file for the Integrated Scripting Environment (ISE), so you can have one profile for your PS> prompt and another for the ISE.
    • I’ve added a short cmdlet for processing the PATH (called Add-Path) and then I use that to alter the path.

Posted from Diigo. The rest of my favorite links are here.

Advertisements
Categories: Uncategorized
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: