From WikiChip
Editing mirc/regex
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.
Latest revision | Your text | ||
Line 195: | Line 195: | ||
In the above example, the outer '''$regsubex''' will make the regex match, then it will loop on the result and replace ''\t'' accordingly everywhere in the subtext. Notice the subtext of the outer '''$regsubex''' is: | In the above example, the outer '''$regsubex''' will make the regex match, then it will loop on the result and replace ''\t'' accordingly everywhere in the subtext. Notice the subtext of the outer '''$regsubex''' is: | ||
<source lang="mIRC">$regsubex(\t,/(.)/g,$upper(\t))</source> | <source lang="mIRC">$regsubex(\t,/(.)/g,$upper(\t))</source> | ||
− | All occurences of '''\t''' (can appear anywhere and it can be touching others characters) are changed with their corresponding $N value, even the one inside '''$upper'''; this means that the code won't work as expected. | + | All occurences of '''\t''' (can appear anywhere and it can be touching others characters) are changed with their corresponding $N value, even the one inside '''$upper'''; this means that the code won't work as expected. Instead, the '''\t''' inside '''$upper''' needs to be the value of the matched text of the ''inner'' '''$regsubex''', ''not'' the outer one. |
− | The idea is to get mIRC to see something other than '''\t''' | + | The idea is to get mIRC to see something other than '''\t''' when looking at this marker inside $upper, from the outer '''$regsubex''' context. |
A simple $+ cannot be used: | A simple $+ cannot be used: | ||
<source lang="mIRC">$regsubex(\t,/(.)/g,$upper( \ $+ t ))</source> | <source lang="mIRC">$regsubex(\t,/(.)/g,$upper( \ $+ t ))</source> | ||
− | Having this as the subtext of the $regsubex would end up calling '''$upper(\t)''' with plain text "\t", because the '''$+''' is going to be evaluated | + | Having this as the subtext of the $regsubex would end up calling '''$upper(\t)''' with plain text "\t", because the '''$+''' is going to be evaluated at the same time '''$upper''' is evaluated, which is after both $regsubex looked for markers. Something need to be done before the markers are replaced. |
− | The solution is to use the '''<nowiki>[[ \ $+ t ]]</nowiki>''' construct: | + | The solution to this issue is to use the '''<nowiki>[[ \ $+ t ]]</nowiki>''' construct: |
<source lang="mIRC">$regsubex(name,abcdefcdab,/(cd)/g,$regsubex(\t,/(.)/g,$upper( [[ \ $+ t ]] )))</source> | <source lang="mIRC">$regsubex(name,abcdefcdab,/(cd)/g,$regsubex(\t,/(.)/g,$upper( [[ \ $+ t ]] )))</source> | ||