Closed nitz closed 4 years ago
Hi @nitz , thanks for submitting this bug! I can reproduce it and will fix it as soon as possible.
The issue should be resolved with the latest changes available in the master branch. Please let me know if you have any questions or still encounter any problems!
Woah that was lightning quick! Thank you! I appreciate that you adopted the dog and cat for your test case too 😂
Hello! First real quick, I've been using libcwalk for a few days so far and it's done basically everything I need with no fuss. I love it!
Okay, so in an application I'm working on now on an embedded platform, I'm using libcwalk to traverse my folder hierarchy as the user navigates. I have a single buffer that I'm using and have been trying to use
cwk_path_get_absolute
to build the active path as the user pushes and pops directories. The issue I've run into is that attempting to append a path after a relative path has been appended results in an incorrect result. I've created a small example here to demonstrate the behavior and my expected outcome:Using the relative ".." to navigate up seems to somehow cause the next time a new fragment is added, append to the end of the original, pre-"up'd" directory.
Is this behavior expected when reusing the base path as the result like that?
Thanks for taking a look!