page request: document stderr to stdout

[corneliusroemer]

Command description

I keep forgetting how to redirect stderr to stdout - would it be possible to document this in tldr in some way?

Not sure what the best way would be since this isn't quite a normal command but a bash inbuilt.

Any clues?

2>&1

Command details

No response

OS

• [ ] Android
• [X] Linux
• [X] macOS
• [ ] sunOS
• [ ] Windows

[navarroaxel]

@waldyrious wdyt?

[corneliusroemer]

Maybe we could create a command stderr? Has anyone ever added bash intrinsics to tldr?

[CleanMachine1]

We have a [[ page. Can this be even called a command more than just a syntax feature of bash.

I think we could add this as tldr 2>&1 and maybe think about documenting such features as && as well.

[EmilyGraceSeville7cf]

I keep forgetting how to redirect stderr to stdout - would it be possible to document this in tldr in some way?

It will be possible only when it will be explicitly permitted by our client specification. Now it literally states the following:

tldr-pages consists of multiple pages - each of which describes a specific command.

By all means, redirection can be shown in some tldr pages but it's unclear what page to use to find i/o redirection syntax. So my point is: update client specification if users need such syntax features to be shown separately from usual tldr pages. Personally I like the idea to demonstrate some shell syntax features separately.

[Managor]

We now have the pages that document this: https://github.com/tldr-pages/tldr/pull/13846