Databases
StackOverflow2013
Postsdbo
PODifficulties with using variables with Ruby gsub call for block replace
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODifficulties with using variables with Ruby gsub call for block replace
    primarykey
    data
    text
    <p>What I'm trying to accomplish is replacing a block of text (not terminated by new lines) in a template-ish way. The block I want to replace looks something like this (to make this more readable, I've put variable values in block brackets):</p> <pre><code>[varA][varB]_begin[varC] content line 1 content line 2 ... [varA][varB]_end[varC] </code></pre> <p>And I want to replace everything including the first varA and the last varC.</p> <p>I put together a skeleton of the regular expression to match this. So, supposing, varA were "&lt;%" and varB were "block" and varC were "%>", the regular expression would need to be:</p> <pre><code>/&lt;%block_beg%&gt;(.*)&lt;%block_end%&gt;/m/ </code></pre> <p>I've confirmed that this pattern should work (via rubyxp)</p> <p>But of course its not that easy because the values we used for varA, varB, and varC in the previous examples need to be dynamically supplied.</p> <p>Given what I understand about Ruby's gsub(), in my estimation the following should work:</p> <pre><code> gsub(/#{@varA}#{@varB}_beg#{@varC}(.*)#{@varA}#{@varB}_end#{@varC}/m, old_str) </code></pre> <p>The code runs silently without throwing errors, but also doesn't replace anything. Can anyone tell me why this isn't working? Should I be taking a different approach?</p> <p>Post-Note 1: The @'s are due to the fact that the variables are class properties.</p> <p>Post-Note 2: I've fixed a few things and it is still not working. I now have:</p> <pre><code> @content.gsub(/#{Regexp.escape(@varA)}#{Regexp.escape(@varB)}_beg#{Regexp.escape(@varC)}(.*)#{Regexp.escape(@varA)}#{Regexp.escape(varB)}_end#{Regexp.escape(@varC)}/m) </code></pre> <p>Anyone know why that doesn't work?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMark Nenadov
    1. USMark Nenadov
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODifficulties with using variables with Ruby gsub call for block replace
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTechnically speaking in specific instance that I am working on, they should all have @'s, because they are properties of a class.
      singulars
      1. PODifficulties with using variables with Ruby gsub call for block replace
      1. USMark Nenadov
    2. COI'd recommend refactoring and replacing your ivars which you want interpolated with a Hash. Then just iterate through the hash and gsub every key with value.
      singulars
      1. PODifficulties with using variables with Ruby gsub call for block replace
      1. USMladen Jablanović
    3. COFirst, create your regexp and assign it to a variable, and then `p myregexp`. See what regex you are actually running. My guess is that your instance variables are `nil`, whose `#to_s` is an empty string, and so your regex is `/_beg(.*)_end/m`.
      singulars
      1. PODifficulties with using variables with Ruby gsub call for block replace
      1. USPhrogz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload