On 8/10/15 2:30 PM, Arthur20 wrote:
> Bash Version: 4.3
> Patch Level: 30
> Release Status: release
>
> Description:
> Bash has different escape syntaxes for `echo -e`, `printf` and
> `$'ANSI_C_style_escape'`. Take a specific point, `printf` and `$'C_Style'`
> accepts octals not starti
On 8/9/15 1:37 PM, aixtools wrote:
> Hi,
>
> Via google I came across the define named
>
> config-top.h:/* #define SYSLOG_HISTORY */
>
> Changing it (manually) to
> config-top.h:#define SYSLOG_HISTORY
>
> Adds syslog statements such as:
> Aug 9 16:52:55 x064 user:info syslog: HISTORY: PID=2622
Greg Wooledge wrote:
> Juanma wrote:
> > > [ is an ordinary command (a "shell builtin")
> >
> > Here is another point I find confusing: I thought a "shell builtin" didn't
> > have a separate binary executable file, like 'cd' (which cd => fail), but
> > some of them do have such form (which [ => /u
On 08/10/2015 12:30 PM, Arthur20 wrote:
> Configuration Information:
> Machine Type: i686-pc-cygwin, i686-pc-msys, x86_86-linux-gnu,
> x86_64-Apple-Darwin
>
> Bash Version: 4.3
> Patch Level: 30
> Release Status: release
>
> Description:
> Bash has different escape syntaxes for `echo -
Configuration Information:
Machine Type: i686-pc-cygwin, i686-pc-msys, x86_86-linux-gnu,
x86_64-Apple-Darwin
Bash Version: 4.3
Patch Level: 30
Release Status: release
Description:
Bash has different escape syntaxes for `echo -e`, `printf` and
`$'ANSI_C_style_escape'`. Take a specific po
At 2015-08-11 01:29:42, "Chet Ramey" wrote:
>Have you considered reading the man page or perhaps the info doc? That's
>where the actions are documented:
>
> -A action
> The action may be one of the following to generate a
> list of possib
On 8/10/15 12:02 PM, Arthur20 wrote:
> Bash Version: 4.3
> Patch Level: 30
> Release Status: release
>
> Description:
> Bash has incomplete documentation for builtins in `complete.def`. The
> [-abcdefgjksuv] options to specify
> types to complete are not documented. This is makin
You can add `-DSYSLOG_HISTORY` to your CFLAGS for building.
And for formatting, apply this patch:
--- bashhist.c 2015-08-11 00:09:38.449468800 +0800
+++ bashhist.c 2015-08-11 00:09:42.970623400 +0800
@@ -713,12 +713,12 @@
char trunc[SYSLOG_MAXLEN];
if (strlen(line) < SYSLOG_MAXLEN)
-sy
Configuration Information:
Machine: i686
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin' -DCONF_VENDOR='pc'
-DLOCALEDIR='/usr/local/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H
-DRECYCLES_
On 08/10/2015 02:18 AM, Juanma wrote:
> Here is another point I find confusing: I thought a "shell builtin" didn't
> have a separate binary executable file, like 'cd' (which cd => fail),
Actually, POSIX requires that there be a separate 'cd' binary, although
it does not have to behave the same a
On Mon, Aug 10, 2015 at 10:18:52AM +0200, Juanma wrote:
> > [ is an ordinary command (a "shell builtin")
>
> Here is another point I find confusing: I thought a "shell builtin" didn't
> have a separate binary executable file, like 'cd' (which cd => fail), but
> some of them do have such form (whic
El Fri 7 of Aug, Greg Wooledge profirió estas palabras:
> > Those brackets I cited above: ( expression )
> In the US we call those "parentheses", and we reserve the word "brackets"
> (or "square brackets") for [ ]. I realize that the UK uses different
> terminology. Hence, the word is ambiguous a
12 matches
Mail list logo
