Floating numbers should have thousand separator with specifier 'n' like python.

Python:

>>> from locale import setlocale, LC_ALL
>>> setlocale(LC_ALL, 'en_US')
'en_US'
>>> '{:n}'.format(1234)
'1,234'
>>> '{:n}'.format(1234.56)
'1,234.56'

C++

setlocale(LC_ALL, "en-US");
fmt::format("{:n} {:n}", 1234, 1234.56);
// gives 1,234 1234.56

func commonInit() {
        self.title = "Choose your country"   

public override func tableView(_ tableView: UITableView, titleForHeaderInSection section: Int) -> String? {
        if isFiltering {
            return nil
        } else if section == 0, hasCurrent {
            return "Current"
        } else if section == 0, !hasCurrent, hasCommon {
            return "C

I cannot succeed setting the language in numbro, with language.min.js included. I'm using the CDN-include. What am I doing wrong?

HTML

<div id="number"></div>

JS

numbro.setLanguage("de-DE");
var number = numbro("1111111111").format({thousandSeparated: true});
document.getElementById("number").innerHTML = number;

The result should read

I would be neat if you could specify a max width for columns and/or tables and have prettytable automatically truncate strings (and probably add a configurable indicator like ...) that exceed that length.

function Foo() {
  return <div />
}

export default React.memo(Foo);

Results in:

<[object Object] />

See facebook/react#14319

Opening an issue here to track the progress, and see what we can do.
The thing is we need the displayName not only for DEV env, but also production.

Pretty much like PROBLEMS window, there should be a specific tab for COMMENTS (much like a TODO list)

There're probably quite a few questions on StackOverflow about formatting in console, tables, colors and word wrap. Find them and help people find the one and only correct solution.

And don't copy-paste answers like the last time. Don't be that stupid, you dirty rep whore. You have 25K rep, it's time to pretend you have brains.

May be add 4 space after proxy_set_header for improve readability?
Before

    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Server $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Real-IP $remote_addr;

After

    proxy_set_he

The BlueStyle conventions are great!

I was wondering if people would be interested in discussing adding some guidelines on when to use export and how that relates to the current section on using using and import. Additionally, it would be nice to clarify if how this guideline on

How to reproduce:

• Netbeans formatting: 4 space

• .editorconfig:

[*]
indent_style = space
indent_size = 2

Current result:
pressing tab results in 4 spaces

Expected result:
pressing tab results in 2 spaces

See https://github.com/rust-lang/rustfmt