[openbox] problems with tilde characters in commands

[Knute]

--- On Mon, 4/6/09, Dana Jansens <danakj at orodu.net> wrote:

> From: Dana Jansens <danakj at orodu.net>
> Subject: Re: [openbox] problems with tilde characters in commands
> To: "openbox mailing list" <openbox at icculus.org>
> Date: Monday, April 6, 2009, 9:58 PM
> 2009/4/6 Anthony Thyssen <A.Thyssen at griffith.edu.au>:

<cut>
> > As such the only working solution thus far is the very
> horrible
> > work around of.
> >
> >    bash -c "xte 'usleep 500000'
> \\\
> >        'str
> http://www.cit.gu.edu.au/'`printf
> '\176'`'anthony/'
> >
> > The tilde is thus provided by the command line
> "printf" AFTER
> > openbox has executed it.
> >
> > And yes  three backslashes are now needed due to
> quoting requirements,
> > even though only one is needed from the command line.
>  Could this be
> > another "openbox" parsing problem?
> >
> > The question then comes down to: How fast can we get
> 'tilde expansion'
> > fixed in the "openbox" source?
> 
> Such hostility, it's amazing.
> 
> > That is only do the expansion if not in quotes, and
> precessed by the
> > start of the line, or white space.
> 
> Allowing a quoted \~ which gets passed literally to the
> command,
> instead of being expanded, should be nice.

LOL

Still complaining about finding a solution that isn't as nice as he likes that is going to be put into a macro so that, to use it, all he has to do is hit a couple of buttons.

hehehe....

Knute