![]() All boil down to this: surface-based nav systems still rule the roost. You still fly airways a great deal of the time and execute what appear to the outside observer to be standard non-precision approaches.īefore going into more detail, it is essential to point out a few regulatory limitations that may come as a surprise. In consequence, most of the changes associated with the adoption of GPS are limited to a simple switch in navigation technology. The most important observation to make about using IFR GPS is also the most obvious: the instrument flight rules (IFR) remain in force: all the basic rules and procedures outlined in the FAR for instrument operations are still there. It's now time to start on the "how to's." home/jim/anaconda3/etc/profile.d/conda.In the last two months I have tackled the job of clearing away some of the underbrush that might obscure the use of GPS for IFR operations. ![]() #export PATH="/home/jim/anaconda3/bin:$PATH" usr/share/bash-completion/bash_completion # this, if it's already enabled in /etc/bash.bashrc and /etc/profile # enable programmable completion features (you don't need to enable # See /usr/share/doc/bash-doc/examples in the bash-doc package. # ~/.bash_aliases, instead of adding them here directly. # You may want to put all your additions into a separate file like # Add an "alert" alias for long running commands. Test -r ~/.dircolors & eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" # enable color support of ls and also add handy aliases # If this is an xterm set the title to "$TERM" \w\a\]$PS1" # a case would tend to support setf rather than setaf.) (Lack of such support is extremely rare, and such # We have color support assume it's compliant with Ecma-48 ![]() # should be on the output of commands, not on the prompt # off by default to not distract the user: the focus in a terminal window # uncomment for a colored prompt, if the terminal has the capability turned Xterm-color|*-256color) color_prompt=yes # set a fancy prompt (non-color, unless we know we "want" color) # set variable identifying the chroot you work in (used in the prompt below) # make less more friendly for non-text input files, see lesspipe(1) # match all files and zero or more directories and subdirectories. # If set, the pattern "**" used in a pathname expansion context will # update the values of LINES and COLUMNS. # check the window size after each command and, if necessary, # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) # append to the history file, don't overwrite it # don't put duplicate lines or lines starting with space in the history. bashrc # If not running interactively, don't do anything profile (excluding standard $path stuff and other personalized things): # if running bash If I close that terminal and reopen a new terminal, (base) is there again. If I run source ~/.profile in the terminal, it disappears. ![]() ![]() I'm wondering why I have (base) on the left of my terminal prompt. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |