Quote:
Originally Posted by textillis
1. But what about simply "\h" to render "hostname"; which is what works for me?
|
Hmm. Well, you know something I don't -- never heard of using "\h" for hostname, may give that a try somewhere or other. I've always found that defining environment variables with descriptive upper case letters to be useful -- you can see the content of a variable with "echo ${VARIABLE};" e.g.,
echo ${HOST} or
echo ${USER}. For that matter, you can see the content of every environment variable by executing "env". Different strokes...
Quote:
Originally Posted by textillis
2. I notice you use single ` ... `; are these equivalent in scripting to " ... " (a key with which I am more comfortable: ie: i can actually hit it accurately, nearly every time  )? |
Frequently single quotes are just fine in place of double quotes (not `, but ', ` means something different entirely). You use `command` as a "sideways pipe" to feed output of "command" into an expression. Something like
Code:
command `other_command argument(s)`
would feed the output of
other_command argument(s) into
command.
Quote:
Originally Posted by textillis
3. slack is sinking into my fibres, into my dreams and taking up waaaayyy too much of my waking moments for me to continue to claim the tag of normality.  |
Yeah, that sort of thing do tend to happen.
Hope this helps some.
