UNIX for Advanced & Expert Users

OK, well I tried running

Code:

export TERM=xterm-color

I also tried xterm and vt100.

I even tried, when testing TERM=vt100 in screen, configuring terminal.app to strictly emulate vt100, by declaring the terminal as vt100 and selected the "strict vt100 keypad behavior" option.

None of this had any affect on the problem. Unless I would have to do something more than simply export TERM=blah within a screen session.

Hi.

I'd guess that it may have to do with your zsh prompt string, or (less cheerfully) the complex completion system of zsh.

What does your prompt string look like? I have not done much with mine, so it looks like:

Code:

leap% ps | grep $$
30801 pts/0    00:00:00 zsh
leap% echo $PROMPT
%m%#

but when I enter cd ~<TAB> it prints the strings to which ~ might expand (in columns) and returns the cursor to after the ~

However, I am not using screen ... cheers, drl

My prompt is fairly complex:

Code:

╭─[mylongusername@Marshalls-MacBook-Pro:~]
╰─[ :( ] $ echo $PROMPT                                                                         (11-20 15:31)
╭─[%{%}%n%{%}@%{%}%U%m%u%{%}:%{%}%2c%{%}]
╰─[ %(?,%{%}:%)%{%},%{%}:(%{%}) ] %(!.#.$)

drl, I believe you have it figured out.

If I start a screen session, and then run export PROMPT=% in order to give myself a blank prompt, the problem is resolved!

So, any ideas what I might do, other than living with it (now that I at least know what's causing it), or using a simple prompt within screen? Is there any way to configure screen, like say, what the prompt variable is?

Hi.

Use half of the current prompt -- as much as makes sense. If it works, add half of the part left out, if it doesn't work, cut the half in half, repeat until solved.

Or, you could start with an emptyish prompt, and add a bit each time.

Good luck, keep us posted ... cheers, drl

To be honest, I can't figure out how to change the default prompt in screen.

I've been looking at screenrc files via google for a couple hours now, but I haven't found anything.

I just noticed that this problem also occurs when using su.

su has a prompt? I think su just drops you into the target user's default shell.