| 01:05.49 | *** join/#utah jalbretsen (~jalbretse@68.69.165.108) |
| 01:27.06 | harleypig | What the heck does this do? if $(<<<"$filename" grep -q '.wiki$'); then echo something; fi |
| 01:27.11 | harleypig | err ... in bash |
| 01:34.26 | *** join/#utah gr3yR0n1n (~gr3yR0n1n@c-174-52-62-40.hsd1.ut.comcast.net) |
| 01:34.47 | keldwud | harleypig, if I knew what the <<< operator did |
| 01:34.52 | keldwud | I could maybe figure it out |
| 01:35.04 | keldwud | opens man pages |
| 01:35.34 | harleypig | I know it's a form of heredoc, but I can't find a reference to it. |
| 01:36.34 | keldwud | http://emacs.stackexchange.com/questions/5336/why-does-typing-instead-produce-eof-n-when-in-shell-script-mode |
| 01:36.38 | keldwud | is that it? |
| 01:36.46 | keldwud | end of file? |
| 01:36.49 | *** join/#utah davyjay (a11c0738@gateway/web/freenode/ip.161.28.7.56) |
| 01:37.05 | frostyfrog | Hello new Linux user davyjay! :) |
| 01:37.29 | keldwud | hmm maybe that doesn't help |
| 01:37.31 | keldwud | I'll dig deeper |
| 01:39.34 | harleypig | keldwud: no, I don't think so, but it does give me some more idea of what's going on. if I change 'soemthing' to $? then if $filename ends in .wiki 1 is printed, otherwise 0 is printed. |
| 01:39.51 | harleypig | So, <<<blah dumps to STDIN? |
| 01:40.58 | harleypig | Yep. |
| 01:41.12 | harleypig | <PROTECTED> |
| 01:41.12 | harleypig | to stdin |
| 01:41.20 | frostyfrog | Cool :) |
| 01:41.20 | keldwud | The format of here-documents is: |
| 01:41.21 | keldwud | <PROTECTED> |
| 01:41.21 | keldwud | <PROTECTED> |
| 01:41.21 | keldwud | <PROTECTED> |
| 01:41.29 | keldwud | is that it? |
| 01:41.32 | keldwud | http://stackoverflow.com/questions/4937792/using-variables-inside-a-bash-heredoc |
| 01:41.45 | keldwud | if <<< translates to <<EOF that is |
| 01:41.46 | harleypig | Well, I knew about <<word ... |
| 01:42.07 | keldwud | p.s. I am probably more in the dark than you are :) |
| 01:42.22 | keldwud | just trying to play Wilson to your House and maybe hopefully get you on the right track |
| 01:42.43 | harleypig | keldwud: :] |
| 01:43.01 | keldwud | so I have my technical interview with SuSe Tuesday |
| 01:43.10 | keldwud | the first interview went well and they didn't even have an opening |
| 01:43.18 | keldwud | but then they had one after discussing |
| 01:43.24 | harleypig | So, if I'm reading this right, It's still << and the 'word' is the stdin operator, <. |
| 01:43.24 | keldwud | so that's good news |
| 01:43.26 | harleypig | oh, nice |
| 01:43.31 | keldwud | harleypig, yeah that's what I was thinking |
| 01:43.37 | keldwud | because in that first stack overflow |
| 01:43.47 | keldwud | it showed that the stdin operator was being translated to EOF |
| 01:43.58 | keldwud | which makes it a word |
| 01:44.10 | harleypig | except <<>"testing" gives a syntax error. |
| 01:44.30 | keldwud | could just be a quirk of bash |
| 01:44.41 | keldwud | because at this level, it's hard to tell what it reads and doesn't read |
| 01:45.11 | keldwud | like, <<>, it could very well just be reading that third chevron properly |
| 01:45.19 | keldwud | and so it's like, "I can't do that, Dave" |
| 01:45.28 | keldwud | but when you give it a <, then it reads it as a word |
| 01:45.35 | keldwud | try echo <<< |
| 01:45.36 | keldwud | ? |
| 01:45.37 | keldwud | :) |
| 01:46.20 | keldwud | Another option of course is to insert <<< with C-3 <. glucas Dec 13 '14 at 2:16 |
| 01:46.21 | keldwud | <PROTECTED> |
| 01:46.21 | keldwud | Thank you for showing how to turn it off. This sh-electric-here-document-mode is a rather useless feature, IMO. |
| 01:46.24 | harleypig | bash: syntax error near unexpected token `newline' |
| 01:46.29 | keldwud | yeah, EOF\n |
| 01:46.33 | keldwud | that's a new line! |
| 01:46.38 | keldwud | so it IS interpreting it that way |
| 01:46.45 | keldwud | so go turn off the sh electric here document mode |
| 01:47.03 | harleypig | Not until I can change this structure. |
| 01:47.25 | harleypig | These if (<<<$filename ...) type tests are scattered throughout this project. |
| 01:47.49 | keldwud | oh man |
| 01:47.52 | keldwud | ooh |
| 01:47.57 | keldwud | maybe they did it in a different shell! |
| 01:48.12 | keldwud | like instead of bash, it was tcsh or something |
| 01:52.31 | keldwud | http://hyperpolyglot.org/unix-shells |
| 01:52.36 | keldwud | maybe this will help |
| 01:52.46 | keldwud | oh, nm |
| 01:52.58 | keldwud | you already got that far in finding out it was stdin from here-string |
| 01:55.51 | keldwud | okay maybe I was just overthinking it |
| 01:55.57 | keldwud | when I first read it, I read it as: |
| 01:56.10 | keldwud | it greps $filename for line ending in .wiki |
| 01:56.10 | keldwud | <PROTECTED> |
| 01:57.03 | keldwud | "<<<" will read to end of file when we reach it |
| 01:57.13 | keldwud | not when we start |
| 02:00.23 | keldwud | harleypig, |
| 02:00.26 | keldwud | I think we have an answer |
| 02:00.30 | keldwud | so it takes the docuement name and it prepends it to the variable |
| 02:01.26 | harleypig | what variable? |
| 02:02.09 | keldwud | FILENAME=file.txt |
| 02:02.09 | keldwud | <PROTECTED> |
| 02:02.09 | keldwud | <PROTECTED> |
| 02:02.09 | keldwud | <PROTECTED> |
| 02:02.09 | keldwud | <PROTECTED> |
| 02:02.14 | harleypig | ? Oh ... no, that doesn't make sense. Other wise <<<"some random text" cat - wouldn't work. |
| 02:02.24 | keldwud | "file.txt\nmycool.wiki\n" |
| 02:02.29 | keldwud | with \n being the new line |
| 02:03.27 | harleypig | $ <<<"some random text\n" cat - |
| 02:03.28 | harleypig | some random text\n |
| 02:04.19 | keldwud | a good example of what a here string is, is: |
| 02:04.19 | keldwud | <PROTECTED> |
| 02:04.19 | keldwud | that is without here string |
| 02:04.19 | keldwud | if grep -q "txt" <<< "$VAR" |
| 02:04.19 | keldwud | that is with having it |
| 02:04.24 | keldwud | not sure if I'm helping or not |
| 02:06.40 | keldwud | lets you not have to open a pipe |
| 02:06.44 | keldwud | is the gist, I think |
| 02:07.17 | harleypig | This? http://linux.die.net/abs-guide/x15683.html (or something like it) |
| 02:08.24 | harleypig | Ok, this is what I was looking for: COMMAND <<<$WORD, where $WORD is expanded and fed to the stdin of COMMAND. |
| 02:08.44 | harleypig | So, <<< is a token in and of itself, which is why <<> didn't work. |
| 02:12.44 | keldwud | the COMMAND is storing it in the variable |
| 02:13.18 | keldwud | https://www.irccloud.com/pastebin/hS3iq7Wl |
| 02:14.58 | keldwud | so << allows you to have new lines |
| 02:14.58 | keldwud | <<< does not |
| 02:14.58 | keldwud | wc << EOF |
| 02:14.58 | keldwud | do |
| 02:14.58 | keldwud | <PROTECTED> |
| 02:14.59 | keldwud | <PROTECTED> |
| 02:15.01 | keldwud | <PROTECTED> |
| 02:15.03 | keldwud | <PROTECTED> |
| 02:15.05 | keldwud | wc << EOF |
| 02:15.07 | keldwud | <PROTECTED> |
| 02:15.09 | keldwud | <PROTECTED> |
| 02:15.13 | keldwud | <PROTECTED> |
| 02:15.15 | keldwud | <PROTECTED> |
| 02:15.17 | keldwud | <PROTECTED> |
| 02:15.59 | keldwud | hope that helps? |
| 02:21.00 | harleypig | :] Yeah ... but <<< has no variable, the "string" after <<< is fed into STDIN |
| 02:21.16 | harleypig | But I understand it much better. |
| 02:26.59 | keldwud | did I make a good Wilson, then? :) |
| 02:27.00 | keldwud | woohoo! |
| 02:27.10 | keldwud | I cheated and got all those answers from friends |
| 02:27.22 | keldwud | but it's the results that matter, right? :) |
| 02:27.27 | keldwud | REBOOT |
| 02:28.23 | *** join/#utah T4rku5 (~T4rku5@unaffiliated/shunkydave) |
| 02:28.43 | *** join/#utah T4rku5 (~T4rku5@unaffiliated/shunkydave) |
| 02:29.34 | harleypig | =) |
| 14:25.14 | *** join/#utah gr3yR0n1n (~gr3yR0n1n@c-174-52-62-40.hsd1.ut.comcast.net) |
| 16:07.07 | *** join/#utah jnbek (~jnbek@pdpc/supporter/active/jnbek) |
| 16:56.45 | *** join/#utah davido_ (~davido@c-50-168-241-168.hsd1.ut.comcast.net) |
| 19:02.47 | levi | Heh, I'm pretty sure I've wanted something like <<< before but didn't realize it existed. |
| 19:02.51 | levi | I hate bash. :/ |
| 22:21.08 | frostyfrog | Sometimes C, sometimes... I wish I could hit you with a hammer... |
| 22:24.47 | levi | Please, hit C with a hammer. |
| 22:54.53 | frostyfrog | xP |
| 22:55.02 | frostyfrog | Found out, it was my fault. |
| 22:55.39 | frostyfrog | I was recursing through directories... Apparently I forgot to ignore . |
| 22:56.15 | frostyfrog | So ./././././././././././././././././<a crap ton lot more ./'s> was exceeding file name limits. xD |
| 22:56.58 | frostyfrog | Anyways, first broken release! Woohoo! No to figure out why Ubuntu & other distros are having such a rough time. https://github.com/frostyfrog/Renzoku |
| 22:57.49 | frostyfrog | made that public as of today. It's my first pet project to actually make it this far, really. |
| 22:59.59 | frostyfrog | I've told a few people from plug about that (incl. natgeorg? ) and I'm so stoked that it's working now :) |
| 23:00.39 | frostyfrog | goes to dance, so as to not bother this channel anymore. |