On 10/12/2013 05:48 PM, Ken Moffat wrote:
> On Sat, Oct 12, 2013 at 04:59:04PM -0500, Dan McGhee wrote:
>> On 10/12/2013 03:01 PM, Ken Moffat wrote:
>>>Maybe the syntax highlighting in that version of gedit is missing
>>> or broken. Try vim and see how it looks ('syntax on' in ~/.vimrc or
>>>
On Sat, Oct 12, 2013 at 04:59:04PM -0500, Dan McGhee wrote:
> On 10/12/2013 03:01 PM, Ken Moffat wrote:
> >>
> > Maybe the syntax highlighting in that version of gedit is missing
> > or broken. Try vim and see how it looks ('syntax on' in ~/.vimrc or
> > /etc/vimrc). I use a black background, w
Hi Dan,
$(...) executes the command within the brackets. It is the same as
having `pwd` (they are backticks).
The reason for the double quotes around the $(pwd) is in case the
current directory name has spaces in it (or anything that is contained
in the $IFS variable to be exact - IFS=the intern
On 10/12/2013 03:01 PM, Ken Moffat wrote:
> On Sat, Oct 12, 2013 at 01:36:04PM -0500, Dan McGhee wrote:
>> I suppose that the most practical thing for me to do is "jump into" Ch.
>> 6 and build with the script in the hint as it exists now. I could
>> "pause" at the end of this command to see what
On Sat, Oct 12, 2013 at 01:36:04PM -0500, Dan McGhee wrote:
>
> I suppose that the most practical thing for me to do is "jump into" Ch.
> 6 and build with the script in the hint as it exists now. I could
> "pause" at the end of this command to see what was happening. However,
> in a previous l
On 10/12/2013 11:56 AM, Pierre Labastie wrote:
> Le 12/10/2013 18:27, Dan McGhee a écrit :
>>
>> Here is the line in question:
>>
>> cd "$HOME/xxxbuild/yyysrc" && srcdir="$(pwd)" || exit 1
>>
>>
>>
>> "Change to the package build directory IF AND ONLY IF the package source
>> directory is the sam
Le 12/10/2013 18:27, Dan McGhee a écrit :
> I'm melding my build script to the current one from this hint. I've
> found a possible syntax error and want to see if my thinking is
> correct. Since I've been monitoring this list closely again, i.e.; the
> last three weeks, I've not seen anyone wh
I'm melding my build script to the current one from this hint. I've
found a possible syntax error and want to see if my thinking is
correct. Since I've been monitoring this list closely again, i.e.; the
last three weeks, I've not seen anyone who has had a problem running
this script. But I t
alex lupu wrote:
>> Bruce wrote:
>> See if awk 'BEGIN {FS="\\.so"}... works for you.
>
> Hi Bruce,
>
> It DOES !!!
> Thank you very much!
>
> As an aside, (to explain) why _I_ prefer 'awk' to 'sed' _in this case:
>
> for f in `cat tempx.txt`; do echo $f | sed -r 's/(.*)\.so.*/\1/'; done
>
> vs.
>
