-
-
Notifications
You must be signed in to change notification settings - Fork 12
Implementing some convenience suggestions #45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I'm not sure what this means, can you provide a screenshot showing what this actually does?
If we are going to do this, please add settings that exposes the previous behavior. Previous behavior should be the default. Too many people rely on previous behavior.
This is obviously subjective. If this is accepted, the Lastly, please follow the convention of the project and add docstrings to any new functions providing the basic description of the function's behavior. |
|
You will need to address lint and spelling issues. For spelling issue, just wrap the offending CWD in with backticks Once completed, I will need time to consider the features and whether we want all of them. I think I'm probably okay with the placeholder and sorting. I'm not sure if I like folders mixed with documents, but I'll think about it. I might be okay with |
|
Awesome, sounds good! Thanks so much |
| "fuzzy_bookmarks_load", "fuzzy_get_cwd", "fuzzy_cwv" | ||
| ]: | ||
| return active | ||
| elif key == "fuzzy_go_to_parent_dir": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry! Just realized there was a mistake in functionality here. It was navigating up a directory on every backspace. This change makes it so that it only navigates up if the input is empty
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. I haven't tested functionality yet, but that is, of course, on my list.
Changes like this require more cautious evaluation. I think I noted that I particularly wanted to make sure this feature behaves without issues, and you've just stumbled on why 🙂.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally agree! There's no rush or pressure on my end to get the changes merged since I can already use them locally. My goal was just to add some options that maybe other users would find helpful


I just started tetsing out ST as a replacement for emacs, and this package is awesome! Thanks for all the work you've put into it.
I just have a few updates that I've been playing with to more closely replicate the experience I'm used to and I thought I'd see if you'd like to incorporate them.
Here's a summary of the changes:
..option from the listFeel free to make any changes, or reject them if you don't think they make sense to include.
Thanks again!