I was trying to point out that filenames passed to FOPEN by ANY app can
contain embedded !varname.  In this case the !varname is not even seen
by the CI.  So I guess that "!" has become a file system meta character!

Jeff V.


On Apr 25,  8:01pm, Jeff Kell wrote:
> Jeff Vance wrote:
> >
> > Another consideration is that you can supply "!varname" in the middle
> > of a filename passed to fopen.  If we make the APIs unaware of
> > escaping rules, how do we: a) retain this functionality, or b) support
> > "!" in filenames?
>
> The "!" in the CI is more of a meta-character, like shell metas.  I
> would expect it to be escaped like shell metas, e.g.:
>
>     :file mpe=!varname            works as now, substitute varname value
>     :file mpe=\!posixname         references "!posixname"
>
> Granted the "!" is somewhat used as an "escape" now, like in the common
> setvar hpprompt "!!hpgroup.!!hpaccount", or to bypass CIOR (!< and !>)
> but this is overloading things a bit.


--