On Thu, Apr 18, 2002 at 01:46:21PM -0600, Gregg Dameron wrote:
> Dan Espen wrote:
>
> > Oops, looks like someone top posted:
> >
> > >
> > >
> > > > I would vote in favor of an increase.
> >
> > You might get your increase, but I don't really favor it.
> > It just uses up some memory for an extre
Dan Espen wrote:
> Oops, looks like someone top posted:
>
> >
> >
> > > I would vote in favor of an increase.
>
> You might get your increase, but I don't really favor it.
> It just uses up some memory for an extreme case that can be avoided
> pretty easily.
Thanks to all who have responded to t
fvwm@fvwm.org writes:
> Ahh, you are putting the whole script _IN_ the config file?
>
> I think what Dominik meant was the return value needs to stay under 1022, may
> be I'm wrong, can someone clarify?
The limit is on the size of the command, not the result.
(The result can produce multiple lin
Dear, k a k @ c i s c o . c o m.
Please don't set the From: header to fvwm@fvwm.org, it confuses others.
Setting it to [EMAIL PROTECTED] would be ok.
On 18 Apr 2002 13:44:46 -0400, fvwm@fvwm.org wrote:
>
> Ahh, you are putting the whole script _IN_ the config file?
>
> I think what Dominik meant
On 18 Apr 2002 11:01:20 -0600, Gregg Dameron wrote:
>
> Dominik Vogt wrote:
>
> > On Wed, Apr 17, 2002 at 07:29:25PM -0600, Gregg Dameron wrote:
> > > Running 2.4.5 on Solaris.
> >
> > In fvwm, a single command line can not be longer than 1022
> > characters (1024 minus 1 for the string end minu
Ahh, you are putting the whole script _IN_ the config file?
I think what Dominik meant was the return value needs to stay under 1022, maybe
I'm wrong, can someone clarify?
The way I do it it to keep a script dir in my path and call them like this:
PipeRead "addExecutableOnMenu BrowserPopup ope
Dominik Vogt wrote:
> On Wed, Apr 17, 2002 at 07:29:25PM -0600, Gregg Dameron wrote:
> > Running 2.4.5 on Solaris.
> >
> > It seems that as a PipeRead script increases in size, fvwm2 struggles to
> > read and execute it. The maximum seems to be 1024 bytes, measured by
> > the string output in deb
On Wed, Apr 17, 2002 at 07:29:25PM -0600, Gregg Dameron wrote:
> Running 2.4.5 on Solaris.
>
> It seems that as a PipeRead script increases in size, fvwm2 struggles to
> read and execute it. The maximum seems to be 1024 bytes, measured by
> the string output in debug mode that begins:
>
> <> abo
Running 2.4.5 on Solaris.
It seems that as a PipeRead script increases in size, fvwm2 struggles to
read and execute it. The maximum seems to be 1024 bytes, measured by
the string output in debug mode that begins:
<> about to attempt '
