@toksyuryel
Renton
Some kind of otherkin dragon thing who thinks he'll be a professional programmer someday.
Favorite pony is Pinkie Pie, but Luna is best pony. Figure that one out.
Notices by Toksyuryel (toksyuryel), page 12
-
@bitshift And that's just screencast.sh. common.sh is another 29 lines on top of that.
-
437 lines. This is probably big enough now that I should add a GPL notice to it.
-
@neurario Specifically, Twitter is not a social network.
-
@neurario One of these things is not like the other.
-
@scribus Could probably include "A Canterlot Wedding" in that list too, now that I think on it.
-
@scribus I generally use "Boast Busters" and "Putting Your Hoof Down" as a yardstick for what's acceptable. Do you feel that's accurate?
-
@scribus I assume I know where the line is, but I've been wrong before.
-
@snowcone Not really. Pretty vanilla if you ask me.
-
@scribus Yeah
-
@scribus Gandi~
-
What I need is a text parser. Thinking logically, the shell already has a text parser which it uses to strip comments. I may be able to circumvent the problem entirely if I can figure out how to use that directly.
Monday, 04-Feb-13 14:32:17 UTC from web -
Notably, vim's syntax highlighting is able to handle that file just fine if it's saved with a .sh extension. If I am not mistaken, vim's syntax highlighting is regex-based, so perhaps if I have a glance at the syntax files I will find my answer.
Monday, 04-Feb-13 14:25:40 UTC from web -
@bitshift Here's the file I made for testing with http://bpaste.net/show/74997/
-
@bitshift No amount of lookaround will satisfy this case: VAR="quoted value" # comment with an "embedded quote" in it
-
@bitshift I have recognized a flaw in my comparison idea which basically means it's not going to work anyway even if there was a way to do it that way. It looks like what I actually need to do is count up the number of quotes, and only match if an even number of quotes precedes the first # and I don't think that's something a regular expression can do. Time to break out awk.
-
-
@bitshift According to that article, you can't use repetition or optional items inside a lookbehind.
-
@bitshift sed actually
-
@mrdragon If you take them off you're doing it wrong.
-
I wish @minti hadn't abandoned !mintrefresh =/ it was more than just a refresh script, and the additional parts of it still haven't been merged into !rdnplus.
Monday, 04-Feb-13 12:32:26 UTC from web -
@bitshift Sounds good *hug*
-
@mrdragon I thought you wanted Spitfire, not wanted to BE Spitfire?
-
@bitshift You didn't allow for any characters to separate the quotes and the #
-
@bitshift This will match when there is a quote character after the # even if there isn't one before it. (I am being generous here- this actually barely matches anything at all, but I understand what you meant to type)
-
@mrdragon Let me just slip into this Spitfire costume…
-
@bitshift I recognize that this breaks when a quote is escaped, but I'd like to take this one step at a time (and I found a snippet that allows for escaped quotes so hopefully finding the solution to the simpler problem will teach me whatever I need to know to work that into the final result).
-
@bitshift The string to match is '\s*#.*' and the string to not match is '".*#.*"'
-
@bitshift The problem arises from needing to check that the string to match is not contained within the string to not match. Specifically, I am trying to match the first # symbol that is not inside quotes.
-
Anyone good at regular expressions? How do I say "match this string unless it also matches this other string"?
