GReagle

I have a branch in my fork in which I changed the command syntax and re-wrote the option parsing. Before I request a pull, I think I'll propose my changes...

I think that this style is easier to read. What do you think? ``` -a | --address) if [ -z "$2" ]; then print_error "missing arg for $1" else generate_email_address...

> I think you will need `shift 2` there or else only the switch will be shifted out of the arguments, leaving the user's supplied argument in the array. Incorrect....

Yes I would love this feature. I just started using Kure, which I got from F-Droid. I use the Random Shuffle feature and I do not want to hear audio...

Looking at config.h, I see that x is a normal keybinding, not an operator. Anyway, my question still applies to P.

Thanks for your feedback. I'll make a branch and changes and a pull request. I see that ~ needs to be changed to g~ in the man page.

Why are J and gJ **not** listed as operators in config.h, but are listed as operators in vis.1? Is there a meaningful difference between ```bindings_operators[]``` and ```bindings_normal[]```?

I would like to list ```ZQ``` in the man page since it is significantly easier for me to type than ```:q!```. Where in the man page should it go?

Thank you for your response. Yes I was using an older version; I'm sorry about that. I am now working with the latest git version. Is it true that in...

The "operators" don't do anything when first pressed, i.e. they wait for a motion or text object to be entered. These operators include c, d, y, , and in config.h...