Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with formatting
Search options not deleted
user 380318
4
votes
Accepted
Should a short error message be formatted as inline code, bold or simply with double quotes?
Code formatting should be reserved for (surprise!) code, or things that are generally displayed as monospace, especially if they're not English-like. … In that case, you should use code formatting. Compare this:
finagle : The term 'finagle' is not recognized as the name of a cmdlet, function, script file, or operable program. …
- 41.7k