Post History
I use man sh and then /^\s+read to get to the section of the man page that discusses the appropriate builtin. You can get a direct link to the Bash read in Debian's manpage site, which has this to...
#8: Post edited
by
Michael
·
2025-06-26T20:38:14Z (about 1 year ago)
- I use `man sh` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to the Bash `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
[The `sh` manpage](https://manpages.debian.org/bookworm/dash/sh.1.en.html) doesn't identify `read` as an important think to anchor, but you can still find it.- I personally find it kind of annoying that the shells' builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: As you noticed, you could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
- I use `man sh` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to the Bash `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
- [The `sh` manpage](https://manpages.debian.org/bookworm/dash/sh.1.en.html) doesn't identify `read` as an important thing to anchor, but you can still find it.
- I personally find it kind of annoying that the shells' builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: As you noticed, you could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
#7: Post edited
by
Michael
·
2025-06-26T20:34:40Z (about 1 year ago)
- I use `man sh` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to the Bash `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
- [The `sh` manpage](https://manpages.debian.org/bookworm/dash/sh.1.en.html) doesn't identify `read` as an important think to anchor, but you can still find it.
I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: As you noticed, you could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
- I use `man sh` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to the Bash `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
- [The `sh` manpage](https://manpages.debian.org/bookworm/dash/sh.1.en.html) doesn't identify `read` as an important think to anchor, but you can still find it.
- I personally find it kind of annoying that the shells' builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: As you noticed, you could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
#6: Post edited
by
Michael
·
2025-06-26T20:34:12Z (about 1 year ago)
I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.- You can get [a direct link to the Bash `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
- [The `sh` manpage](https://manpages.debian.org/bookworm/dash/sh.1.en.html) doesn't identify `read` as an important think to anchor, but you can still find it.
- I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: As you noticed, you could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
- I use `man sh` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to the Bash `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
- [The `sh` manpage](https://manpages.debian.org/bookworm/dash/sh.1.en.html) doesn't identify `read` as an important think to anchor, but you can still find it.
- I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: As you noticed, you could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
#5: Post edited
by
Michael
·
2025-06-26T20:33:19Z (about 1 year ago)
Explain why builtins are grouped into their parent's manpage
- I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
You can get [a direct link to `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: You could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
- I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to the Bash `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
- [The `sh` manpage](https://manpages.debian.org/bookworm/dash/sh.1.en.html) doesn't identify `read` as an important think to anchor, but you can still find it.
- I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: As you noticed, you could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
#4: Post edited
by
Michael
·
2025-06-26T20:29:34Z (about 1 year ago)
Explain why builtins are grouped into their parent's manpage
- I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but this is how it is.
- I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
- I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but one can imagine why this is important: You could be in Bash and run `sh -c 'read foo'` or something, which changes what `read` is able to do.
#3: Post edited
by
Michael
·
2025-06-26T20:19:51Z (about 1 year ago)
Link Debian manpage
- I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but this is how it is.
- I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- You can get [a direct link to `read` in Debian's manpage site](https://manpages.debian.org/bookworm/bash/bash.1.en.html#read), which has this to say about `-s`:
- > - **`-s`** Silent mode. If input is coming from a terminal, characters are not echoed.
- I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but this is how it is.
#2: Post edited
by
Michael
·
2025-06-26T14:52:09Z (about 1 year ago)
I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.
- I personally find it kind of annoying that the shell's builtins have a huge section devoted to them rather than being broken into multiple man pages, but this is how it is.
#1: Initial revision
by
Michael
·
2025-06-26T14:47:34Z (about 1 year ago)
I use `man bash` and then `/^\s+read` to get to the section of the man page that discusses the appropriate builtin.