Skip to content
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.

Sign up for GitHub

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

Jump to bottom

floating point number #5

Open
mattn opened this issue Mar 9, 2012 · 2 comments
Open

floating point number #5

mattn opened this issue Mar 9, 2012 · 2 comments

Comments

@mattn
Copy link

mattn commented Mar 9, 2012

How about support 0.9 to 1.0 with increment?
@tpope
Copy link
Owner

tpope commented Mar 9, 2012

Sounds pretty complicated, once you take it to its logical conclusion: -1.00000 => -0.99999, for example (and that's not even counting the inevitable feature request for an option to omit the leading zero there). Plus it conflicts with versioning schemes (2.9 => 2.10), and needs to tread lightly around certain date formats (03.09.2012). And what happens if we invoke it before the decimal point? What happens if we invoke it on the 2 in 1.20?

The short of it is this feels like a lot of complexity for very little gain.

@mattn
Copy link
Author

mattn commented Mar 9, 2012

Sounds pretty complicated

Yes I think so. I could't write patch easily.
Currently speeddating has d<c-a> like key mappings to differentiate something. How about f<c-a> treat floating point value?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tpope @mattn