-
Notifications
You must be signed in to change notification settings - Fork 40
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
(Feature Request) Open marked files with default $EDITOR #35
Comments
Hi, Thank you very much for your suggestion! This does sound like it could be very useful, but how would you suggest marking files? At the moment, the command |
No problem at all, I really like this utility so thank YOU!
|
Thank you very much for this! I will have a careful look in the weekend and get back to you then. |
Hi 5c0tt-b0t, Sorry for being a bit slow with this. But since the suggested change is quite significant, I think it's good to take some time before incorporating it. I really like the idea, though, and think it would be very useful for frequently edited files such as One thing I wonder is whether the interface might be a bit complex to remember, since quite a few cases are considered. It might be cleaner (though a bit more verbose), to add a flag
to add a mark with label
to add a mark with label |
dont apologise! i agree the script i used above as an example has alot of checks and I was actually going to re-write it with flags too to make it alot simpler! I like this idea! :) |
Hi, first of all.... this is amazing, THANK YOU!!!
When I saw this initially, I thought, as it can mark files as well as directories, that pressing ENTER on a file would open the file just as it does a directory, but it appears that it just navigates to the file's directory instead.
I think it would be alot nicer to open any mark, not just directories, otherwise marking files is not needed, we can already just mark the directory instead which is better.
For example: I marked my 'zshrc' & 'bashrc' when I could've just marked '/etc' instead which gives me access to both files through one shortcut.
My feauture request would make FZM's file marking a very valuable feature!
FZM could default to: default $EDITOR (if set)
If not: look for 'nano' & 'vi/vim' as both of these editors are pre-installed in most distros now unless...
a variable for us to set like: "FZM_EDITOR" to let us pick our own, this could serve an extra purpose also! adding this means we could fill up FZM with all of our project's files and have them open in vim, but still have my default editor set as micro for opening normal txt/rc/configs when outside of FZM.
Thank you again.
The text was updated successfully, but these errors were encountered: