Bug#406447: move plugin doesn't preserve /apps/compiz/plugins/move/allscreens/options/initiate_button=<Mod4>Button1 setting

To: Enrico Zini <enrico@enricozini.org>
Cc: 406447@bugs.debian.org
Subject: Bug#406447: move plugin doesn't preserve /apps/compiz/plugins/move/allscreens/options/initiate_button=<Mod4>Button1 setting
From: Brice Goglin <Brice.Goglin@ens-lyon.org>
Date: Wed, 06 Jun 2007 22:13:10 +0200
Message-id: <[🔎] 46671556.2000300@ens-lyon.org>
Reply-to: 406447@bugs.debian.org, 406447@bugs.debian.org

Hi Enrico,

Do you still reproduce this problem with the move plugin of compiz not
preserving initiate_button setting when set to <Mod4>Button1? With
latest compiz 0.5 currently in unstable?

Thanks,
Brice

Reply to:

Follow-Ups:
- Bug#406447: move plugin doesn't preserve /apps/compiz/plugins/move/allscreens/options/initiate_button=<Mod4>Button1 setting
  - From: "Jeff Stanich" <jeffstanich@simixsolutions.com>
- Bug#406447: move plugin doesn't preserve /apps/compiz/plugins/move/allscreens/options/initiate_button=<Mod4>Button1 setting
  - From: Enrico Zini <enrico@enricozini.org>

Prev by Date: Bug#397718: black content in full-screen windows, after updating to 0.2.2
Next by Date: Bug#391228: compiz: does not work correctly with twinview
Previous by thread: Bug#397718: black content in full-screen windows, after updating to 0.2.2
Next by thread: Bug#406447: move plugin doesn't preserve /apps/compiz/plugins/move/allscreens/options/initiate_button=<Mod4>Button1 setting
Index(es):
- Date
- Thread