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

Why ls() changes current working dir (cwd)? #29

Open
ksmolyanin opened this issue Mar 1, 2013 · 1 comment
Open

Why ls() changes current working dir (cwd)? #29

ksmolyanin opened this issue Mar 1, 2013 · 1 comment

Comments

@ksmolyanin
Copy link

I think your library is excellent but ...
I guess that semantics of ls() (derived from UNIX "ls" command) presupposes its read only behavior. In your implementation it changes current working directory. For example these steps:
mkdir('/dir1' ....
ls('/dir1/' ...
mkdir('/dir2' ...

lead to the following dir structure:
/dir1/dir2
(dir2 is a sub-folder)
while these ones (just without intermediate ls()):
mkdir('/dir1' ....
mkdir('/dir2' ...

to this structure:
/dir1
/dir2

(both dirs are in the root)

@ebidel
Copy link
Owner

ebidel commented Mar 13, 2013

Can't remember why I did this, but I'll look into it. #20 is related.

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

2 participants