++ ++the PS1 string should be set in .bashrc. this is because +non-interactive bashes go out of their way to unset PS1. the bash man +page tells how the presence or absence of PS1 is a good way of knowing +whether one is in an interactive vs non-interactive (ie script) bash +session. + + ++the way i realized this is that startx is a bash script. what this +means is, startx will wipe out your prompt. when you set PS1 in +.profile (or .bash_profile), login at console, fire up X via startx, +your PS1 gets nuked in the process leaving you with the default +prompt. + + ++one workaround is to launch xterms and rxvts with the -ls option to +force them to read .profile. but any time a shell is called via a +non-interactive shell-script middleman PS1 is lost. system(3) uses sh +-c which if sh is bash will kill PS1. a better way is to place the +PS1 definition in .bashrc. this is read every time bash starts and is +where interactive things - eg PS1 should go. + + ++therefore it should be stressed that PS1=..blah.. should be in .bashrc +and not .profile. + + +
++ ++"In my interactive shell I have 62 aliases and 25 functions. My rule +of thumb is that if I need something solely for interactive use and +can handily write it in bash I make it a shell function (assuming +it can't be easily expressed as an alias). If these people are +worried about memory they don't need to be using bash. Bash is one +of the largest programs I run on my linux box (outside of Oracle). +Run top sometime and press 'M' to sort by memory - see how close +bash is to the top of the list. Heck, it's bigger than sendmail! +Tell 'em to go get ash or something." + +
Shell functions are about as efficient as they can be. It is the +approximate equivalent of sourcing a bash/bourne shell script save that no +file I/O need be done as the function is already in memory. The shell +functions are typically loaded from [.bashrc or .bash_profile] depending on +whether you want them only in the initial shell or in subshells as well. +Contrast this with running a shell script: Your shell forks, the child does +an exec, potentially the path is searched, the kernel opens the file and +examines enough bytes to determine how to run the file, in the case of a +shell script a shell must be started with the name of the script as its +argument, the shell then opens the file, reads it and executes the +statements. Compared to a shell function, everything other than executing +the statements can be considered unnecessary overhead.+
I tried putting the string in PS1, but it +causes flickering under some window managers because it results in setting +the prompt multiple times when you are editing a multi-line command (at +least under bash 1.4.x -- and I was too lazy to fully explore the reasons +behind it).I had no trouble with it in the PS1 string, but didn't +use any multi-line commands. He also points out that it works under xterm, +xwsh, and dtterm, but not gnome-terminal (which uses only the main title). +I also found it to work with rxvt, but not kterm. + +
++ ++I love computer history so here goes: + + ++When IBM designed the first PC they needed some character codes to use, so +they got the ASCII character table (128 numbers, letters, and some +punctuation) and to fill a byte addressed table they added 128 more +characters. Since the PC was designed to be a home computer, they fill the +remaining 128 characters with dots, lines, points, etc, to be able to do +borders, and grayscale effects (remember that we are talking about 2 color +graphics). + + ++Time passes, PCs become a standard, IBM creates more powerful systems and +the VGA standard is born, along with 256 colour graphics, and IBM continues +to include their IBM-ASCII characters table. + + ++More time passes, IBM has lost their leadership in the PC market, and the +OS authors dicover that there are other languages in the world that use +non-english characters, so they add international alphabet support in their +systems. Since we now have bright and colorful screens, we can trash the +dots, lines, etc. and use their space for accented characters and some +greek letters, which you'll see in Linux. + + +
me and a couple guys got on irc and started hacking with sed and +got this: ++Considering how muchuptime | sed -e 's/.* \(.* days,\)\? \(.*:..,\) .*/\1 \2/' -e's/,//g' -e 's/ days/d/' -e 's/ up //' . +It's ugly, and doesn't use regex nearly as well as it should, but it +works. It's pretty slow on a P75, though, so I removed it.
++ +Copyright (C) 2000 Free Software Foundation, Inc. +59 Temple Place, Suite 330, Boston, MA 02111-1307 USA +Everyone is permitted to copy and distribute verbatim copies +of this license document, but changing it is not allowed. +
+ ++ Copyright (c) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 + or any later version published by the Free Software Foundation; + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + A copy of the license is included in the section entitled "GNU + Free Documentation License". +
ycfjPZYiFTotKpe+F9kkpuB11s*?
zz0W_Vj{`(!Yl M4o6`3iO0FM9^4_w;_D{qYOe_f1>Lu=Px7!R&?QQNe^LgUYHUk9=JB
z8~3kE=#p(#A07UD{?huD{v8EvvRmLhICLjXn;8TTzUuAv%7JGuEu9Nw!{=o^-u+fR
zZ}hHmT|E*Y+M%CmE4xPx@zy;l9hq6)=@eytn!Nu!Yhx=rZ*Dr-rr&QC0qI5hEnMLK
z^V1FgR&1L-E~KIw&L4#u>tJd{A`*J^eODD
z2;g0UiUihgKmAr)
bhS
zoXTqzJH$