# The form data below was edited by super-tom_tyler # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # Status: Job status; [open/closed/suspended]. Required # Project: The project this job is for. Required. # Severity: [A/B/C] (A is highest) Required. # ReportedBy The user who created the job. Can be changed. # ReportedDate: The date the job was created. Automatic. # ModifiedBy: The user who last modified this job. Automatic. # ModifiedDate: The date this job was last modified. Automatic. # OwnedBy: The owner, responsible for doing the job. Optional. # Description: Description of the job. Required. # DevNotes: Developer's comments. Optional. # Type: Type of job; [Bug/Feature]. Required. Job: SDP-168 Status: closed Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2017/04/02 17:31:21 ModifiedBy: super-tom_tyler ModifiedDate: 2017/04/02 17:31:23 OwnedBy: tom_tyler Description: Work around RHEL/CentOS 7 command completion issue. There is a known issue with 'set -u' in CentOS 7 interfering with command line completion in interactive shells. It goes totally bonkers when you try a tab completion. We use 'set -u' as a good programming practice; it declares bash variables to be declared before being referenced. But it's not really needed in interactive shells. It's not an issue in CentOS 6. I was hoping this would get fixed in RHEL/CentOS, but it's not as of CentOS 7.3. One workaround would be to remove 'set -u' from p4_vars, and instead set it in all scripts instead. That way it is always set for programming, and not set when p4_vars is sourced for human interactive use. DevNotes: This job, SDP-168, was originally named job000671. Type: Feature