Date: Tue, 03 Jul 2018 07:42:22 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229472] man echo misses -e option Message-ID: <bug-229472-227-OxxpYEmYDV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229472-227@https.bugs.freebsd.org/bugzilla/> References: <bug-229472-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229472 --- Comment #5 from Torsten Zuehlsdorff <tz@freebsd.org> --- (In reply to Conrad Meyer from comment #4) > Jamie hits the nail on the head. And I guess we're already explicit > about this: I tend to disagree ;) When using "man alias" for example, we get the builtin manpage. This is true for every builtin i every tried the last years. "man echo" is the only manpage for an builtin. Also the statement is not too helpful. While i am able to figure out which shell i am using: many users are not. Also the builtin manpage itself is not very helpful. It redirects me to the next manpage of the shell itself (after g. So my workflow is: 1) man echo 2) man builtin 3) man bash And every manpage is getting more complex and harder to understand. Beside the fact, that its possible to use different echos (if i read the buildin manpage correct?). In conclusion: maybe its fine from a technical point of view. From a user point of view it is very confusing. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229472-227-OxxpYEmYDV>