On Fri 28 Mar 2014 10:23:17 Chris Down wrote:
there's really nothing to add to Chris's wonderful post :)
-mike
signature.asc
Description: This is a digitally signed message part.
billyco...@gmail.com writes:
> > huge wall of text
First of all, please follow basic etiquette and trim your quotes to what
is relevant. I can't even fit your e-mail on my entire screen.
> On one hand I realize you think you're being helpful to someone who
> has just started bash programming, but
On Thursday, March 27, 2014 2:15:22 PM UTC-4, Eduardo A. Bustamante López wrote:
> > Your response is "I recommend you to use 'set -x'"? Nice. Unfortunately
> > it also means you're a troll, so further discussion with you is pointless.
>
> >
>
>
>
> Well, care to explain why I'm labeled a
> Your response is "I recommend you to use 'set -x'"? Nice. Unfortunately it
> also means you're a troll, so further discussion with you is pointless.
>
Well, care to explain why I'm labeled as a troll?
I ran the following:
| bash-4.3$ mkdir a b c
| bash-4.3$ touch 1 2 3
| bash-4.3$
On Wednesday, March 26, 2014 8:30:12 PM UTC-4, billy...@gmail.com wrote:
> I tested on bash 4.3 and 3.0
>
>
>
> testing]$ bash --version
>
> bash --version
>
> GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu)
>
>
>
> In a directory I have:
>
>
>
> testing]$ ls -l
>
> total
> These restrictions that you talk about are important, but you don't seem to
> hear me when I say "My filenames never have spaces". My directories never
> have spaces. I am meticulous about my filesystems. On one hand I realize
> you think you're being helpful to someone who has just started
On Wednesday, March 26, 2014 8:30:12 PM UTC-4, billy...@gmail.com wrote:
> I tested on bash 4.3 and 3.0
>
>
>
> testing]$ bash --version
>
> bash --version
>
> GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu)
>
>
>
> In a directory I have:
>
>
>
> testing]$ ls -l
>
> total
On Wed, Mar 26, 2014 at 09:02:02PM -0700, billyco...@gmail.com wrote:
> The original intention was to play a randomly sorted list of songs (except
> ABBA):
See http://mywiki.wooledge.org/BashFAQ/026
I would use an approach like this:
files=()
while IFS= read -r -d '' file; do
files+=("$file")
On Wednesday, March 26, 2014 8:30:12 PM UTC-4, billy...@gmail.com wrote:
> I tested on bash 4.3 and 3.0
>
>
>
> testing]$ bash --version
>
> bash --version
>
> GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu)
>
>
>
> In a directory I have:
>
>
>
> testing]$ ls -l
>
> total
On Wednesday, March 26, 2014 8:30:12 PM UTC-4, billy...@gmail.com wrote:
> I tested on bash 4.3 and 3.0
>
>
>
> testing]$ bash --version
>
> bash --version
>
> GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu)
>
>
>
> In a directory I have:
>
>
>
> testing]$ ls -l
>
> total
This is a "user" problem. You are using the wrong features for the
task, your code should read:
| for f in *; do ./test "$f"; done
and quote all other variable expansions.
NEVER do: for foo in `...`ORfor foo in $(...(
This is wrong, because you're relying on word splitting and glob
expa
On Wed 26 Mar 2014 17:45:33 billyco...@gmail.com wrote:
> I thought about the changes I have made recently and I had added the
> following into my .bashrc:
>
> eval $(dircolors -b ~/.dir_colors)
>
> I commented it out, and now everything works. I think it's still a bug,
> though I know how to fi
On Wednesday, March 26, 2014 8:30:12 PM UTC-4, billy...@gmail.com wrote:
> I tested on bash 4.3 and 3.0
>
>
>
> testing]$ bash --version
>
> bash --version
>
> GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu)
>
>
>
> In a directory I have:
>
>
>
> testing]$ ls -l
>
> total
I tested on bash 4.3 and 3.0
testing]$ bash --version
bash --version
GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu)
In a directory I have:
testing]$ ls -l
total 16
-rw-r--r-- 1 hpierce hpierce 77 Mar 26 20:09 dog1
-rw-r--r-- 1 hpierce hpierce 77 Mar 26 20:09 dog2
-rw-r--r-- 1 hpie
14 matches
Mail list logo
