Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Should be called

oohya.directory



sort by: page size:

. = current directory

.. = parent directory


Or even:

  puts Dir["*.rb"]

Like Open Directory?

Akthough this does work

    dir "c:/*.txt" /w/o/s/p

r/opendirectories

There is a subreddit for Open Directories!

> The libraries are searched in the binary’s current directory first.

Huh?


This is precisely the struggle that I've been having to deal with lately. Though, does anyone know if this works with OpenDirectory?

I suppose this would be the more straightforward and expected behaviour:

    less: somedir: is a directory

  # create a directory in the current directory and cd to it

  function mkcd() { mkdir -p "$@" && eval cd "\"\$$#\""; }

    function dir(){
      #make the windows guy happy 
      find ./ -type f -name "$1"
    }

> The filesystem APIs could be extended with a "CWD" handle argument that can be passed around

Why would you even want a working directory at that point?


Technical topic directories are alive and well!

https://github.com/sindresorhus/awesome


Well, that's basically what directories are.

Hmmm. In Python, I would leverage the dedicated utility of the standard library:

  os.makedirs(path)

Directories that are based on objective criteria don't have this problem.

For example /dev is defined by objective criteria, and thus there's not much argument to what goes into /dev. We should only have core directory structure defined by objective criteria.


Thanks for sharing, I didn't know this directory!

The dir structure is defined by me.

Namespaces are defined by the 3rd party developer.


An IDE should get access to the specific directory that contains the project, not everything.
next

Legal | privacy