Re: How to match regex in bash? (any character)

2011-09-30 Thread Roger
> On Fri, Sep 30, 2011 at 06:20:32AM +, Stephane CHAZELAS wrote:
>2011-09-29, 13:52(-08), Roger:
>[...]
>> Since you're saying the regex description is found within either regex(3) or
>> regex(7), couldn't there be a brief note within the Bash Manual Page be 
>> something
>> to the effect:
>[...]
>
>No, it's not.
>
>I suppose bash could say: See your system regex(3)
>implementation documentation for the description of extended
>regular expression syntax on your system. That syntax should be
>compatible with one version or the other of the POSIX Extended
>Regular Expression syntax whose specification for the latest
>version as of writing can be found at:
>http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_04
>
>regex(3) points to the API (regex.h), how the system documents
>the regexps covered by that API is beyond bash knowledge.


Exactly, a simple "man regex" (aka regex(3)) points to regex.h here.  Few will
know how to search for the regex(7) manual file.

-- 
Roger
http://rogerx.freeshell.org/



Bug: shell history loses lines beginning with # in a here-document

2011-09-30 Thread Jonathan Wakely
[I've just created a bug report at Savannah, but looking at the Bash
page on gnu.org I realised it should have ben sent here rather than
]

Run these command:

$ gcc -x c - <
 int main() { printf("hi\n"); }
 EOT
$ ./a.out
hi

now use the up cursor (or "fc -2" or any equivalent) to return to the
gcc command, it has been
mangled to:

gcc -x c - <

Updating Bash port on VMS

2011-09-30 Thread John E. Malmberg

Hello,

I and others are working on updating the bash port on VMS the current 
version of Bash.


As this port can not depend the pre-existence of Bash or other common 
tools, I will end up with a number of additional VMS specific files. 
This includes build scripts and various helper modules, and documentation.


I would like to collect those files into a VMS specific directory, and 
would like to know where to put that directory in the current tree for 
when the port is complete and I can start submitting patches.


The work is being based on the 4.2 release + patches.

Regards,
-John