Not that I am the one to decide ...
but what is easier to read
sed s%`which bash`%'echo '/tools/bin/bash'`% -i /somescript.sh
or
sed s%$(which bash)%$(echo '/tools/bin/bash')% -i /somescript.sh
if you read a book?
you could also make a statement at the beginning of the book that this
is for
Bruce Dubbs wrote:
I also note, not that it means much, that the backquote form is easier
to type for lazy typists. :) The backquote is 2 keystrokes. The $()
for is six, counting the shift key three times.
Depends on your keyboard settings. I need six keystrokes for the
backtick form as
Randy McMurchy wrote:
Hi all,
I was thinking about perhaps replacing the backticks (`) in the
configure commands of the GNOME packages to $(command) syntax, but
it occurred to me that $(command) might be a bashism and other shells
(zsh, csh, etc.) might not understand them.
Does anybody
Randy McMurchy wrote:
On Tue, 2006-02-28 at 20:35 -0600, I wrote:
echo ${BIGSTRING} | sed s/^.*\($MYSTRING\).*$/\\${COUNTER}/
The word string was returned, as expected.
JUSTFORBRUCE=`echo ${BIGSTRING} | sed s/^.*\($MYSTRING\).*$/\\${COUNTER}/`
echo $JUSTFORBRUCE
Woops, we didn't get what
On Wed, 2006-03-01 at 13:23 -0500, Jeremy Huntwork wrote:
If you meant something else, I'd appreciate another example. :)
Of course, you are totally correct. They are not the same. Brain fart
on my end.
Though they *should* (in my opinion) be the same, the difference is
documented and known.
Hello,
I've installed a LFS system for use as a lightweight cvs/apache server
(maybe mail server also later).
When configuring the CVS server, I've noticed that some instructions
were left out (intentionally ?) on configuring the CVS for multiple
repositories (with, usually, each having
Andrew Benton wrote:
Have you filed a bug about this?
Andy
Just did - http://wiki.linuxfromscratch.org/blfs/ticket/1829.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
