search

pw4ever / awesome-wm-config

awesome window manager config with persistent dynamic tagging
271 stars 55 forks source link

toggle notfiy instead of adding new #2

Closed ContextSwitchWang closed 8 years ago

ContextSwitchWang commented 8 years ago

If I use modkey + \ multiple time, multiple "info" will be displayed. And you gotta kill'em one by one. I changed that behavior to turn that "info" off is used a second time. I think that should be more reasonable for most people.

And I add an additional key to display volume info, you can ignore it, though, if you don't want it.

pw4ever commented 8 years ago

@AnthonyAaronHughWong Thanks for the patch! Can you isolate the changes to info from the volume keybinding, and file the info patch as a separate patch? I cannot cherry-pick it from your pull request if you file both changes as one.

The volume patch depends on "myscripts/myvol.sh". If you also like to have it merged, please contribute that script, put it under the existing folder "bin" (instead of "myscripts"), specify binary dependencies (e.g., "pacman -S xxxx"), and add corresponding keyboard entry in README.md.

ContextSwitchWang commented 8 years ago

Definitely, I can. Since the volume is platform dependent, I'd better leave it out.

Another thing I'm currently thinking is, the extend by 1/7 approach can't resize client precisely sometimes. What I'd prefer is a Vim like binding: use Mod + num before a command, so that the effect is repeated num times. But that contradicts with the view tag binding. So maybe we can use Mod + num before Mod + g to view tag num, and we don't need the Mod + control + num anymore.

( In fact, there's another project awesome-vim-bindings implementing a modal vim-bindings with all these. However, a complete vim like binding may be a little overhead, 'cause simple things would take lots of strokes, so I reckon global keys should be kept. )

What you think?

On Tuesday, November 17, 2015 07:40:04 AM pw4ever wrote:

@AnthonyAaronHughWong Thanks for the patch! Can you isolate the changes to info from the volume keybinding, and file the info patch as a separate patch? I cannot cherry-pick it from your pull request if you file both changes as one.

The volume patch depends on "myscripts/myvol.sh". If you also like to have it merged, please contribute that script, put it under the existing folder "bin" (instead of "myscripts"), specify binary dependencies (e.g., "pacman -S xxxx"), and add corresponding keyboard entry in README.md.

Reply to this email directly or view it on GitHub: https://github.com/pw4ever/awesome-wm-config/pull/2#issuecomment-157407341

                                                  With my kindest regards,
                                                              Qiming Wang,
                                           Wed, 18 Nov 2015 13:24:24 +0800
ContextSwitchWang commented 8 years ago

And of course, We can use Mod + u + num, to apply numeric argument, but that contradicts with view the urgent client.

pw4ever commented 8 years ago

@AnthonyAaronHughWong My opinion is that number-based tag ids are just shortcuts to the more general name-based tag ids.

If there are more than 10 tags (which goes beyond the limit of number-based tag ids), it is better to use the more general Modkey g and friends. I challenge you to quickly identify the 13th tag if you have 20 of them. Name does not suffer from the problem as long as you keep them unique. If you have more than 1 screen, my personal convention is to prefix screens other than the primary one with a number, e.g., main and 2main won't clash.

Conversely, current number-based tag ids are compatible with the default Awesome config, is easy to reach, and switch tag focus with a single combo key.

Although the Vim's number prefix and Emacs's universal argument (C-u) are obviously handy for general editing, I do not see the same usefulness applies in this case.

If you disagree the logic here, there is always the option to fork the repo :)

ContextSwitchWang commented 8 years ago

Okay. But in fact, the main reason for this is for resizing, not tag finding.

Thanks for sharing opinion anyway...

                                                  With my kindest regards,
                                                              Qiming Wang,
                                           Wed, 18 Nov 2015 14:48:32 +0800
pw4ever commented 8 years ago

@AnthonyAaronHughWong My apology---long day before computer, missed your point.

I use the current resizing keybinding for coarse resizing, and use Modkey + Right button for more precise needs. IMO, mouse is more intuitive and precise than keyboard for this particular task; the only downside I can see is the general evilness of "hands off the keyboard home row".

I am personally content with current settings, but if you are going to pursue and implement the idea of adding prefix argument to keyboard resizing, I would love to try it out.