It would be nice if the freelinking filter left codeblocks alone.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | freelinking.patch | 1.65 KB | nigelcunningham |
| #2 | freelinking.patch | 1.62 KB | nigelcunningham |
It would be nice if the freelinking filter left codeblocks alone.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | freelinking.patch | 1.65 KB | nigelcunningham |
| #2 | freelinking.patch | 1.62 KB | nigelcunningham |
Comments
Comment #1
Grayside commentedComment #2
nigelcunningham commentedHere is a patch that implements that. It works by splitting the string to be freelinked into parts, using opening and closing code tags. It then rebuilds the string, applying the original _freelinking_do_filtering function only to parts that fall outside the code tags. Nested code tags are handled correctly.
Works for me with the markdown module, but the markdown module needs to have a lower weight (run first).
Comment #3
nigelcunningham commentedSmall correction.
The first version didn't apply the filtering function to text prior to the first opening code tag, and I was too busy focusing on the harder parts of the problem :)
Comment #4
juampynr commentedShall we go ahead and work on this? I guess we could make it more flexible by adding a setting in the admin form to ignore text within certain tags (ie. code).
Comment #5
gisleFour years has passed, and there has not been a second request. I'd say this feature does not have enough traction to be worth implementing, given that it makes a complex regexp even more complex.