In Writeboard, if you enter -- (two normal dashes/hyphens), it gets displayed as — (one em-dash).

That's probably fine and cool in most cases, but gets annoying if you'd want to document e.g. Unix commands—like wget —auth-no-challenge—for copy-pasting them later. This breaks down with the "clever" em-dash conversion.

I found a clumsy workaround: write the two dashes like -<b></b>- or -</b>- in the page source. Is there any better way to avoid Writeboard converting the dashes? Using <pre> tags for verbatim formatting doesn't seem to help in this case.

  • "As part of refocusing on Basecamp, we’ve decided to retire Writeboard.com. You’ll still be able to create Writeboards inside Basecamp Classic and Backpack, but you’ll no longer be able to start new stand-alone Writeboards here at Writeboard.com."
    – ale
    Commented Oct 31, 2015 at 15:48

1 Answer 1


Writeboard uses Textile as it's markup language, with limited HTML support. In Textile, inline code blocks can be created like this:


or, using HTML:


Both of which are equivalent when processed. It's analogous to Markdown's (used here for all StackExchange sites) `Code` style. The results of these is:

alt text

The actual code used to produce the above screenshot is:

Use the <code>--flag</code>, such as <code>wget --auth-no-challenge</code>

Textile should support @wget --auth-no-challenge@ or @--flag@
  • Great, thanks! I couldn't get @code@ working in Writeboard, but <code> works fine.
    – Jonik
    Commented Nov 6, 2010 at 10:49
  • @Jonik That's odd, I managed to get @code@ working. The second line in the screenshot was actually created with that markup
    – Yi Jiang
    Commented Nov 6, 2010 at 11:13
  • Can you give a more complete example of using @code@? Something that illustrates where the code block starts and ends.
    – Jonik
    Commented Nov 6, 2010 at 11:19
  • Ah, now I get it. :-) (Stupid user error: I tried things like @code@ --, thinking maybe it behaves like Writeboard's bq.) Thanks again!
    – Jonik
    Commented Nov 6, 2010 at 11:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.