You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to be able to have a history of the calculations that doesn't goes away when closing VimCalc window. It would be even better to have a separated history for each task/project.
I think this could be accomplished through a command that activate VimCalc on the current buffer, instead of on a new one. Through vim filetypes it would be possible to have VimCalc activated automatically when opening such history files.
Thanks for sharing this awesome plugin!
The text was updated successfully, but these errors were encountered:
Thanks for submitting this request. I like the idea of a persistent history and will add it to my todo list.
I intend to revisit VimCalc and add a bunch of new features. User-defined formulae, an RPN mode and lists of numbers for stats-based operations are all on my radar too. However, I must admit, this work is fairly low on my priority list so you may have to be patient. In the meantime: I'm happy to receive pull requests! ;)
I've feeling the need of a better tool to perform calculations for a long time, and especially one integrated with Vim, and have been searching vim.org at times for a while.
Finding VimCalc was a very good surprise, and it fulfill most of my needs on its current state, so I have no problem with waiting :D
Thank you very much for your time and effort on this great tool.
I'd like to be able to have a history of the calculations that doesn't goes away when closing VimCalc window. It would be even better to have a separated history for each task/project.
I think this could be accomplished through a command that activate VimCalc on the current buffer, instead of on a new one. Through vim filetypes it would be possible to have VimCalc activated automatically when opening such history files.
Thanks for sharing this awesome plugin!
The text was updated successfully, but these errors were encountered: