4 ms·
The main argument I’ve come across against this is that text editors commonly put great weight on file names—opening by file name, showing the file name without
by chrismorgan 8y ago
The main argument I’ve come across against this is that text editors commonly put great weight on file names—opening by file name, showing the file name without its containing directory structure or with it harshly abridged (e.g. /h/c/B/p/controllers.py). It would be nice for this to be addressed better in editors, but it is a bit of a tricky matter to handle across varying projects.
Of course, as presented, having lots of files named “posts.py” is also fairly terrible in text editors.
One solution is for the filename to include more, e.g. posts/posts-controllers.py. This helps some tools at the cost of others and greater verbosity.
- AdrianoKF 8y agoThis summarizes my struggle when getting my feet wet with custom Ansible playbooks. Having a bunch of `main.yml` files open in your editor and trying to figure out what exactly it is you're currently looking at greatly increases cognitive load and distracts from the actual task at hand.
- deleted 8y ago[deleted]
- andreareina 8y agoI like how emacs does it: when there's one file open with a particular name, show just the name; when there's more than one, there's a legend with as much of the path as needed to disambiguate. * unique filename: filename.ext * common filename, different directories: filename.ext<dirname> * common filename and immediate parent directory name: filename.ext<grandparent/parent> * etc