Format:ĭocument, Folder, or the name of the custom documentĬlass or item type. Uses the template_name value as the prefix to this folder ID. The system-generated identification number for the document. Is displayed for the server in the ID column on the Repositories tab Specifies the server to log in to. Specify the ID that Specifies which desktop to log in to. Specify the ID that isĭisplayed for the desktop in the ID column on the Desktops tab in theĪdministration tool. Sometimes I want to bridge the gap from command line to the Finder, usually when I’m processing files and want to indicate which ones have been processed.In addition to the previous response, for downloading you can also construct a URL for IBM Content Navigator like this #CYBERDUCK SOFTLAYER MAC#The Mac Finder has the concept of “labels” which used to, and may still, have text associated with them, but I only use them to color the background of files in the Finder. They could certainly each be their own shell script in the bin directory, but…they’re not. Shell functions give me more control than an alias. Without them the text wraps incorrectly when you cd to a long or deeply-nested directory name. The extra backslashes and square brackets are necessary so that the color codes are not counted as printed characters when counting columns. This PS1 variable gives me a prompt like this: That said, the PS1 variable is one that I usually override and specify manually in ~/.bash_profile. I use it to create a default shell prompt that has a good chance of being an unexpected color when I SSH onto another system. The tRandColor variable gives me a color based on the hostname of the system. Frankly, I don’t know if I have to have all these empty “set” statements, but it seems like good form. I have the big if/then statement so that I can embed these variables, and if colors are supposed to be ignored, the variables will simply be empty. If then INTERACTIVETERM=”-NO-“ TERM=”vt100” fi This is because tput barfs if there’s no proper TERM variable set, so before I define colors, I make a way to detect interactivity. Because of a number of other ways in which I interact with the shell, such as DTerm, the awesomest tiny tool I’ve come across in a long time, I need to know if the bash_profile script is running in some kind of interactive way (Terminal.app) or something else. Colorsīefore I get into functions and status updates, I want to be able to sprinkle my terminal with useful color using tput commands and ANSI escape sequences. Of course I use directory listings pretty much continuously, but I find that I use pg to search for running processes quite a bit too. I have others (not shown) for making common SSH connections and other things. Many of these you’ll find on other sites that suggest useful aliases, but in summary, I have various shortcuts for listing directory contents by clearing the screen first (‘c’) and in color, keeping track of current directory changes (OK, those are functions not aliases, but they’re awfully short), and searching for running processes or programs I’d like to install. Here are some of the alias commands I put in my Dropbox bash_profile file: In my bash profiles I put aliases, very simple command substitutions or expansions. Of course one of the first things I do in the Dropbox file is add bin to my PATH:Įxport PATH=~/Dropbox/bin:$PATHĮven if you don’t use Dropbox, having most of your bash environment set up in a separate file makes it easy to copy from machine to machine and keep your customizations readily accessible. Inside my ~/.bash_profile script, near the top, I check for and include the Dropbox file: It’s what Apple’s iDisk is supposed to be, except that Apple’s iDisk is unreliable and slow, where as the Dropbox and SugarSync guys have figured it out.įirst I create a bin folder on my Dropbox:Īs a repository for my new ~/Dropbox/bin/bash_profile script as well as sundry scripts and command line apps that I want to share, such as my LocateMe app for finding my latitude and longitude. If you haven’t explored Dropbox or SugarSync yet, you probably should. The following are suggestions for useful additions to your command line lifestyle. The key is to abstract away machine-specific references. With a little effort you can share the critical components across several computers either automatically ( Dropbox or SugarSync) or manually. If you live at the command line as I do, you probably have a number of aliases, functions, and status updates added to your ~/.bash_profile, ~/.bashrc, or similar file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |