Closed paulroub closed 2 years ago
Interesting. I can see how this would be beneficial and will look into what might be causing the issue.
On 15 Aug 2022, at 8:14, Paul Roub wrote:
I have a dotfiles repo, managed by dotbot, that includes my bunches.
dotbot links my
~/dotfiles/bunches
to~/bunches
.$ ls -l bunches lrwxr-xr-x 1 paulroub staff 32 Aug 15 09:04 bunches -> /Users/paulroub/dotfiles/bunches $ ls ~/dotfiles/bunches release.bunch present.bunch # etc
If I configure bunch to look into
~/dotfiles/bunches
, all is well. If I instead point it to~/bunches
, it finds nothing.-- Reply to this email directly or view it on GitHub: https://github.com/ttscoff/bunch/issues/246 You are receiving this because you are subscribed to this thread.
Message ID: @.***>
The workaround is painfully easy and obvious, of course, so it's far from a high priority concern.
I think I have this working. When I tested it I got a different result: trying to select a symlink/alias in the open dialog immediately resolved to the source folder. So it worked, it was just impossible to actually use a symlink. If I have it NOT resolve the alias, then the contentsOfDirectoryAtURL returns empty. So I decided to just have it resolve the URL in memory before parsing the folder, which seems to be working. Will test a bit more before putting it out.
Sweet. I think the difference may be that I recently reorganized things, and ~/bunches
used to be a real folder. I changed it to a symlink without Bunch's knowledge. So even more self-inflicted than I'd realized.
Pushed the change in the beta release this morning. It will make it into the stable release soon unless people run into issues.
I have a dotfiles repo, managed by dotbot, that includes my bunches.
dotbot links my
~/dotfiles/bunches
to~/bunches
.If I configure bunch to look into
~/dotfiles/bunches
, all is well. If I instead point it to~/bunches
, it finds nothing.