[p4] How to negate a trigger without removing it from thetriggers form

Albrecht, Matt matt.albrecht at zilliant.com
Mon Dec 11 05:53:41 PST 2006


The technique I've been using lately is to change the search path to something that doesn't exist, for example:

   RequireJobs submit //depot/... "perl mycommand"
to:
   RequireJobs submit //xdepot/... "perl mycommand"

It's very easy to spot the difference, easy to change, and I don't have to worry about typos causing trigger errors.

--Matt

-----Original Message-----
From: perforce-user-bounces at perforce.com on behalf of John Hopkins
Sent: Fri 08-Dec-06 5:38 PM
To: perforce-user at perforce.com
Subject: Re: [p4] How to negate a trigger without removing it from thetriggers form
 
>From: "Greg Pan" <Greg.Pan at excapsa.ca>
>Subject: [p4] How to negate a trigger without removing it from the
>         triggers form
>Is it possible to negate a particular trigger by putting a minus sign
>before the line representing the trigger? I tested it out that minus
>sign does not work. Any other character may do the magic?
>
>Although it's not a big deal to remove the line totally from the
>triggers form it could be handy to negate it temporarily somehow, just
>like you negate a mapping line in your client view.

Prefixing the command with 'exit;' seems to work (tested on a Linux
server).  For example:

Triggers:
   modify-submit-form out change "exit;modify-submit-form %formfile%"


Hope that helps,
John
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user



More information about the perforce-user mailing list