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.

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

ft follow lightspeed's case sensitivity setting, but i'd rather they didn't #147

Open
emmanueltouzery opened this issue Jun 1, 2022 · 0 comments
Labels

Comments

@emmanueltouzery
Copy link

This issue was already mentioned in #104. It seems it was agreed that lightspeed should not change ft to be case insensitive no matter what settings are set for lightspeed. But it seems lightspeed still changes this.

I have the latest version of lightspeed, on nvim 0.7.0, with the following config:

use {'ggandor/lightspeed.nvim', Commit='c5b93fc1d76a708cb698417326e04f4786a38d90', config = function()
  require'lightspeed'.setup {
    ignore_case = true,
  }
end}

and for instance, with this text:

import { postForm } from 'utils/fetch';

If i put the cursor at the beginning of the line with ignore_case=true, then ctf will stop at the F of postForm. While if ignore_case=false is set then it will stop at the f of 'from'.

I'd really rather that tf behave in the "normal" case sensitive manner, no matter what is the setting for lightspeed.

emmanueltouzery added a commit to emmanueltouzery/nvim_config that referenced this issue Jun 3, 2022
partly a workaround for ggandor/lightspeed.nvim#147 and partly I only used/wanted these two anyway
@ggandor ggandor added the API label Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants