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

Count from 1 instead of 0 when searching packages #83

Merged
merged 1 commit into from
Jan 6, 2018

Conversation

Morganamilo
Copy link
Contributor

I feel like starting from 1 is much better ergonomically while not using
a numpad. This could be added as a config option instead if you would
prefer.

I feel like starting from 1 is much better ergonomically while not using
a numpad. This could be added as a config option instead if you would
prefer.
@maximbaz
Copy link
Contributor

maximbaz commented Jan 2, 2018

Over time I got used to this, but I remember being confused and uncomfortable with yay starting indexes from zero, so I support this change. Config is probably an overkill for this :)

@Jguer
Copy link
Owner

Jguer commented Jan 6, 2018

@maximbaz I'm away from my dev environment at the moment, can you test that this patch does not create any conflicts and selects the right package on searches containing only AUR, only repo and AUR and repo?

Otherwise I'll only be able to review it in 7 days.

@Morganamilo
Copy link
Contributor Author

Morganamilo commented Jan 6, 2018

When I submitted this I tested:

  • 0 (invalid)
  • Number packages + 1 (invalid)
  • The first + last package
  • Both packages on the aur/repos boundary

All seemed to work as expected.

@maximbaz
Copy link
Contributor

maximbaz commented Jan 6, 2018

Testing now, will get back in a few moments.

@maximbaz
Copy link
Contributor

maximbaz commented Jan 6, 2018

Works well in all 3 cases, the patch itself looks good to me too.

@Morganamilo
Copy link
Contributor Author

I forgot to mention I also did test all these cases on both --bottomup and --topdown. so it should be good for those too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants