> Oh, and I've got this as my prompt. Drop this in ~/.bashrc if you use
> bash...
>
> function elite2 {
> local TTY=`tty|cut -d/ -f3,4`
> local C1="\[\033[32;40m\]"
> local C2="\[\033[35;40m\]"
> local C3="\[\033[0m\]"
> local D="$C2-$C1"
> PS1="$D(\u$C2@$C1\h)$D($TTY)$D(\$(date +%Y%m%d)$C2.$C1\$(date
> +%H%M))$C2-\n$D(\w)$C2 | $C3"
> }
>
Yowsah, that's one thing i'd LIKE to get working under emacs (in copious
spare time :P)
> elite2
> unset elite2
>
>
> It makes a green and purple prompt that looks like this:
>
> -(rob@fuggles)-(pts/2)-(20010817.1302)-
> -(~/code) |
Um what does that line do?, i tried parts on it on my terminal but
couldn't get it to show me the behavior (yes i do type whole lines in to
check them out) Is ~/code a translator?
>
> --
> Rob <rob_at_euglug_dot_net>
> my @euglugCode = qw(v+++ e--- eug+ bsd+++ gnu+ S+++);
>
nice,
qw = quick.work# in python you leave off the() from a
# function to assign the function itself
# to the variable.
# is a coment in a line of code the parser drops everything to the
# end of the line. After seeing a # symbol
;I think we can dispense with the semicolons ;-)
anybody want to show and tell on how to parse a buffer?
i = buffer('chr',80,kw**)
# kw** is a dictionary (hashtable, associated array) passed to func
what does this email look like when you pass it through the wiki's parser?
