freebsd-doc Digest, Vol 639, Issue 5
Lee Brown
leeb at ratnaling.org
Sat Jul 4 16:32:42 UTC 2015
On Sat, Jul 4, 2015 at 5:00 AM, <freebsd-doc-request at freebsd.org> wrote:
> Send freebsd-doc mailing list submissions to
> freebsd-doc at freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-doc
> or, via email, send a message with subject or body 'help' to
> freebsd-doc-request at freebsd.org
>
> You can reach the person managing the list at
> freebsd-doc-owner at freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-doc digest..."
>
>
> Today's Topics:
>
> 1. [Bug 201303] c99(1) still says it's a wrapper around GCC
> (bugzilla-noreply at freebsd.org)
> 2. sh(1) man page suggestion: prompt string syntax (Mike Brown)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 03 Jul 2015 12:11:08 +0000
> From: bugzilla-noreply at freebsd.org
> To: freebsd-doc at FreeBSD.org
> Subject: [Bug 201303] c99(1) still says it's a wrapper around GCC
> Message-ID: <bug-201303-9 at https.bugs.freebsd.org/bugzilla/>
> Content-Type: text/plain; charset="UTF-8"
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201303
>
> Bug ID: 201303
> Summary: c99(1) still says it's a wrapper around GCC
> Product: Documentation
> Version: Latest
> Hardware: Any
> OS: Any
> Status: New
> Severity: Affects Only Me
> Priority: ---
> Component: Documentation
> Assignee: freebsd-doc at FreeBSD.org
> Reporter: bruce.cran at gmail.com
>
> In the STANDARDS section of c99(1), it says:
>
> "The c99 utility interface conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
> Since it is a wrapper around GCC, it is limited to the C99 features that GCC
> actually implements. See http://gcc.gnu.org/gcc-4.2/c99status.html."
>
> Since the project has switched from gcc to clang, that's no longer correct.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 3 Jul 2015 23:37:17 -0600
> From: Mike Brown <mike at skew.org>
> To: freebsd-doc at freebsd.org
> Subject: sh(1) man page suggestion: prompt string syntax
> Message-ID: <20150704053717.GA21782 at chilled.skew.org>
> Content-Type: text/plain; charset=us-ascii
>
> I was having trouble finding out what escape codes are valid in an sh(1)
> prompt. The man page does not say, so I looked at /usr/src/bin/sh/parser.c and
> determined what the options are. Please consider adding this info to the man
> page, /usr/src/bin/sh/sh.1 :
>
>
> A prompt string must be less than 128 characters. All characters are output
> verbatim, except these sequences:
>
> '$' is replaced with '#' if the user is root.
> '\h' is replaced with the local hostname.
> '\H' is replaced with the fully-qualified hostname.
> '\W' is replaced with the working directory.
> '\w' is replaced with the full path of the working directory.
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> freebsd-doc at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-doc
> To unsubscribe, send any mail to "freebsd-doc-unsubscribe at freebsd.org"
>
> ------------------------------
>
> End of freebsd-doc Digest, Vol 639, Issue 5
> *******************************************
It's there (please excuse the ugly regexp):
# man sh | grep "\\\\\(H\|h\|w\|W\\|\\$\)"
\H The local hostname.
\h The fully-qualified hostname.
\W The final component of the current working directory.
\w The entire path of the current working directory.
\$ Superuser status. ``$ '' for normal users and ``# ''
# uname -a
FreeBSD dc 10.1-RELEASE-p3 FreeBSD 10.1-RELEASE-p3 #4: Sat Jan 10
19:15:42 UTC 2015 root@:/usr/obj/usr/src/sys/GENERIC amd64
More information about the freebsd-doc
mailing list