I've come to a better understanding of how expansion occurs and now
realize that this is not a bug.
Thanks to Chet for his time in responding to my messages.
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
[EMAIL PROTECTED] wrote:
> I had been using ${HOSTNAME%%.*} in my prompt to show the local
> host name portion of my full host name (e.g. localhost instead
> of localhost.localdomain). After enabling the nullglob shell
> option, this pattern is being replaced by a n
On Sat, 2005-07-02 at 12:24 -0400, Chet Ramey wrote:
> Michael Wardle wrote:
> > Hi Chet
> >
> > Thanks for your very prompt reply.
> >
> > I understand that globbing is happening, but I don't understand why
> > deleting a parameter should occur with nullglob set if the parameter
> > matches but
Michael Wardle wrote:
> Hi Chet
>
> Thanks for your very prompt reply.
>
> I understand that globbing is happening, but I don't understand why
> deleting a parameter should occur with nullglob set if the parameter
> matches but the word to delete doesn't. The bash behavior seems to make
> this c
> I also noticed in the POSIX standard that quoting the word part should
> cause it to be literal and prevent globbing. If I try this in bash, I
> get the same result as in my original message, that is:
>
> $ shopt -s nullglob
> $ connectioninfo='${HOST%%".*"} ${USER}'
> $ echo $connectioninfo
>
Hi Chet
Thanks for your very prompt reply.
I understand that globbing is happening, but I don't understand why
deleting a parameter should occur with nullglob set if the parameter
matches but the word to delete doesn't. The bash behavior seems to make
this construct useful only for file name del
[EMAIL PROTECTED] wrote:
> Bash Version: 3.0
> Patch Level: 16
> Release Status: release
>
> Description:
> I had been using ${HOSTNAME%%.*} in my prompt to show the local
> host name portion of my full host name (e.g. localhost instead
> of localhost.localdomain). After
