**** BEGIN LOGGING AT Sun May 05 02:59:58 2013
May 05 08:38:13 <DocScrutinizer05> http://talk.maemo.org/showthread.php?p=1341376#post1341376
May 05 08:40:58 <MohammadAG> bash is a mysterious thing sometimes :|
May 05 08:41:06 <MohammadAG> or I'm losing my script-fu
May 05 08:49:30 <DocScrutinizer05> hey MohammadAG!
May 05 08:50:01 <MohammadAG> hey DocScrutinizer05 :)
May 05 08:50:22 <DocScrutinizer05> I once actually found a bug in bash, but usually it's just the user aka PEBKAC
May 05 08:50:54 <DocScrutinizer05> what's your problem?
May 05 08:51:37 <DocScrutinizer05> MohammadAG: also, have you already voted?
May 05 08:52:02 <MohammadAG> I just figured it out
May 05 08:52:21 <MohammadAG> apparently a for x in $(ls) loop fails for spaces
May 05 08:52:30 <MohammadAG> I just switched to a while read loop
May 05 08:52:39 <MohammadAG> DocScrutinizer05, nope, it's that time again?
May 05 08:53:09 <DocScrutinizer05> ugh, see topic!
May 05 08:53:46 <MohammadAG> heh, I usually skip the first part
May 05 08:54:20 <DocScrutinizer05> (for x in $y) a env is one token usually
May 05 08:54:25 <DocScrutinizer05> I'd think
May 05 08:55:02 <MohammadAG> ls *m4a | while read f; do aac2mp3 -b 320 -c "$f"; done worked
May 05 08:55:24 <MohammadAG> for files in "$(ls *m4a)"; do aac2mp3 -b 320 -c "$files"; done didn't
May 05 08:55:59 <DocScrutinizer05> btw WFM
May 05 08:56:04 <DocScrutinizer05> jr@saturn:/usr/share/man> echo $x
May 05 08:56:05 <DocScrutinizer05> a b c
May 05 08:56:07 <DocScrutinizer05> jr@saturn:/usr/share/man> for y in $x; do echo $y; done
May 05 08:56:08 <DocScrutinizer05> a
May 05 08:56:10 <DocScrutinizer05> b
May 05 08:56:11 <DocScrutinizer05> c
May 05 08:56:33 <MohammadAG> DocScrutinizer05, your files don't have spaces in their name
May 05 08:56:50 <MohammadAG> Due to the nature of digital music, it's sort of possible for files to have spaces in their names :P
May 05 08:56:57 <DocScrutinizer05> ooh, so you got the other problem
May 05 08:57:16 <DocScrutinizer05> the you must use " " arounf the name
May 05 08:57:21 <DocScrutinizer05> around
May 05 08:58:14 <MohammadAG> isn't that what I'm doing?
May 05 08:58:46 <DocScrutinizer05> well, no, you're doing exactly the opposite
May 05 08:59:08 <DocScrutinizer05> "a.m4a foo bar.m4a"
May 05 09:01:03 <MohammadAG> hmm, so what's the correct way?
May 05 09:02:16 <DocScrutinizer05> jr@saturn:~> for y in x*; do echo $y; done
May 05 09:02:17 <DocScrutinizer05> x
May 05 09:02:19 <DocScrutinizer05> x 1
May 05 09:02:20 <DocScrutinizer05> x 2
May 05 09:02:22 <DocScrutinizer05> x 3
May 05 09:03:21 <MohammadAG> DocScrutinizer05, echo takes spaces
May 05 09:03:26 <MohammadAG> do something else
May 05 09:03:55 <MohammadAG> like cat for example
May 05 09:04:12 <DocScrutinizer05> jr@saturn:~> for y in x*; do ls -l "$y"; done
May 05 09:04:13 <DocScrutinizer05> -rw-r--r-- 1 jr users 40  4. Mai 03:00 x
May 05 09:04:15 <DocScrutinizer05> -rw-r--r-- 1 jr users 0  5. Mai 11:01 x 1
May 05 09:04:16 <DocScrutinizer05> -rw-r--r-- 1 jr users 0  5. Mai 11:01 x 2
May 05 09:04:18 <DocScrutinizer05> -rw-r--r-- 1 jr users 0  5. Mai 11:01 x 3
May 05 09:04:59 <DocScrutinizer05> :-)
May 05 09:06:16 <MohammadAG> still doesn't work for me :(
May 05 09:06:21 <MohammadAG> for x in `ls *.m4a.mp3`; do 
May 05 09:06:21 <MohammadAG>   t=`echo "$x" | sed 's/\.m4a.mp3$/.mp3/'`; 
May 05 09:06:21 <MohammadAG>   echo "moved \"$x\" -> \"$t\""
May 05 09:06:21 <MohammadAG> done
May 05 09:06:22 <DocScrutinizer05> duh!
May 05 09:06:33 <DocScrutinizer05> no fucking `ls *`
May 05 09:06:38 <MohammadAG> ah ok
May 05 09:06:40 <MohammadAG> :P
May 05 09:06:52 <MohammadAG> ooooh shiny
May 05 09:07:38 <DocScrutinizer05> when bash does the expanding, bash knows about the spaces in that token
May 05 09:07:57 <DocScrutinizer05> with `ls *` it has no way to know
May 05 09:09:57 <MohammadAG> now to figure out what kind of m3u files my dad's car takes
May 05 09:10:22 <MohammadAG> DocScrutinizer05, I totally forgot about * working without a command
May 05 09:10:25 <MohammadAG> e.g ls
May 05 09:11:01 <DocScrutinizer05> yeah, the main difference between a decent unix shell and a fake like dos, where every command is doing that on its own
May 05 09:11:42 <DocScrutinizer05> actually `ls` is the same like `echo *`
May 05 09:12:10 <DocScrutinizer05> basically
May 05 09:46:42 <MrPingu_> Hi here!
May 05 10:15:34 <zammy> Hi all
May 05 10:17:19 <zammy> i am using the default program fot chat on n900 
May 05 10:17:48 <zammy> It is pretty cool
May 05 10:26:11 <zammy> But i would know how to get my provider SIM settings on n900? 
May 05 10:31:12 <zammy> i read around for google
May 05 10:33:14 <zammy>  no possible
May 05 10:33:14 <zammy> Uff
May 05 10:45:00 <infobot> DocScrutinizer: infobot joined!
May 05 10:46:31 <DocScrutinizer05> ~+status
May 05 10:46:32 <infobot> Since Sun May  5 10:38:28 2013, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 0 commands.  I have been awake for 8m 3s this session, and currently reference 119044 factoids.  I'm using about 18636 kB of memory. With 0 active forks. Process time user/system 6.46/0.14 child 0.01/0
May 05 10:46:48 <DocScrutinizer05> o.O
May 05 11:38:27 <Mr_Stupid> Oorgle?
May 05 13:01:07 <DocScrutinizer05> MohammadAG: anyway filenames with spaces are a pita in unix, and I strongly suggest to not even allow them anywhere. When importing e.g. mp3 then just convert all spaces to underlines
May 05 13:15:06 <kerio> filenames with spaces are a PITA if you're using inferior tools
May 05 13:15:12 <kerio> or using them wrong
May 05 13:23:41 <apic> A splendid good Sunday.
May 05 13:36:44 <DocScrutinizer05> kerio: on linux about every (cmdline) tool is "inferior" when it comes to handling filenames with spaces
May 05 13:57:06 <ron0062010> 2
May 05 14:17:18 <Riviera> DocScrutinizer05: Do you have any example?
May 05 14:17:50 <Riviera> Actually particularly Linux (i.e. GNU) tools work quite well with filenames that even contain newline characters.
May 05 14:24:28 <DocScrutinizer05> Riviera: use find in a for x in `find ...` loop, with filenames that contain spaces
May 05 14:24:53 <DocScrutinizer05> have fun
May 05 14:24:59 <Riviera> DocScrutinizer05: As kerio said, that's wrong usage.
May 05 14:25:14 <DocScrutinizer05> hahaha
May 05 14:25:28 <Riviera> DocScrutinizer05: Splitting input into words and then being surprised that the input is split is not a convincing example.
May 05 14:25:34 <DocScrutinizer05> so what's "right" use then?
May 05 14:25:50 <Riviera> DocScrutinizer05: Depends on what's available.  You said Linux, so I assume GNU tools, like bash and GNU find:
May 05 14:25:55 <kerio> find $path -$filters -exec
May 05 14:26:04 <DocScrutinizer05> meh
May 05 14:26:11 <Riviera> DocScrutinizer05: while IFS= read -r -d '' x; do some_command "$x"; done < <(find .. -print0)
May 05 14:26:11 <kerio> or find $path -$filters -print0 | xargs -0
May 05 14:26:19 <DocScrutinizer05> I'm smart enough to know about -exec
May 05 14:26:30 <DocScrutinizer05> even about -print0
May 05 14:26:45 <Riviera> DocScrutinizer05: That'll work not only with paths containing spaces but also with newlines, and, in fact, any characters.
May 05 14:26:50 <DocScrutinizer05> but obviously for x in list, it's fucked up
May 05 14:26:57 <Riviera> As -exec and | xargs -0 would as well, but you wanted a loop, so there you are.
May 05 14:27:07 <Riviera> Well certainly, but that's expected.
May 05 14:28:09 <DocScrutinizer05> the point is that for x actually works just fine
May 05 14:28:22 <DocScrutinizer05> it's the $( find ) that fucks up stuff
May 05 14:28:37 <Riviera> You can make it work for find output that doesn't contain paths with newlines with:  IFS=$'\n'; set -f; for blah in $(find); do ..; done
May 05 14:28:46 <DocScrutinizer05> for x in "a b" "c d" "e f" works like a charm
May 05 14:28:53 <Riviera> Sure.
May 05 14:29:31 <Riviera> But $() isn't a good choice anyway, because you would have to use it unquoted, hence word-splitting and pathname expansion happen.  Also $() removes trailing newline characters.
May 05 14:29:33 <kerio> any shell trick except using NUL as a separator will eventually fail
May 05 14:29:39 <DocScrutinizer05> I tried with IFS=, and IFS=: and it blew chunks on "do" unexpected
May 05 14:30:04 <Riviera> Well, as kerio said, the tools work just fine if you don't use them incorrectly.
May 05 14:30:22 <DocScrutinizer05> ooh, kerio said that?
May 05 14:30:25 <DocScrutinizer05> hah!
May 05 14:30:26 <Riviera> So a legitimate blame would be things were too complicated.
May 05 14:30:46 <Riviera> Why do you laugh that much?  You obviously are too clueless for this level of arrogance.
May 05 14:31:18 <DocScrutinizer05> a legitimate blame would be that anybody using blanks, comma, backspace, esc, exclamation mark,  etc, in a filename should get shot with hot owlshit
May 05 14:31:32 <kerio> except that they're perfectly valid characters to use in a path name
May 05 14:31:59 <kerio> well, you don't use characters in path names, you use bytes
May 05 14:32:02 <DocScrutinizer05> even esc ans backspace?
May 05 14:32:18 <Riviera> Yes, every character except \0 and, well /.
May 05 14:32:23 <kerio> i think that the only two invalid bytes are NUL and '/'
May 05 14:32:29 <DocScrutinizer05> my point stands
May 05 14:32:34 <DocScrutinizer05> hot owl shit
May 05 14:32:39 <kerio> oh, absolutely
May 05 15:03:03 <jaska> you can also make eth0:0 style aliases that have escape codes or backspaces in them with ifconfig :)
May 05 15:23:50 <samn900> Hello, how can I use all common commands of irc by the n900? 
May 05 15:24:16 <samn900> Such /ctcp
May 05 15:37:23 <Macer> what client are you using?
May 05 15:37:33 <Macer> if you use irssi on it then it works just the same
May 05 15:37:59 <samn900> Well now here is default chat client of n900 
May 05 15:38:24 <samn900> But i have installed also irssi right now
May 05 15:39:23 <samn900> So i am fine now but i would switch tabs on irssi client 
May 05 15:39:52 <samn900> Idk how to use it
May 05 15:42:13 <Macer> http://www.irssi.org/documentation/manual
May 05 15:42:20 <Macer> or you can just   install xterm
May 05 15:42:23 <Macer> er
May 05 15:42:24 <Macer> xchat
May 05 15:42:36 <Macer> xchat = gui based client
May 05 15:42:55 <samn900> Yes I tried xchat
May 05 15:43:09 <samn900> It did not connect
May 05 15:44:46 <Macer> if it didn't connect it is a problem with whatever server you are using
May 05 15:44:49 <Macer> maybe the server is down
May 05 15:44:56 <Macer> or you have to send it something to connect because of no identd
May 05 15:45:08 <samn900> Nope anyway thx
May 05 15:45:15 <samn900> For the link
May 05 15:45:16 <Macer> k
May 05 15:45:18 <Macer> yeah
May 05 15:45:27 <Macer> irssi has a bit of a learning curve.. but once you do it it is worth it
May 05 15:45:32 <Macer> especially since you can use it on a shell 
May 05 15:45:33 <Macer> heh
May 05 15:45:38 <Macer> which is what most people do 
May 05 15:46:11 <samn900> I want just to use to connect to my eggdrop so i only need ctcp command available
May 05 15:46:19 <samn900> Nothing else
May 05 15:46:30 <samn900> Thx its enough for me
May 05 16:15:50 <kerio> >.<
May 05 16:16:07 <kerio> for crying out loud, stop using IRC to download warez
May 05 16:16:10 <kerio> it's a crappy method
May 05 16:16:44 <samn900> I dont
May 05 17:56:22 <Win7Mac> how can I find a certain user in http://maemo.org/profile/list/? Sort: is missing "by user" I'd say...
May 05 18:33:58 <Win7Mac> or am I missing something?
May 05 20:34:16 <DocScrutinizer51> i would honestly like to get a repligard backup from Nemein and compare or even merge it to our currnt repligard
May 05 20:51:49 <DocScrutinizer51> anyway, finding (out about) a GUID that's 'missing' and where it comes from, what type/record it has or should have in repligard, etc
May 05 20:52:10 <DocScrutinizer51> is probably the way forward
May 05 20:53:35 <DocScrutinizer51> eh ECHAN
May 05 21:01:05 <Win7Mac> ~ECHAN
**** ENDING LOGGING AT Mon May 06 02:59:58 2013