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

SCP transfrer break when enabling bash-it #220

Closed
vpassapera opened this issue Jul 27, 2013 · 4 comments
Closed

SCP transfrer break when enabling bash-it #220

vpassapera opened this issue Jul 27, 2013 · 4 comments

Comments

@vpassapera
Copy link

If i enable bash it and make my .bashrc a link to .bash_profile whenever I try to do an SCP transfer instead of transferring the file it echos out the last directory used.

@edubxb edubxb mentioned this issue May 20, 2015
@nwinkler
Copy link
Member

@vpassapera On the off chance that you're reading this - is this still an issue for you? If it is - a couple of questions for you:

  • Which OS/Linux distro are you using?
  • We've made a couple of changes to the installer to select the correct file based on the OS, i.e. for Linux we're installing into .bashrc now - which should avoid the above problem. Have you tried this change, and has it fixed your issue? See bash_profile vs bashrc #173 for more details...

CC @edubxb

@namtrah
Copy link

namtrah commented Aug 21, 2015

This does not fix the problem. I use Ubuntu 14.04.1 and have pulled the latest bash-it version. then sourced my .bashrc and tried the following command:

scp name@ubuntu:~/.bashrc BASHRC

Which should technically use scp to copy my local .bashrc via SSH back into BASHRC (this is a hypothetical test here). All I get is the directory and no file copied.

@edubxb
Copy link
Member

edubxb commented Aug 21, 2015

@namtrah can you put here the output of the error you get then doing this?

@vpassapera
Copy link
Author

@nwinkler I completely forgot about this issue.

I actually eventually solved the problem so long ago, I don't even remember what I did.

Thank's for the follow up though!

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

4 participants