Defect #6376
open
Turning off textile inline with '==' doesn't work.
Added by Noah Diewald over 13 years ago.
Updated about 11 years ago.
Description
At http://www.textism.com/tools/textile/index.php if I enter:
==-test== is ==test-==
-test is test-
I get:
<p>-test is test-</p>
<p><del>test is test</del></p>
In Redmine this produces:
test is test
test is test
Or:
<del>test is test</del>
<p><del>test is test</del></p>
This is really bad news for me because I have a bunch of linguists that want to use familiar notations to talk about prefixes and suffixes and this useless delete formatting can't be simply turned off as it can be in normal textile, my only other alternative being to suggest the use of @'s, which change the font and have different meanings.
You can use < code >...< /code > (only around the dashes) or < notextile >...< /notextile > (around the whole words/characters combination) as a workaround.
Note: I've added some extra spaces to prevent incorrect parsing here.
- Status changed from New to Closed
- Resolution set to Wont fix
Please reopen if the above mentioned syntax doesn't suit your needs.
- Status changed from Closed to Reopened
I suppose some arguments for including would be the following.
Part of the nice thing about using textile is that one doesn't have to use verbose syntax to do simple things.
Another nice thing about textile is that it is widely used and so its often unintuitive syntax is at least familiar. Why not implement the that works in other textile systems?
There must be other people who would like to have an easy way to temporarily turn off textile for a portion of text in a manner that is predictable based on their experience with textile in other programs.
I have people reporting issues and commenting on issues that are relatively uncomfortable with markup in general. Maybe that isn't the target user base but it seems that I can't be the only one. == seems easier to sell to them than < notextile >...< /notextile >.
I guess a related issue is that == does have some significance to the system since it will disappear when used -- as I accidentally had happen above in my previous comment -- but at the same time doesn't do what you'd expect it to. That seems like a real bug. I spent a long time trying to figure out what I was doing wrong when using it before realizing that it just doesn't work. If the == remained uninterpreted then I would have realized the feature was unimplemented immediately.
Supported in RedCloth 4. More about RedCloth 4: #6269
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by