search

haya14busa / vim-easymotion

DEPRECATED
https://github.com/Lokaltog/vim-easymotion
23 stars 0 forks source link

Change plugin name including variable, mapping etc... #10

Closed haya14busa closed 10 years ago

haya14busa commented 10 years ago

I want to change plugin name from vim-easymotion to vim-lazymotion because I think this repository is no longer mere a fork now and I want to remove some code which exists only for backward compatibility.

In addition, GitHub cannot search fork repositories and Google rank may be low too. Other some plugins which enhance vim's motion dose not refer to haya14busa/vim-easymotion but Lokaltog/vim-easymotion.

But, renaming variable and mapping must surprise users when they update, and force them to re-configure some code, so I wimped out.

Solution list:

  1. Leave this repository as a fork and don't change name too
  2. Leave this repository as a fork but change name including variable
  3. Leave this repository as a fork, change name, but leave variable as 'easymotion'
  4. Make new repository and make this repo deprecated
    • I think this solution is good, but the users will not notice it soon.
    • It will clean up Issue,PullRequest,Star, and other info.

About name: vim-lazymotion I think this name ...

  1. respect 'vim-easymotion'
  2. means move cursor not easily but lazily, and this concept is good(?)

English isn't my first language, so I'm not sure this name make sense. (such as 'lazy' also means 'delayed' (e.g. lazyloading)

If you are interested in or have any good ideas, please write comments.

Thanks.

joshtch commented 10 years ago

'Lazy' to me seems like it's referring to the plugin, which it isn't, it's referring to the user. I think something that sounds like quick or flash or something that gives a sense of speed would be better. Or alternately something like "targetmotion", which connects the fact that the plugin uses a targeting system to move around. I do think keeping the -motion suffix is a good idea though, to acknowledge the plugin's origins.

haya14busa commented 10 years ago

Thanks for your comments! :sushi:

'Lazy' to me seems like it's referring to the plugin

Really? Hmm, I like the name 'lazymotion' because Levenshtein distance to 'easymotion' is only two and pronunciations of 'easy' and 'lazy' look alike (and I thought 'lazymotion' give an image of enabling us to move cursor 'lazily' by some chance) but I should reconsider it...

Yeah, to use quick or flash to stress the speed or to use target/marker/label to describe plugin's feature correctly looks good, but I suspect just -motion suffix really respect plugin's origins and these name didn't attract me personally.

Anyway, I should reconsider it. Thanks!

joshtch commented 10 years ago

I meant like quickmotion or flashmotion or something; keep the suffix, change the prefix. It actually didn't occur to me the similarity in sounds between 'easy' and 'lazy'.

haya14busa commented 10 years ago

Thanks for your replay.

I meant like quickmotion or flashmotion or something; keep the suffix, change the prefix.

I understood it. Sorry for my poor English. 'quickmotion' looks good to some extent, but do these name really imply this repository is originally from easymotion? Just keep the '-motion' suffix looks insufficient for me because -motion prefix is used by another plugin too (e.g. CamelCaseMotion)

It actually didn't occur to me the similarity in sounds between 'easy' and 'lazy'.

Oh, really? I thought both word have "-zē", so I said I found similarity in sounds.

\ˈlā-zē\ \ˈē-zē\

Hmm, it's difficult to come up with good name...

joshtch commented 10 years ago

Yeah, not until further reflection. Probably because it's text, but I dunno. Maybe someone else can give some input on this.

How do you feel about calling it "easymotion plus" or something? It would be like how there is an Adblock and an Adblock Plus, except in the case of easymotion the original is no longer being developed. Also vi -> Vi IMproved, and others. It definitely makes sense to try to draw people away from the original since it's not being developed, and adding a "plus" would clearly indicate that, ceteris paribus, yours should be preferred. Especially since you actually respond to bug reports. Something to think about...

haya14busa commented 10 years ago

How do you feel about calling it "easymotion plus" or something?

At first, I thought just adding 'plus' is too simple, but on second thought, it has many good points including you mentioned above and it solve some problems I worry about to change plugin name.

I want to come up with some cool name like 'Vi IMproved' not just adding 'plus', but if I couldn't come up with or someone else don't have any good ideas, it seems like 'vim-easymotion-plus' is good enough for me.

I'll add some features and want to rewrite README and help doc before changing the plugin's name, so there are much time to consider.

Thanks, @joshtch!

joshtch commented 10 years ago

Sure thing! I'm glad I could help. :)

haya14busa commented 10 years ago

I do not need to change name any more because I became collaborator on Lokaltog/vim-easymotion repo & took over the project #12. I'll probably push to Lokaltog/vim-easymotion repo this weekend. It will be different from my fork version in that selectline & selectphrase became separated plugin, and removed <Plug>(easymotion-S) because easymotion-S is same as easymotion-bd-w.

However, most parts will be same as my fork version and I'll develop and maintain freely in Lokaltog's repo.

I do not need to change name anymore, but thanks again, @joshtch !

joshtch commented 10 years ago

Congrats! I'm happy to see you getting the recognition you deserve. Thanks for your great work @haya14busa!

haya14busa commented 10 years ago

Congrats! I'm happy to see you getting the recognition you deserve.

Thanks :dog: I pushed to Lokaltog/vim-easymotion, so please see it.

https://github.com/Lokaltog/vim-easymotion