Re^4: Broken cpan shell

I thought about it, but it's not just a matter of one small strike-through over misspelling.

Your reply begins with a clear reference to a typo and the edited version of the OP now clearly states that a typo has been corrected. I didn't think anyone would be confused by your suggested correction, by what it refers to, by how it makes sense, or think any less of your advice. It is followed by me posting outcome of a correct command and then another person's suggestion to edit the OP, which I did. Sorry if I slighted you in the process.

Comment on Re^4: Broken cpan shell

Replies are listed 'Best First'.
Re^5: Broken cpan shell by kcott (Archbishop) on Jan 16, 2019 at 06:13 UTC
It's not that I feel slighted. The issue is that viewers of this thread, who come to it after your change, will be confused. I indicated changing '`-MCAN`': I've just done a search of the entire thread; my response is currently the only place where '`-MCAN`' exists. In terms of striking out large tracts of content, that certainly does happen. Something like this is not that unusual: Sorry, I completely misread your question. Please ignore. ... original text ... `... original code ...` [download] If you feel that the stricken content is likely to be highly distracting, consider hiding it with `<readmore>` or `<spoiler>`. Perhaps something like: Oops! I got that terribly wrong. The original content is in the spoiler; the intended (better) content follows: <Reveal this spoiler or all in this thread> ... better text ... `... better code ...` [download] — Ken	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Broken cpan shell
by kcott (Archbishop) on Jan 16, 2019 at 06:13 UTC

It's not that I feel slighted. The issue is that viewers of this thread, who come to it after your change, will be confused. I indicated changing '-MCAN': I've just done a search of the entire thread; my response is currently the only place where '-MCAN' exists.

In terms of striking out large tracts of content, that certainly does happen. Something like this is not that unusual:

Sorry, I completely misread your question. Please ignore.

... original text ...

... original code ...
[download]

If you feel that the stricken content is likely to be highly distracting, consider hiding it with <readmore> or <spoiler>. Perhaps something like:

Oops! I got that terribly wrong. The original content is in the spoiler; the intended (better) content follows:

... better text ...

... better code ...
[download]

— Ken

[reply]
[d/l]
[select]