Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't work if PROMPT_COMMAND is set by something else #20

Open
jml opened this issue Sep 27, 2013 · 2 comments
Open

Doesn't work if PROMPT_COMMAND is set by something else #20

jml opened this issue Sep 27, 2013 · 2 comments

Comments

@jml
Copy link
Owner

jml commented Sep 27, 2013

This just bit a new user.

Not sure we can fix it, but we should at least document it.

@caneff
Copy link

caneff commented Sep 27, 2013

That was me. I just tried adding the undistract-me stuff to the end of the .bashrc file, after all my other PROMPT_COMMAND stuff was defined, and it seems to work now.

@anarcat
Copy link

anarcat commented Dec 20, 2018

I just tried adding the undistract-me stuff to the end of the .bashrc file, after all my other PROMPT_COMMAND stuff was defined, and it seems to work now.

can you clarify how you fixed this exactly? I'm also having the issue that i have weird behavior when other PROMPT_COMMAND functions are set... for example, i see this:

anarcat@curie:powerline(master)$ true
anarcat@curie:powerline(master)$ sleep 13
"true" took 14 secs

I have a "__prompt_command" function to do hacks on my prompt, which I added this way:

PROMPT_COMMAND="__prompt_command;${PROMPT_COMMAND}";

I also tried the other way:

PROMPT_COMMAND="${PROMPT_COMMAND};__prompt_command";

no luck...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants