| Summary | Code block title |
| Queue | Wicked |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | ben (at) |
| Requester | ben (at) |
| Created | 06/19/2005 (7488 days ago) |
| Due | |
| Updated | 07/16/2005 (7461 days ago) |
| Assigned | |
| Resolved | 07/16/2005 (7461 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Stalled
Assigned to ben
I'll update this ticket accordingly.
State ⇒ Feedback
Paul we can still extend our own code render rule.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Code block title
Queue ⇒ Wicked
State ⇒ New
blocks. An example of how this would be useful is for specifying a
filename in howto documents, so the reader can easily determine which
file this code belongs in. I envision displaying the file name in
italics, either directly above, or directly below the code block, with
little or no padding. Though, the details are open to discussion, of
course.