Browsing Uyghur translation

359.

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.

361.

Tells the WM 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-flash", 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.

363.

If true, then the WM 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.

365.

Some applications disregard specifications in ways that result in window manager misfeatures. This option puts the WM in a rigorously correct mode, which gives a more consistent user interface, provided one does not need to run any misbehaving applications.

367.

Defines the names that should be assigned to workspaces. If the list is too long for the current number of workspaces, names in excess will be ignored. If the list is too short, or includes empty names, missing values will be replaced with the default ("Workspace N").

371.

Select the proxy configuration mode. Supported values are "none", "manual", "auto". If this is "none", then proxies are not used. If it is "auto", the autoconfiguration URL described by the "autoconfig-url" key is used. If it is "manual", then the proxies described by "/system/proxy/http", "/system/proxy/https", "/system/proxy/ftp" and "/system/proxy/socks" will be used. Each of the 4 proxy types is enabled if its "host" key is non-empty and its "port" key is non-0. If an http proxy is configured, but an https proxy is not, then the http proxy is also used for https. If a SOCKS proxy is configured, it is used for all protocols, except that the http, https, and ftp proxy settings override it for those protocols only.

384.

If true, then connections to the proxy server require authentication. The username/password combo is defined by "/system/proxy/http/authentication-user" and "/system/proxy/http/authentication-password". This applies only to the http proxy; when using a separate https proxy, there is currently no way to specify that it should use authentication.