Loading...
 
Skip to main content

Features / Usability


text cmd problems

I'm running 1.9.2 on a hosted service with shell access, so fix options are limited.

When entering text and trying to use CamelCase commands, most of the commands don't work correctly. foo gets you blue text; foo gets you the link, but without the color. **foo** doesn't result in bold face text. "foo" doesn't get you italics. foo does get you underlined text.

Anyone got any idea how I can get all the commands to work properly?

tnx

eyore15
(mark miller)

posting for corrections once I saw how it rendered and correcting typo

Line one should read NO shell access — that's what the original draft says, but for some reason the final version isn't the same.

Line four after italics should read (double underscore) foo (double underscore) doesn't get you underline text but rather bold face. foo

> I'm running 1.9.2 on a hosted service with no shell access, so fix options are limited.
>
> When entering text and trying to use CamelCase commands, most of the commands don't work correctly. foo gets you blue text; foo gets you the link, but without the color. **foo** doesn't result in bold face text. "foo" doesn't get you italics. (double underscores)foo does get you underlined text.
>
> Anyone got any idea how I can get all the commands to work properly?
>
> tnx
>
> eyore15
> (mark miller)


Check your wikik syntax. See thisQuestion and thisQuestion FAQ for details.

HTH,

-RickQuestion

> I'm running 1.9.2 on a hosted service with shell access, so fix options are limited.
>
> When entering text and trying to use CamelCase commands, most of the commands don't work correctly. foo gets you blue text; foo gets you the link, but without the color. **foo** doesn't result in bold face text. "foo" doesn't get you italics. foo does get you underlined text.
>
> Anyone got any idea how I can get all the commands to work properly?
>
> tnx
>
> eyore15
> (mark miller)