Currently, ait will just place the directory name in the buffer name such as dir/foo.txt. This doesn't work if you have many files opened in similarly named directories. Take, for example, this project filesystem structure:
If you opened both client.txts you wouldn't have a way to figure out which is which as they would both get named Api/client.txt. GNU Emacs usually adds a number to the buffer name such as client.txt<1> which I'm not totally against but I find that it is still difficult to know which is which.
Potential Solutions:
GNU Emacs way (client.txt<1>, client.txt<2>) (still kind of confusing)
added .. until there is something unique (Api/client.txt and Database/../client.txt) (could get long but not as long as #3)
Full path relative to ${pwd} (Api/client.txt, Database/Api/client.txt) (could get really long)
???
Currently, `ait` will just place the directory name in the buffer name such as `dir/foo.txt`. This doesn't work if you have many files opened in similarly named directories. Take, for example, this project filesystem structure:
```
api/
|-> Api/ -> client.txt
|-> Database/ -> Api -> client.txt
```
If you opened both `client.txt`s you wouldn't have a way to figure out which is which as they would both get named `Api/client.txt`. GNU Emacs usually adds a number to the buffer name such as `client.txt<1>` which I'm not totally against but I find that it is still difficult to know which is which.
Potential Solutions:
1. GNU Emacs way (`client.txt<1>`, `client.txt<2>`) (still kind of confusing)
2. added `..` until there is something unique (`Api/client.txt` and `Database/../client.txt`) (could get long but not as long as `#3`)
3. Full path relative to `${pwd}` (`Api/client.txt`, `Database/Api/client.txt`) (could get really long)
4. ???
Kevin "The Nuclear" Bloom
Currently,
aitwill just place the directory name in the buffer name such asdir/foo.txt. This doesn't work if you have many files opened in similarly named directories. Take, for example, this project filesystem structure:If you opened both
client.txts you wouldn't have a way to figure out which is which as they would both get namedApi/client.txt. GNU Emacs usually adds a number to the buffer name such asclient.txt<1>which I'm not totally against but I find that it is still difficult to know which is which.Potential Solutions:
client.txt<1>,client.txt<2>) (still kind of confusing)..until there is something unique (Api/client.txtandDatabase/../client.txt) (could get long but not as long as#3)${pwd}(Api/client.txt,Database/Api/client.txt) (could get really long)