ash: Add accelerator for snapping windows left/right.

ash/accelerators/accelerator_table.cc

Index: ash/accelerators/accelerator_table.cc
diff --git a/ash/accelerators/accelerator_table.cc b/ash/accelerators/accelerator_table.cc
index 01e3fdb8f0c9d62f7d2f5ef99d6b94f1e46fb3c0..6f07383179891c42ddf7705d84ae7779204d5fcf 100644
--- a/ash/accelerators/accelerator_table.cc
+++ b/ash/accelerators/accelerator_table.cc
@@ -71,6 +71,10 @@ const AcceleratorData kAcceleratorData[] = {
   { ui::ET_TRANSLATED_KEY_PRESS, ui::VKEY_VOLUME_UP, false, false, false,
     VOLUME_UP },
   { ui::ET_TRANSLATED_KEY_PRESS, ui::VKEY_S, true, false, true, FOCUS_TRAY },
+  { ui::ET_TRANSLATED_KEY_PRESS, ui::VKEY_LEFT, false, true, true,

[Daniel Erat, 2012/04/17 16:51:19]

it has been asserted in the past (by pkasting, i think) that we should stay away
from ctrl-alt accelerators.  i think they conflict with certain accelerators for
entering non-latin characters, although perhaps only on other OSes.

also, these are weird since i believe that we remap alt-up/down to page up/down
and ctrl-alt-up/down to home/end on chromebooks.  it's best to stay as far away
from that mess as possible.

i used alt-comma and alt-period for similar actions in the old X window manager.
 any reason that those, or their ctrl- equivalents, couldn't be used here
instead?

[sadrul, 2012/04/25 16:04:21]

I changed the bindings to the ones suggested in the bug (alt- []-=+)

+    SNAP_WINDOW_LEFT },
+  { ui::ET_TRANSLATED_KEY_PRESS, ui::VKEY_RIGHT, false, true, true,
+    SNAP_WINDOW_RIGHT },
   { ui::ET_TRANSLATED_KEY_PRESS, ui::VKEY_F1, true, true, false, SHOW_OAK },
   { ui::ET_TRANSLATED_KEY_PRESS, ui::VKEY_1, false, false, true,
     SELECT_WIN_0 },