I am open to this. There are quite a log of places an URL gets displayed. One place I am particularly aware of is in show_diagnostics, enough that I put in a warning Note: some output may contain passwords. Redact before sharing..

I suggest move the masking code into a function, say display_masked_url, so it can be used in more places.

I am open to this. There are quite a log of places an URL gets displayed. One place I am particularly aware of is in show_diagnostics, enough that I put in a warning Note: some output may contain passwords. Redact before sharing..

I suggest move the masking code into a function, say display_masked_url, so it can be used in more places.

Good idea, I have changed this. Could you please have a check? I also changed the download URL in diagnostics to avoid any password leakage.

The quotes are a bit tricky with the nesting!

(Closed by mistake.)

I misunderstood a couple of the uses, so added suggestions to preserve the original style.

I was worried about spaces in password, but now I remember username and password need to be url-encoded for robustness anyway: https://github.com/tj/n/blob/master/docs/proxy-server.md

However, adding the quotes around the variable expansions fixes warnings from shellcheck so I would have wanted the changes anyway.

Thanks @jinxiao

Released in v10.1.0