Directory Change Echoing Since LEAP 42.3 Update

English Applications
1

Recently I have updated my system to LEAP 42.3 through the ‘zypper up’. It went almost perfectly with one error related to a GFX driver (asked on another thread).

One extremely odd thing that changed is that when I change directory in a terminal, the directory gets echoed back! Example:


[/temp] cd /tmp
Directory: /tmp
[/tmp]

WTH? Since the beginning of time!!! it would and should do this:


[/temp] cd /tmp
[/tmp]

So I got used that if there is an output from a command, there must be an error, for example changing to a directory that does not exist. Now I do a double-take
every time. It does not seem that the code has been changed for a rather long time:

[/tmp] tcsh --version
tcsh --version
tcsh 6.18.01 (Astron) 2012-02-14 (x86_64-unknown-linux) options wide,nls,lf,dl,al,kan,sm,color,filec
[/tmp]

Is there a workaround?

2

It’s not happening here.

Actually, I can get it to happen. If I remove (or temporarily rename) my “.cshrc” and “.csh.expert”, then it happens if my TERM is not set to “xterm”.

So, for example, after renaming those startup files, I can do:

xterm -tn vt100

and I see the problem. If I don’t use the “-tn vt100”, then instead the title line of the “xterm” window changes to indicate the directory.

This is done by an alias (for “cwdcmd”), which is being set in “/etc/csh.cshrc”.

There was a recent bug report about “cwdcmd”, though I think it was for Tumbleweed. The bug report was that “cwdcmd” alias should not be set if “.csh.expert” exists.

In any case, if you have your own “.cshrc” or “.csh.expert”, you can use “unalias” there to undefine that alias.

Personally, I use:

unalias *

in my “.csh.expert”, which removes all predefined aliases.

3

Hi,

This is great info! Thank you. I have progressed but I still do not know exactly what is happening.

My TERM variable comes in as xterm-color, so when I changed it to xterm, nothing changed at first but then I noticed that in a
nested shell, the echoing of the directory is gone now! Although, if TERM remains as xterm-color, nested shells still behave in
the wrong way.

Then I checked my .tcsch file and have nothing to set this or affect this, so there must be defaults that come from somewhere
and that place must have changed. So I looked at the aliases load and found one called cwdcmd as you mentioned. I don’t set
that anywhere but it is set somehow!

The workaround that solved the issue was to add ‘unalias cwdcmd’ to my .tcsh. Behavior is back to normal but this is a dirty
way to solve it, unaliasing something that was never aliased! So it is indeed a bug.

Do you know where the defaults are set? Where I could remove the alias from being set i the first place?

Thanks again!

4

The are set in “/etc/csh.cshrc”. There’s a warning there, to not change that file.

You can create a “.csh.expert” which causes parts of that file to be skipped. And you can add some of your own commands (such as an “unalias” there).

5

That is it! The bug is clearly there.

Thank you very much!