From: frank Date: Tue, 17 Jan 2012 06:46:17 +0000 (+0100) Subject: saving uncommitted changes in /etc prior to emerge run X-Git-Url: https://git.uhu-banane.de/?a=commitdiff_plain;h=ab03eb7c76bcc9b2fa37440664bbda84b1f9f05e;p=config%2Fbruni%2Fetc.git saving uncommitted changes in /etc prior to emerge run --- diff --git a/gconf/gconf.xml.defaults/%gconf-tree-de.xml b/gconf/gconf.xml.defaults/%gconf-tree-de.xml index e462c580..22429f78 100644 --- a/gconf/gconf.xml.defaults/%gconf-tree-de.xml +++ b/gconf/gconf.xml.defaults/%gconf-tree-de.xml @@ -2,6 +2,455 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Der Schlüssel »/apps/metacity/global_keybindings/run_command_window_screenshot« legt eine Tastenkombination fest, auf deren Eingabe hin der vom diesem Schlüssel angegebene Befehl ausgeführt wird. + + + + + Der Schlüssel »/apps/metacity/global_keybindings/run_command_screenshot« legt eine Tastenkombination fest, auf deren Eingabe hin der vom diesem Schlüssel angegebene Befehl ausgeführt wird. + + + + + Die Schlüssel »/apps/metacity/global_keybindings/run_command_N« legen Tastenkombinationen fest, auf deren Eingabe hin diese Befehle ausgeführt werden. Die Eingabe der Tastenkombination run_command_N führt dazu, dass command_N ausgeführt wird. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Der Name einer Arbeitsfläche. + + + + + + + Einige Anwendungen halten sich nicht an Spezifikationen, wodurch Fehlverhalten bei Fensterverwaltungen entstehen können. Diese Option schaltet Metacity in einen rigoros vorbildlichen Modus, der eine konsistentere Benutzerumgebung bringt, wenn Sie keine sich falsch verhaltenden Anwendungen benötigen. + + + + + Falls dieser Schlüssel gesetzt ist, arbeitet Metacity anwendungs- und nicht fensterorientiert. Das Konzept ist etwas abstrakt, aber generell verhält sich der Computer im anwendungsorientierten Modus eher wie ein Mac und weniger wie Windows. Wenn Sie im anwendungsorientierten Modus ein Fenster fokussieren, werden alle zur Anwendung gehörigen Fenster angehoben. Außerdem werden in diesem Modus Mausklicks zum Fokussieren nicht an Fenster von anderen Anwendungen weitergereicht. Allerdings ist der anwendungsorientierte Modus momentan in weiten Teilen nicht implementiert. + + + + + Falls dieser Schlüssel wahr ist, gibt Metacity dem Benutzer weniger Rückmeldungen durch Einsatz von Gitterrahmen, keinen Animationen und anderem. Dies bedeutet für viele eine signifikante Verschlechterung der Benutzerfreundlichkeit, erlaubt es jedoch älteren Anwendungen und Terminal-Servern von Drittanbietern auch dann zu funktionieren, wenn dies sonst nicht möglich wäre. Die Gitterrahmenfunktion wird jedoch nicht verwendet, wenn die Barrierefreiheit eingeschaltet ist. + + + + + Legt fest, ob Metacity als Compositing-Verwaltung agiert. + + + + + Legt fest, wie Metacity visuell darstellen soll, dass die Systemglocke ausgelöst wurde oder ein anderer »Piepser« seitens der Anwendung erfolgt ist. Zulässige Werte: »fullscreen« (Schwarz/weiß-Blinken im Vollbild) sowie »frame_flash« (Titelbar der betroffenen Anwendung blinkt). Ist die Anwendung unbekannt, die die Glocke ausgelöst hat (bei Systemsignaltönen ist dies der Normalfall), blinkt die Titelbar des momentan fokussierten Fensters. + + + + + Legt fest, ob Anwendungen oder das System hörbare Signaltöne ausgeben können; kann in Verbindung mit der »visuellen Glocke« verwendet werden, um »stumme« Signaltöne auszugeben. + + + + + Visuelle Rückmeldungen zeigen, wenn eine Anwendung oder das System eine »Glocke« oder einen Signalton auslöst. Dies ist nützlich für Hörgeschädigte und die Arbeit in lauter Umgebung. + + + + + Anzahl der Arbeitsflächen. Die Zahl muss größer als Null sein und hat ein festgelegtes Maximum, um zu verhindern, dass Ihr Desktop durch das versehentliche Anfordern von sehr vielen Arbeitsflächen unbrauchbar wird. + + + + + Eine Zeichenkette, die für die Fenstertitel verwendete Schrift angibt. Die Größenangabe wird jedoch nur verwendet, falls die Option »titlebar_font_size« auf 0 gesetzt ist. Außerdem ist diese Funktion wirkungslos, falls die Option »titlebar_uses_desktop_font« »WAHR« ist. + + + + + Falls dieser Schlüssel gesetzt ist, wird die Option zum Setzen der Titelleistenschrift (»titlebar_font«) ignoriert und die Standard-Anwendungsschrift für Fenstertitel verwendet. + + + + + Das Thema legt unter anderem das Aussehen von Fensterrahmen und Titelleisten fest. + + + + + Die Zeitverzögerung, bevor ein Fenster angehoben wird, falls »auto_raise« auf WAHR gesetzt ist. Die Verzögerung wird in Millisekunden angegeben. + + + + + Falls dieser Schlüssel gesetzt ist und der Fokusmodus entweder »sloppy« oder »mouse« ist, wird das fokussierte Fenster automatisch nach der vom Schlüssel »auto_raise_delay« angegeben Zeit angehoben. Dies hat weder Einfluss auf das Klicken auf ein Fenster um es anzuheben, noch auf das Überfahren eines Fensters bei Ziehen-und-Ablegen. + + + + + Dieser Schlüssel legt fest, was bei einem Rechtsklick auf die Titelleiste geschehen soll. Zulässige Werte: »toggle_shade« (Fenster ein- bzw. ausrollen), »toggle_maximize« (Fenster maximieren bzw. wiederherstellen), »toggle_maximize_horizontally« und »toggle_maximize_vertically« (Fenster horizontal bzw. vertikal maximieren), »minimize« (Fenster minimieren), »shade« (Fenster einrollen), »menu« (Fenstermenü anzeigen), »lower« (Fenster in den Hintergrund) sowie »none« (nichts tun). + + + + + Dieser Schlüssel legt fest, was bei einem Klick mit der mittleren Maustaste auf die Titelleiste geschehen soll. Zulässige Werte: »toggle_shade« (Fenster ein- bzw. ausrollen), »toggle_maximize« (Fenster maximieren bzw. wiederherstellen), »toggle_maximize_horizontally« und »toggle_maximize_vertically« (Fenster horizontal bzw. vertikal maximieren), »minimize« (Fenster minimieren), »shade« (Fenster einrollen), »menu« (Fenstermenü anzeigen), »lower« (Fenster in den Hintergrund) sowie »none« (nichts tun). + + + + + Dieser Schlüssel legt fest, was bei einem Doppelklick auf die Titelleiste geschehen soll. Zulässige Werte sind: »toggle_shade« (Fenster ein- bzw. ausrollen), »toggle_maximize« (Fenster maximieren bzw. wiederherstellen), »toggle_maximize_horizontally« und »toggle_maximize_vertically« (Fenster horizontal bzw. vertikal maximieren), »minimize« (Fenster minimieren), »shade« (Fenster einrollen), »menu« (Fenstermenü anzeigen), »lower« (Fenster in den Hintergrund) sowie »none« (nichts tun). + + + + + Das Abschalten dieser Option kann zu einem fehlerhaften Verhalten führen. Deshalb werden Benutzer dazu angehalten sie unverändert zu lassen. Viele Aktivitäten (z.B Klicken in den Client-Bereich, Verschieben oder Verändern der Größe eines Fensters) führen normalerweise als Nebeneffekt dazu, dass das Fenster in den Vordergrund geholt wird. Wenn diese Option abgeschaltet ist, wovon dringend abgeraten wird, werden diese Aktivitäten von der Benutzerinformation entkoppelt und Anfragen von Anwendungen zum Anheben ignoriert. Lesen Sie http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6. Trotzdem kann das Fenster durch einen Linksklick mit gedrückter linker Maustaste, durch einen Klick auf die Fenster-Dekoration oder durch spezielle Anforderung des Arbeitsflächenumschalters bzw. der Fensterliste weiter in den Vordergrund geholt werden. Dieser Schlüssel ist im »Klicken-für-Fokus«-Modus momentan deaktiviert. Die Möglichkeiten ein Fenster in den Vordergrund zu holen, wenn »raise_on_click« abgeschaltet ist, enthalten auch nicht programmatische Anforderungen durch Anwendungen. Diese werden ohne Beachtung ihres Grundes ignoriert. Falls Sie ein Software-Entwickler sind und Sie Beschwerden von Benutzern erhalten, dass Ihre Software nicht richtig funktioniert, weil diese Option abgeschaltet ist, antworten Sie, dass es die Schuld des Benutzers ist. Der Benutzer sollte darauf hingewiesen werden diese Option wieder einzuschalten oder mit den Konsequenzen leben zu müssen. + + + + + Dieser Schlüssel bietet erweiterte Kontrolle darüber, wie neu erstellte Fenster den Fokus erhalten. Zulässige Werte: »smart« benutzt den vom Nutzer festgelegten Fokusmodus, »strict« erteilt von einer Befehlszeile gestarteten Fenstern keinen Fokus. + + + + + Der Modus des Fensterfokus legt fest, wie Fenster aktiviert werden. Er hat drei mögliche Werte: »click« führt dazu, dass Fenster angeklickt werden müssen, um fokussiert zu werden, »sloppy« bewirkt, dass Fenster fokussiert werden, sobald sich der Mauszeiger über dem Fenster befindet, und das Verhalten bei »mouse« entspricht dem von »sloppy« mit dem Zusatz, dass den Fenstern der Fokus wieder genommen wird, sobald der Mauszeiger das Fenster verlässt. + + + + + Die Anordnung der Knöpfe auf der Titelleiste. Der Wert muss eine Zeichenkette der Form »menu:minimize,maximize,spacer,close« sein. Der Doppelpunkt trennt die rechte von der linken Ecke der Titelleiste und die Namen der einzelnen Knöpfe sind durch Kommas getrennt. Mehrfachnennungen von Knopfnamen sind nicht erlaubt. Unbekannte Knopfnamen werden ohne Ausgabe ignoriert, sodass in zukünftigen Versionen dieses Fenstermanagers Knöpfe hinzugefügt werden können, ohne die Konfiguration älterer Versionen zu beeinflussen. + + + + + Falls dieser Schlüssel wahr ist, so wird mit der rechten Taste die Größe angepasst, und mit der mittleren Taste und der Zusatztaste »mouse_button_modifier« ein Menü angezeigt. Wenn er falsch ist, ist es genau anders herum. + + + + + + + + diff --git a/gconf/gconf.xml.defaults/%gconf-tree-en_GB.xml b/gconf/gconf.xml.defaults/%gconf-tree-en_GB.xml index ca71bca8..72dd50ab 100644 --- a/gconf/gconf.xml.defaults/%gconf-tree-en_GB.xml +++ b/gconf/gconf.xml.defaults/%gconf-tree-en_GB.xml @@ -2,6 +2,455 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The /apps/metacity/global_keybindings/run_command_window_screenshot key defines a keybinding which causes the command specified by this setting to be invoked. + + + + + The /apps/metacity/global_keybindings/run_command_screenshot key defines a keybinding which causes the command specified by this setting to be invoked. + + + + + The /apps/metacity/global_keybindings/run_command_N keys define keybindings that correspond to these commands. Pressing the keybinding for run_command_N will execute command_N. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The name of a workspace. + + + + + + + Some applications disregard specifications in ways that result in window manager misfeatures. This option puts Metacity in a rigorously correct mode, which gives a more consistent user interface, provided one does not need to run any misbehaving applications. + + + + + If true, then Metacity works in terms of applications rather than windows. The concept is a bit abstract, but in general an application-based setup is more like the Mac and less like Windows. When you focus a window in application-based mode, all the windows in the application will be raised. Also, in application-based mode, focus clicks are not passed through to windows in other applications. Application-based mode is, however, largely unimplemented at the moment. + + + + + If true, metacity will give the user less feedback by using wireframes, avoiding animations, or other means. This is a significant reduction in usability for many users, but may allow legacy applications to continue working, and may also be a useful tradeoff for terminal servers. However, the wireframe feature is disabled when accessibility is on. + + + + + Determines whether Metacity is a compositing manager. + + + + + Tells Metacity how to implement the visual indication that the system bell or another application 'bell' indicator has been rung. Currently there are two valid values, "fullscreen", which causes a fullscreen white-black flash, and "frame_flash" which causes the titlebar of the application which sent the bell signal to flash. If the application which sent the bell is unknown (as is usually the case for the default "system beep"), the currently focused window's titlebar is flashed. + + + + + Determines whether applications or the system can generate audible 'beeps'; may be used in conjunction with 'visual bell' to allow silent 'beeps'. + + + + + Turns on a visual indication when an application or the system issues a 'bell' or 'beep'; useful for the hard-of-hearing and for use in noisy environments. + + + + + Number of workspaces. Must be more than zero, and has a fixed maximum to prevent making the desktop unusable by accidentally asking for too many workspaces. + + + + + A font description string describing a font for window titlebars. The size from the description will only be used if the titlebar_font_size option is set to 0. Also, this option is disabled if the titlebar_uses_desktop_font option is set to true. + + + + + If true, ignore the titlebar_font option, and use the standard application font for window titles. + + + + + The theme determines the appearance of window borders, titlebar, and so forth. + + + + + The time delay before raising a window if auto_raise is set to true. The delay is given in thousandths of a second. + + + + + If set to true, and the focus mode is either "sloppy" or "mouse" then the focused window will be automatically raised after a delay specified by the auto_raise_delay key. This is not related to clicking on a window to raise it, nor to entering a window during drag-and-drop. + + + + + This option determines the effects of right-clicking on the title bar. Current valid options are 'toggle_shade', which will shade/unshade the window, 'toggle_maximize' which will maximise/unmaximise the window, 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' which will maximise/unmaximise the window in that direction only, 'minimize' which will minimise the window, 'shade' which will roll the window up, 'menu' which will display the window menu, 'lower' which will put the window behind all the others, and 'none' which will not do anything. + + + + + This option determines the effects of middle-clicking on the title bar. Current valid options are 'toggle_shade', which will shade/unshade the window, 'toggle_maximize' which will maximise/unmaximise the window, 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' which will maximise/unmaximise the window in that direction only, 'minimize' which will minimise the window, 'shade' which will roll the window up, 'menu' which will display the window menu, 'lower' which will put the window behind all the others, and 'none' which will not do anything. + + + + + This option determines the effects of double-clicking on the title bar. Current valid options are 'toggle_shade', which will shade/unshade the window, 'toggle_maximize' which will maximise/unmaximise the window, 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' which will maximise/unmaximise the window in that direction only, 'minimize' which will minimise the window, 'shade' which will roll the window up, 'menu' which will display the window menu, 'lower' which will put the window behind all the others, and 'none' which will not do anything. + + + + + Setting this option to false can lead to buggy behaviour, so users are strongly discouraged from changing it from the default of true. Many actions (e.g. clicking in the client area, moving or resizing the window) normally raise the window as a side-effect. Setting this option to false, which is strongly discouraged, will decouple raising from other user actions, and ignore raise requests generated by applications. See http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6. Even when this option is false, windows can still be raised by an alt-left-click anywhere on the window, a normal click on the window decorations, or by special messages from pagers, such as activation requests from tasklist applets. This option is currently disabled in click-to-focus mode. Note that the list of ways to raise windows when raise_on_click is false does not include programmatic requests from applications to raise windows; such requests will be ignored regardless of the reason for the request. If you are an application developer and have a user complaining that your application does not work with this setting disabled, tell them it is _their_ fault for breaking their window manager and that they need to change this option back to true or live with the "bug" they requested. + + + + + This option provides additional control over how newly created windows get focus. It has two possible values; "smart" applies the user's normal focus mode, and "strict" results in windows started from a terminal not being given focus. + + + + + The window focus mode indicates how windows are activated. It has three possible values; "click" means windows must be clicked in order to focus them, "sloppy" means windows are focused when the mouse enters the window, and "mouse" means windows are focused when the mouse enters the window and unfocused when the mouse leaves the window. + + + + + Arrangement of buttons on the titlebar. The value should be a string, such as "menu:minimize,maximize,spacer,close"; the colon separates the left corner of the window from the right corner, and the button names are comma-separated. Duplicate buttons are not allowed. Unknown button names are silently ignored so that buttons can be added in future metacity versions without breaking older versions. A special spacer tag can be used to insert some space between two adjacent buttons. + + + + + Set this to true to resize with the right button and show a menu with the middle button while holding down the key given in "mouse_button_modifier"; set it to false to make it work the opposite way around. + + + + + + + + diff --git a/gconf/gconf.xml.defaults/%gconf-tree-ru.xml b/gconf/gconf.xml.defaults/%gconf-tree-ru.xml index ba5d52ce..2508cab7 100644 --- a/gconf/gconf.xml.defaults/%gconf-tree-ru.xml +++ b/gconf/gconf.xml.defaults/%gconf-tree-ru.xml @@ -2,6 +2,455 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Ключ /apps/metacity/global_keybindings/run_command_window_screenshot определяет комбинацию клавиш, которая вызывает запуск команды, определённой в данном ключе. + + + + + Ключ /apps/metacity/global_keybindings/run_command_screenshot определяет комбинацию клавиш, которая вызывает запуск команды, определённой в данном ключе. + + + + + Ключи /apps/metacity/global_keybindings/run_command_N определяют комбинации клавиш, которые соответствуют этим командам. Нажатие комбинации run_command_N запустит на выполнение command_N. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Имя рабочего места. + + + + + + + Некоторые приложения игнорируют спецификации, поэтому в менеджер окон встроены возможности для обхода ошибок в этих приложениях. Этот ключ переводит Metacity в режим строгого соответствия спецификациям, что даёт всем окнам более последовательный внешний вид, но при этом приложения с ошибками могут работать неправильно. + + + + + Если этот ключ установлен, Metacity работает с приложениями, а не с окнами. Архитектура, основанная на приложениях, больше похожа на системы Mac, чем на Windows. При активизации окна в режиме, основанном на приложениях, поднимаются все окна приложения. Кроме того, в режиме, основанном на приложениях, щелчки мышью не передаются в окна других приложений. Реализация режима, основанного на приложениях, в настоящий момент ещё весьма далека от завершения. + + + + + Если этот ключ установлен, Metacity предоставляет пользователю меньше обратной связи за счёт использования контурных рамок, отключения анимации и другими способами. Это существенно снижает удобство для многих пользователей, но позволяет продлить срок службы старых приложений, а также может быть полезно для терминальных серверов. Следует отметить, что отображение контурной рамки отключается при включении специальных возможностей. + + + + + Определяет, является ли Metacity менеджером композиции. + + + + + Указывает Metacity, как реализовать индикацию звукового сигнала. Сейчас существуют два значения этого ключа: «fullscreen» вызывает чёрно-белое мерцание экрана, «frame_flash» вызывает мерцание строки заголовка того окна, приложение в котором подало звуковой сигнал. Если неизвестно, какое приложение подало сигнал, мерцать будет заголовок активного окна. + + + + + Определяет, могут ли приложения или система подавать слышимые звуковые сигналы. Может быть использован совместно с ключом «видимый сигнал», чтобы подавать бесшумные «гудки». + + + + + Включает визуальную индикацию системного звукового сигнала. Это полезно для слабослышащих и при работе в шумном окружении. + + + + + Число рабочих мест. Должно быть больше нуля. Имеет фиксированный максимум, чтобы нельзя было разрушить среду, запросив слишком много рабочих мест. + + + + + Строка описания шрифта для заголовка окна. Размер из описания будет использоваться, только если для параметра titlebar_font_size выбрано значение 0. Этот параметр также отключён, если для параметра titlebar_uses_desktop_font выбрано значение «истина». + + + + + Если этот ключ установлен, то параметр titlebar_font игнорируется, и для заголовков окон используется стандартный шрифт приложения. + + + + + Тема определяет внешний вид границ окна, заголовка окна и так далее. + + + + + Время задержки всплывания окна, если установлен ключ auto_raise. Задержка измеряется в миллисекундах. + + + + + Если этот ключ установлен, и режим фокуса либо «sloppy», либо «mouse», тогда окно, находящееся в фокусе, будет автоматически поднято по истечении задержки, указанной в ключе auto_raise_delay. Это не касается ни щелчка по окну для его поднятия, ни перехода в окно путём перетаскивания в него. + + + + + Этот ключ определяет действие щелчка правой кнопкой мыши по заголовку окна. В настоящее время допустимыми значениями являются «toggle_shade» (скручивает окно в полоску или раскатывает обратно), «toggle_maximize» (разворачивает окно или восстанавливает обычный размер), «toggle_maximize_vertically» и «toggle_maximize_horizontally» (разворачивает окно только в одном направлении или восстанавливает обычный размер), «minimize» (сворачивает окно), «shade» (скрутит окно вверх), «menu» (показывает меню окна), «lower» (помещает окно под другими) и, наконец, «none» (не делает ничего). + + + + + Этот ключ определяет действие щелчка средней кнопкой мыши по заголовку окна. В настоящее время допустимыми значениями являются «toggle_shade» (скручивает окно в полоску или раскатывает обратно), «toggle_maximize» (разворачивает окно или восстанавливает обычный размер), «toggle_maximize_vertically» и «toggle_maximize_horizontally» (разворачивает окно только в одном направлении или восстанавливает обычный размер), «minimize» (сворачивает окно), «shade» (скрутит окно вверх), «menu» (показывает меню окна), «lower» (помещает окно под другими) и, наконец, «none» (не делает ничего). + + + + + Этот ключ определяет действие двойного щелчка на заголовке окна. В настоящее время допустимыми значениями являются «toggle_shade» (скручивает окно в полоску или раскатывает обратно), «toggle_maximize» (разворачивает окно или восстанавливает обычный размер), «toggle_maximize_vertically» и «toggle_maximize_horizontally» (разворачивает окно только в одном направлении или восстанавливает обычный размер), «minimize» (сворачивает окно), «shade» (скрутит окно вверх), «menu» (показывает меню окна), «lower» (помещает окно под другими) и, наконец, «none» (не делает ничего). + + + + + Если этот параметр не установлен, возможно ошибочное поведение, поэтому мы настоятельно рекомендуем воздержаться от изменений значения по умолчанию. Многие действия (например, щелчок по окну, перемещение окна или изменение его размера) обычно поднимают окно на передний план. Если этот параметр не установлен, что настоятельно не рекомендуется, поднятие на передний план будет отделено от других действий и запросы на поднятие окна на передний план, поступающие от приложений, будут игнорироваться. Смотрите http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6. Даже если этот параметр не установлен, окна могут быть подняты на передний план с помощью одновременного нажатия на клавишу Alt и щелчка левой кнопкой мыши по любой области окна, щелчка по заголовку окна или специальных сообщений, таких как запросы на поднятие окна. Это поведение в данный момент выключено в режиме щелчка для передачи фокуса. Заметьте, что обозначенный выше список не включает в себя программные запросы от приложений о поднятии окон на передний план, такие запросы будут проигнорированы независимо от причины. Если вы разработчик приложения и вам приходится слушать замечания пользователей, что ваше приложение работает некорректно, укажите им, что _они_ допустили ошибку, выключив этот параметр и сломав менеджер окон, и что они должны вернуть этому параметру значение по умолчанию или прекратить посылать замечания. + + + + + Этот параметр предоставляет дополнительное управление тем, как новые окна получают фокус. Он имеет два возможных значения. Значение «smart» применяет обычный режим фокуса пользователя, а «strict» приводит к тому, что окна, запущенные из терминала, не получают фокус. + + + + + Режим передачи фокуса в окно определяет, как активируются окна. У этого режима три возможных значения; «click» — означает, что для активации окна на нём надо щелкнуть; «sloppy» — означает, что окно активируется, когда на него перемещается указатель мыши; «mouse» — означает, что окно активируется, когда в него перемещается указатель мыши, и перестает быть активным, когда указатель мыши выходит из него. + + + + + Расположение кнопок в заголовке окна. Значение должно быть строкой, например, «menu:minimize,maximize,spacer,close». Двоеточие разделяет левый и правый углы окна, имена кнопок разделяются запятыми. Дублирование кнопок не допускается. Неизвестные имена кнопок всегда игнорируются без уведомления, так что кнопки могут быть добавлены в будущих версиях, не нарушая предыдущих. Специальный элемент spacer может использоваться для вставки пробела между двумя кнопками. + + + + + Если ключ установлен, размер окна изменяется правой кнопкой мыши, а меню показывается средней, если удерживается клавиша, заданная в «mouse_button_modifier». Если ключ не установлен, функции кнопок мыши меняются местами. + + + + + + + + diff --git a/gconf/gconf.xml.defaults/%gconf-tree-vi.xml b/gconf/gconf.xml.defaults/%gconf-tree-vi.xml index 1dfc3eec..c37be828 100644 --- a/gconf/gconf.xml.defaults/%gconf-tree-vi.xml +++ b/gconf/gconf.xml.defaults/%gconf-tree-vi.xml @@ -2,6 +2,362 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Những khóa «/apps/metacity/global_keybindings/run_command_window_screenshot» định nghĩa tổ hợp phím, khi được nhấn, sẽ thực hiện lệnh được ghi trong khóa này. + + + + + Những khóa «/apps/metacity/global_keybindings/run_command_screenshot» định nghĩa tổ hợp phím, khi được nhấn, sẽ thực hiện lệnh được ghi trong khóa này. + + + + + Những khóa «/apps/metacity/global_keybindings/run_command_N» định nghĩa tổ hợp phím tương ứng với những lệnh này. Hãy nhấn phím tổ hợp của «run_command_N» để thực hiện «command_N». + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Tên của vùng làm việc. + + + + + + + Một số ứng dụng riêng bỏ qua đặc tả, gây ra bộ quản lý cửa sổ không hoạt động cho đúng. Tùy chọn này đặt Metacity trong chế độ đúng chính xác, mà bảo tồn một giao diện người dùng thống nhất hơn, nếu bạn không cần chạy ứng dụng nào chạy sai. + + + + + Nếu bật thì trình Metacity hoạt động như theo ứng dụng hơn là theo cửa sổ. Khái niệm này hơi trừu tượng, nhưng nói chung một thiết lập dựa trên ứng dụng thì giống như Mac hơn Windows. Khi bạn đặt tiêu điểm lên một cửa sổ trong chế độ dựa trên ứng dụng, mọi cửa sổ trong ứng dụng đó sẽ được hiển thị. Ngoài ra, trong chế độ dựa trên ứng dụng, nhấn tiêu điểm không được chuyển cho cửa sổ của ứng dụng khác. Ngoài ra chế độ dựa trên ứng dụng chưa được làm tại thời điểm này. + + + + + Nếu bật thì trình metacity sẽ cho người dùng xem phản hồi ít hơn bằng cách dùng đường viền, tránh hoạt ảnh, hoặc bằng cách khác. Phần lớn người dùng sẽ thấy biết tính hữu dụng đã giảm xuống, nhưng mà có lẽ tùy chọn này sẽ cho phép ứng dụng cũ hơn tiếp tục hoạt động, và có lẽ cũng là thoả hiệp có ích cho trình phục vụ thiết bị cuỗi. Tuy nhiên, tính năng đường viền đã tắt khi khả năng truy cập được bật. + + + + + Quyết định nếu trình Metacity là bộ quản lý ghép lại hay không. + + + + + Cho Metacity biết cách thực hiện cái hiển thị khi có chuông từ hệ thống hoặc từ ứng dụng khác. Hiện thời chỉ có hai gia trị hợp lệ là «fullscreen» (toàn màn hình), làm chớp trắng-đen toàn màn hình, và «frame_flash» (khung chớp) làm chớp thanh tựa đề của ứng dụng rung chuông. Nếu không biết ứng dụng nào rung chuông (trường hợp thường khi là «chuông hệ thống»), tựa đề ứng dụng đang có tiêu điểm sẽ chớp. + + + + + Xác định ứng dụng hoặc hệ thống có thể phát sinh tiến «bíp» hay không; có thể dùng chung với «cái chuông hình» để cho phép «bíp» câm. + + + + + Bật chỉ thị trực quan khi ứng dụng hoặc hệ thống rung chuông; rất hữu dụng trong môi trường ồn ào hoặc không nghe rõ. + + + + + Số vùng làm việc. Phải là số lớn hơn số không, và có giới hạn cố định lớn nhất (để tránh việc hủy màn hình nền một cách bất ngờ bởi vì một yêu cầu 34 tỉ vùng làm việc). + + + + + Chuỗi mô tả phông chữ mô tả phông chữ cho tựa đề cửa sổ. Tuy nhiên kích thước theo mô tả này sẽ chỉ được dùng nếu tùy chọn « titlebar_font_size » (kích thước phông chữ thanh tựa đề) được đặt là 0. Ngoài ra, tùy chọn này sẽ tắt nếu tùy chọn « titlebar_uses_desktop_font » (thanh đựa đề dùng phông chữ của màn hình làm việc) bật. + + + + + Nếu bật, bỏ qua tùy chọn «titlebar_font», và dùng phông chữ ứng dụng chuẩn cho tựa đề cửa sổ. + + + + + Sắc thái xác định diện mạo của đường viền cửa sổ, thanh tựa đề, và nhiều thứ khác. + + + + + Khoảng chờ trước khi hiện cửa sổ nếu đặt «auto_raise». Khoảng chờ tính theo số phần ngàn giây. + + + + + Nếu bật, và chế độ tiêu điểm hoạc là « sloppy » (luộm thuộm) hay « mouse » (con chuột) thì cửa sổ có tiêu điểm sẽ được nâng lên tự động, sau một thời gian hoãn được xác định bởi khoá « auto_raise_delay » (hoãn nâng lên tự động). Cái này không liên quan đến việc nhắp vào cửa sổ để nâng nó lên, cũng không liên quan đến việc vào cửa sổ trong khi kéo và thả. + + + + + Tùy chọn này quyết định tác dụng của việc nhấn-giữa chuột trên thanh tựa. Tùy chọn hợp lệ hiện thời là: + • toggle_shade tạo bóng/thôi tạo bóng cửa sổ + • toggle_maximize phóng to/thôi phóng to cửa sổ + • toggle_maximize_horizontally phóng to cửa sổ theo chiều ngang + • toggle_maximize_vertically phóng to cửa sổ theo chiều dọc + • minimize thu nhỏ cửa sổ + • shade cuộn cửa sổ lên + • menu hiển thị trình đơn cửa sổ + • lower đặt cửa sổ vào nền sau các cửa sổ khác + • none không làm gì. + + + + + Tùy chọn này quyết định tác dụng của việc nhấn-giữa chuột trên thanh tiêu đề. Tùy chọn hợp lệ hiện thời là: + • toggle_shade tạo bóng/thôi tạo bóng cửa sổ + • toggle_maximize phóng to/thôi phóng to cửa sổ + • toggle_maximize_horizontally phóng to cửa sổ theo chiều ngang + • toggle_maximize_vertically phóng to cửa sổ theo chiều dọc + • minimize thu nhỏ cửa sổ + • shade cuộn cửa sổ lên + • menu hiển thị trình đơn cửa sổ + • lower đặt cửa sổ vào nền sau các cửa sổ khác + • none không làm gì. + + + + + Tùy chọn này quyết định tác dụng của việc nhấn đúp chuột trên thanh tiêu đề. Tùy chọn hợp lệ hiện thời là: + • toggle_shade tạo bóng/thôi tạo bóng cửa sổ + • toggle_maximize phóng to/thôi phóng to cửa sổ + • toggle_maximize_horizontally phóng to cửa sổ theo chiều ngang + • toggle_maximize_vertically phóng to cửa sổ theo chiều dọc + • minimize thu nhỏ cửa sổ + • shade cuộn cửa sổ lên + • menu hiển thị trình đơn cửa sổ + • lower đặt cửa sổ vào nền sau các cửa sổ khác + • none không làm gì. + + + + + + + + + Tùy chọn này cung cấp khả năng thêm điều khiển cách gán tiêu điểm cho cửa sổ mới tạo. Nó có hai giá trị có thể : + • smart áp dụng chế độ tiêu điểm bình thường của người dùng đó, + • strict gây ra cửa sổ không có tiêu điểm nếu được tạo từ thiết bị cuối. + + + + + Chế độ tiêu điểm cửa sổ chỉ ra cách cửa sổ được kích hoạt. Nó có thể có ba giá trị sau: «nhắp» (click) nghĩa là cửa sổ được nhấn để nhận tiêu điểm, «luộn thuộm» (sloppy) nghĩa là cửa sổ nhận tiêu điểm nếu con chuột đi ngang qua cửa sổ, và «chuột» (mouse) nghĩa là cửa sổ nhận tiêu điểm khi con chuột đi vào cửa sổ và mất tiêu điểm khi con chuột rời khỏi cửa sổ. + + + + + Bố trí các nút trên thanh tiêu đề. Giá trị nên là một chuỗi như là « menu:minimize,maximize,close » (trình đơn:cực tiểu hóa,cực đại hóa,đóng), dấu hai chấm tách góc trái ra khỏi góc phải cửa sổ, tên các nút được cách nhau bởi dấu phẩy. Không cho phép nút đúp nào. Tên nút không rõ sẽ được bỏ qua để cho các nút tiếp tục được bổ sung vào các phiên bản tiếp theo của metacity mà không phá vỡ phiên bản cũ. Một thẻ phân cách đặc biệt có thể được dùng để chèn khoảng cách vào giữa hai nút kề nhau. + + + + + + + + diff --git a/gconf/gconf.xml.defaults/%gconf-tree.xml b/gconf/gconf.xml.defaults/%gconf-tree.xml index 22839731..57c2ab2b 100644 --- a/gconf/gconf.xml.defaults/%gconf-tree.xml +++ b/gconf/gconf.xml.defaults/%gconf-tree.xml @@ -1,6 +1,158 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1005,6 +1157,1186 @@ + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Control><Shift><Alt>Down + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Control><Shift><Alt>Up + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Control><Shift><Alt>Right + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Control><Shift><Alt>Left + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>F8 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>F7 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>F4 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>F9 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>F5 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>F10 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>space + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + + + gnome-screenshot --window + + + The /apps/metacity/global_keybindings/run_command_window_screenshot + key defines a keybinding which causes the command specified + by this setting to be invoked. + + + + + + + gnome-screenshot + + + The /apps/metacity/global_keybindings/run_command_screenshot + key defines a keybinding which causes the command specified + by this setting to be invoked. + + + + + + + + + + The /apps/metacity/global_keybindings/run_command_N + keys define keybindings that correspond to these commands. + Pressing the keybinding for run_command_N will + execute command_N. + + + + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>Print + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + Print + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>F2 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Alt>F1 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Control><Alt>d + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + <Control><Alt>Escape + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + <Alt>Escape + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + <Alt>F6 + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + <Control><Alt>Tab + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + <Alt>Tab + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + +This keybinding may be reversed by holding down the "shift" key; therefore, "shift" cannot be one of the keys it uses. + + + + + + <Control><Alt>Down + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Control><Alt>Up + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Control><Alt>Right + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + <Control><Alt>Left + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + The format looks like "<Control>a" or "<Shift><Alt>F1". + +The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action. + + + + + + disabled + + + The keybinding that runs the correspondingly-numbered + command in /apps/metacity/keybinding_commands + + The format looks like "<Control>a" or + "<Shift><Alt>F1". + + The parser is fairly liberal and allows lower or upper case, + and also abbreviations such as "<Ctl>" and + "<Ctrl>". If you set the option to the special string + "disabled", then there will be no keybinding for this + action. + + + + + + + + + + + + The name of a workspace. + + + + + + + + + + Some applications disregard specifications in ways that result in + window manager misfeatures. This option puts Metacity in a + rigorously correct mode, which gives a more consistent user + interface, provided one does not need to run any misbehaving + applications. + + + + + + + + If true, then Metacity works in terms of applications rather than + windows. The concept is a bit abstract, but in general an + application-based setup is more like the Mac and less like + Windows. When you focus a window in application-based mode, all + the windows in the application will be raised. Also, in + application-based mode, focus clicks are not passed through to + windows in other applications. Application-based mode is, + however, largely unimplemented at the moment. + + + + + + + + If true, metacity will give the user less feedback by using + wireframes, avoiding animations, or other means. This is a + significant reduction in usability for many users, but may allow + legacy applications to continue working, and may also be a + useful tradeoff for terminal servers. However, the wireframe + feature is disabled when accessibility is on. + + + + + + + + Determines whether Metacity is a compositing manager. + + + + + + + fullscreen + + + Tells Metacity how to implement the visual indication that the + system bell or another application 'bell' indicator has been + rung. Currently there are two valid values, "fullscreen", which + causes a fullscreen white-black flash, and "frame_flash" which + causes the titlebar of the application which sent the bell signal + to flash. If the application which sent the bell is unknown (as + is usually the case for the default "system beep"), the currently + focused window's titlebar is flashed. + + + + + + + + Determines whether applications or the system can generate + audible 'beeps'; may be used in conjunction with 'visual bell' to + allow silent 'beeps'. + + + + + + + + Turns on a visual indication when an application or the system + issues a 'bell' or 'beep'; useful for the hard-of-hearing and for + use in noisy environments. + + + + + + + + Number of workspaces. Must be more than zero, and has a fixed + maximum to prevent making the desktop unusable by accidentally + asking for too many workspaces. + + + + + + + Sans Bold 10 + + + A font description string describing a font for window + titlebars. The size from the description will only be used if the + titlebar_font_size option is set to 0. Also, this option is + disabled if the titlebar_uses_desktop_font option is set to true. + + + + + + + + If true, ignore the titlebar_font + option, and use the standard application font for window + titles. + + + + + + + Clearlooks + + + The theme determines the appearance of window borders, + titlebar, and so forth. + + + + + + + + The time delay before raising a window if auto_raise is set to + true. The delay is given in thousandths of a second. + + + + + + + + If set to true, and the focus mode is either "sloppy" or "mouse" + then the focused window will be automatically raised after a + delay specified by the auto_raise_delay key. This is not related + to clicking on a window to raise it, nor to entering a window + during drag-and-drop. + + + + + + + menu + + + This option determines the effects of right-clicking on the + title bar. Current valid options are + 'toggle_shade', which will shade/unshade the window, + 'toggle_maximize' which will maximize/unmaximize the window, + 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' + which will maximize/unmaximize the window in that direction only, + 'minimize' which will minimize the window, + 'shade' which will roll the window up, + 'menu' which will display the window menu, + 'lower' which will put the window behind all the others, + and 'none' which will not do anything. + + + + + + + lower + + + This option determines the effects of middle-clicking on the + title bar. Current valid options are + 'toggle_shade', which will shade/unshade the window, + 'toggle_maximize' which will maximize/unmaximize the window, + 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' + which will maximize/unmaximize the window in that direction only, + 'minimize' which will minimize the window, + 'shade' which will roll the window up, + 'menu' which will display the window menu, + 'lower' which will put the window behind all the others, + and 'none' which will not do anything. + + + + + + + toggle_maximize + + + This option determines the effects of double-clicking on the + title bar. Current valid options are + 'toggle_shade', which will shade/unshade the window, + 'toggle_maximize' which will maximize/unmaximize the window, + 'toggle_maximize_horizontally' and 'toggle_maximize_vertically' + which will maximize/unmaximize the window in that direction only, + 'minimize' which will minimize the window, + 'shade' which will roll the window up, + 'menu' which will display the window menu, + 'lower' which will put the window behind all the others, + and 'none' which will not do anything. + + + + + + + + Setting this option to false can lead to buggy behavior, so + users are strongly discouraged from changing it from the default + of true. + + Many actions (e.g. clicking in the client area, moving or resizing the window) + normally raise the window as a side-effect. Setting this option to false, which + is strongly discouraged, will decouple raising from other user actions, and + ignore raise requests generated by applications. See + http://bugzilla.gnome.org/show_bug.cgi?id=445447#c6. + Even when this option is false, windows can + still be raised by an alt-left-click anywhere on the window, a + normal click on the window decorations, or by special messages + from pagers, such as activation requests from tasklist applets. + This option is currently disabled in click-to-focus mode. + + Note that the list of ways to raise windows when raise_on_click + is false does not include programmatic requests from + applications to raise windows; such requests will be ignored + regardless of the reason for the request. If you are an + application developer and have a user complaining that your + application does not work with this setting disabled, tell them + it is _their_ fault for breaking their window manager and that + they need to change this option back to true or live with the + "bug" they requested. + + + + + + + smart + + + This option provides additional control over how newly created + windows get focus. It has two possible values; "smart" applies + the user's normal focus mode, and "strict" results in windows + started from a terminal not being given focus. + + + + + + + click + + + The window focus mode indicates how windows are activated. + It has three possible values; "click" means windows must + be clicked in order to focus them, "sloppy" means windows + are focused when the mouse enters the window, and "mouse" means + windows are focused when the mouse enters the window and + unfocused when the mouse leaves the window. + + + + + + + menu:minimize,maximize,close + + + Arrangement of buttons on the titlebar. The + value should be a string, such as + "menu:minimize,maximize,spacer,close"; the colon separates the + left corner of the window from the right corner, and + the button names are comma-separated. Duplicate buttons + are not allowed. Unknown button names are silently ignored + so that buttons can be added in future metacity versions + without breaking older versions. + A special spacer tag can be used to insert some space between + two adjacent buttons. + + + + + + + + Set this to true to resize with the right button and show a menu + with the middle button while holding down the key given in + "mouse_button_modifier"; set it to false to make it work the + opposite way around. + + + + + + + <Alt> + + + Clicking a window while holding down this modifier key + will move the window (left click), resize the window + (middle click), or show the window menu (right click). + The middle and right click operations may be swapped + using the "resize_with_right_button" key. + Modifier is expressed as "<Alt>" or "<Super>" + for example. + + + + +