Opened 14 months ago

Closed 13 months ago

Last modified 13 months ago

#3128 closed help (fixed)

PUMA set -u

Reported by: pmcguire Owned by: um_support
Component: PUMA Keywords: tab completion, bash, unset, set, command history
Cc: Platform: PUMA
UM Version:

Description (last modified by pmcguire)

Hi CMS Helpdesk
Tab completion of commands on PUMA with bash often gives errors. With my .profile (which is similar to other people's), when I log in and type:
cd r and then hit the TAB key (trying to do tab completion to the roses directory, I get this error:
cd r-bash: COMPREPLY: unbound variable.

I found from a google search that this maybe be because the UNSET variable is set:
set -u.

If I do a:
set +u
then the problem with tab completion goes away.
But I don't know right now if this has other repercussions.

Any advice?

Change History (4)

comment:1 Changed 14 months ago by pmcguire

  • Description modified (diff)

comment:2 Changed 14 months ago by ros

Hi Patrick,

This is possibly a question for Andy when he returns. I've just switched my shell to bash and tab complete works ok for me. I'm not sure how you've got set -u as default this is not usually what you want as it can cause nasties. You normally only switch it to -u when you specifically want to check unbounds. Not sure what is different in your environment….

We will be moving to a replacement server in a few months so may not be worth spending too much time on if you have a workaround.


comment:3 Changed 13 months ago by andy

  • Resolution set to fixed
  • Status changed from new to closed

Hi Patrick,

I don't know why this was set for you. Have you changed anything to unset it in your setup files - .profile .bashrc?

It should not be set at all and thus will default to the unrestricted shell and give tab completion.

As Ros says we are moving to a new Puma server in a couple of months so I wouldn't spend too much time on this. I will close the ticket but please pop round for a chat if you want to discuss this further.


comment:4 Changed 13 months ago by pmcguire

Hi Andy/Ros?
I don't know what happened either to get the set -u behavior. I haven't had problems since then.
Thanks for closing the ticket.

Note: See TracTickets for help on using tickets.