Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: % bug in beta20-test1

X-seq: zsh-workers 1332
From: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
To: pws@xxxxxx (Peter Stephenson)
Subject: Re: % bug in beta20-test1
Date: Tue, 11 Jun 1996 13:45:59 +0200 (MET DST)
Cc: zsh-workers@xxxxxxxxxxxxxxx
In-reply-to: <199606111124.NAA22785@xxxxxxxxxxxx> from Peter Stephenson at "Jun 11, 96 01:24:40 pm"
Organization: Dept. of Comp. Sci., Eotvos University, Budapest, Hungary
Phone: (36 1)2669833 ext: 2667, home phone: (36 1) 2752368

> hzoli@xxxxxxxxxx wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > 
> > > mason@xxxxxxxxxxxxx wrote:
> > > > % %
> > > > zsh: command not found: fg
> > > 
> > > This is supposed to fixed this (plus the same bug which occurred with
> > > autoresume).
> > 
> > I did not try this patch but it seems that things like command %1 or
> > foo=%1 ; $foo will trigger autoresume.
> 
> The second of these was entirely deliberate.  I still think that's
> preferable.

I do not see why.  You can always use fg $foo explicitely.

>  You can handle the first by looking at the command flags
> when checking. 

I know that (but cflags should be used instead of cmd->flags).  But there
is an other problem.  With your patch \%1 also triggers autoresume so it is
not possible to execute a command beginning with a % (but correct me if I'm
wrong, I did not try your patch).

foo=%1 ; $foo never worked and noone complaind about it.

Zoltan

References:
- Re: % bug in beta20-test1
  - From: Peter Stephenson

Messages sorted by: Reverse Date, Date, Thread, Author