Testing the basic coding stuff

I’m a 99er and for some reason, some basic coding isn’t working. I know I can click in the above menu to Cartooniverse <----bold that name. And yet, in Preview, it’s not bolded.

If I use the old-school method of brackets and Bs, it appears to work here in this test thread. Yet, in regular threads ( as was just the case a few moments ago ), bolding a member’s name as I write doesn’t deliver the name bolded in my post. It’s a small thing, but it’s a shame.

How do I fix this? And, is there a coding method whereby I can write out a member’s name and they know I’ve mentioned their name in my post?

If I use the brackets/ bolding, I get [ b ]Cartooniverse[ / b ] to work when typed out without spacing: Cartooniverse .

Frustrating. I cannot discern if it’s bolding or not. Which is in and of itself weird.

What’s the Straight Dope on coding? Where do I find the list of basic hand-typed codes to modify as I write?

Many thanks.

This might be a better fit for the Site Feedback forum, since that’s where questions and discussions about the Discourse software seem to belong.

I’m not sure what you’re having trouble with. The “old-school method of brackets and Bs” should work to make text boldface. In your OP, I see your name bolded both places it should be (and not in the place where you left the spaces in the brackets). Alternatively, you can surround the word to be bolded with double asterisks (single asterisks get you italics).

I agree that there ought to be a “basic list of hand-typed codes” but I’m not sure where.

For that, you want to precede the name with an @ sign. If you type an @ and then keep typing, Discourse will even suggest autocompletes (I think it lists folks in the thread first, then all matching members, maybe sorted by how active they are).

Like this: @Cartooniverse . Which I typed with an @ symbol, then a C, then tab to autocomplete it.

The user will get notified if you do this, so that they know someone’s talking to or about them. Often this is what you want, but if it’s not, you can use “regular” boldfacing.

My Edits.

Wow. When I SEE my post in this thread, nothing is Bolded. Hmph.

@Chronos, thank you for that tip !! Will deploy with great alacrity.

I’m bolding your name here: Cartooniverse. And now I’m @-ing you: @Cartooniverse (which to me looks not bolded but with a gray background).

I maybe have a vague memory of people complaining that, in at least one of the “themes,” bolding doesn’t show up very well, but I don’t remember which. You could try switching your theme and see if that has an effect.

To change your theme (at least from a computer), click your avatar (next to the three-lines “hamburger” menu), then click “Preferences” (the head-and-shoulders icon), click “Preferences” again on the screen that comes up (which has a “gear” icon next to it), select “Interface,” choose a theme from the drop-down menu, and click Save Changes.

At least, that’s how I found it. The theme I use is “Straight Dope Light,” which I think is closest to the way the board looked back in the vBulletin days.

There is a guide here:

If you google “discourse text formatting” it’s not the first thing that shows up, but it is on the first page of google results.

Looking through it, I do see one error. Quote tags need to be on a line all by themselves. You can’t put the quote tags inline the way it says on that page. Everything else looked correct, but I did only take a quick glance at it.

The way I typically bold things is just to highlight it with my mouse or cursor and then press CTRL-B. Discourse will put two asterisks on either side of what you have selected to make it bold. You can also just type the asterisks yourself.

If the text doesn’t look bold, that may be an issue with whatever theme you are using or with your particular browser and operating system or device.

I actually found that page but hesitated to recommend it because the error you note jumped out at me and made me wonder what else there was untrustworthy.

That was quote tags on the same line. Which does work, but only if what’s quoted is also all one line (i.e., has no returns in it). A number of other tags also work that way: They can either be all one line, or the tags each on a line by themselves, but no combination.

this = code

So { is this }, but it was supposed to be multiple lines, but I put the tags next on the same line as other stuff.

Here{
 the tags;
 are each on their;
 own line;
}

My Edit of your post above.

Yes- it may well be the theme. I always prefer the darkest themed backgrounds. Across all software platforms. There is no hard evidence that bluelight from monitors damage the retinas, but I do find a pure white background to be hard on my eyes. Going with the darkest theme possible is easier to look at, for me. That said- the dark theme here may well eliminate the perceived bolding I’ve been using in my posts that others say they can see. --Shrug-- I can live with that.

As always, thanks for the detailed info, engineer_comp_geek