fvwm 4_FV7144TFATG

fvwm 4_FV7144TFATG31.2.MiscellaneousCommands31.2.1.BugOptsBugOpts[option[bool]],…Thiscommandcontrolsseveralworkaroundsforbugsinthirdpartyprograms.Theindividualoptionsareseparated

大家好,又见面了,我是你们的朋友全栈君。如果您正在找激活码,请点击查看最新教程,关注关注公众号 “全栈程序员社区” 获取激活教程,可能之前旧版本教程已经失效.最新Idea2022.1教程亲测有效,一键激活。

31.2. Miscellaneous Commands

31.2.1. BugOpts

BugOpts [option [bool]],…

This command controls several workarounds for bugs in third party programs. The individual options are separated by commas. The optional argument bool is a boolean argument and controls if the bug workaround is enabled or not. It can either be “True” or “False” to turn the option on or off, or “toggle” to switch is back and forth. If bool is omitted, the default setting is restored.

FlickeringMoveWorkaround disables ConfigureNotify events that are usually sent to an application while it is moved. If some windows flicker annoyingly while being moved, this option may help you. Note that if this problem occurs it is not an fvwm bug, it is a problem of the application.

MixedVisualWorkaround makes fvwm install the root colormap before it does some operations using the root window visuals. This is only useful when the -visual option is used to start fvwm and then only with some configurations of some servers (e.g. Exceed 6.0 with an 8 bit PseudoColor root and fvwm using a 24 bit TrueColor visual).

The ModalityIsEvil option controls whether Motif applications have the ability to have modal dialogs (dialogs that force you to close them first before you can do anything else). The default is to not allow applications to have modal dialogs. Use this option with care. Once this option is turned on, you have to restart fvwm to turn it off.

RaiseOverNativeWindows makes fvwm try to raise the windows it manages over native windows of the X server’s host system. This is needed for some X servers running under Windows, Windows NT or Mac OS X. Fvwm tries to detect if it is running under such an X server and initializes the flag accordingly.

RaiseOverUnmanaged makes fvwm try to raise the windows it manages over override_redirect windows. This is used to cope with ill-mannered applications that use long-lived windows of this sort, contrary to ICCCM conventions. It is useful with the Unmanaged style option too.

FlickeringQtDialogsWorkaround suppresses flickering of the focused window in some modules when using KDE or QT applications with application modal dialog windows. By default this option is turned on. This option may be visually disturbing for other applications using windows not managed by fvwm. Since these applications are rare it is most likely safe to leave this option at its default.

QtDragnDropWorkaround surpresses the forwarding of unknown ClientEvent messages to windows — usually this is harmless, but Qt has problems handling unrecognised ClientEvent messages. Enabling this option might therefore help for Qt applications using DragnDrop. This option is off by default.

EWMHIconicStateWorkaround is needed by EWMH compliant pagers or taskbars which represent windows which are on a different desktops as iconified. These pagers and taskbars use a version of the EWMH specification before version 1.2 (the current KDE 2 & 3 versions). These pagers and taskbars use the IconicState WM_STATE state to determine if an application is iconified. This state, according to the ICCCM, does not imply that a window is iconified (in the usual sense). Turning on this option forces fvwm to establish an equivalence between the IconicState WM_STATE state and the iconified window. This violates ICCCM compliance but should not cause big problems. By default this option is off.

With the DisplayNewWindowNames enabled, fvwm prints the name, icon name (if available), resource and class of new windows to the console. This can help in finding the correct strings to use in the Style command.

When the ExplainWindowPlacement option is enabled, fvwm prints a message to the console whenever a new window is placed or one of the commands PlaceAgain, Recapture or RecaptureWindow is used. The message explains on which desk, page, Xinerama screen and position it was placed and why. This option can be used to figure out why a specific window does not appear where you think it should.

The DebugCRMotionMethod option enables some debugging code in the ConfigureRequest handling routines of fvwm. It is not helpful for the user, but if you report a bug to the fvwm team we may ask you to enable this option.

The TransliterateUtf8 option enables transliteration during conversions from utf-8 strings. By default fvwm will not transliterate during conversion, but will fall back to alternate strings provided by the clients if conversion from utf-8 fails due to characters which have no direct correspondance in the target charecter set. Some clients however neglect to set non utf-8 properties correctly in which case this option may help.

31.2.2. BusyCursor

BusyCursor [Option bool],…

This command controls the cursor during the execution of certain commands. Option can be DynamicMenu, ModuleSynchronous, Read, Wait or *. An option must be followed by a boolean argument bool. You can use commas to separate individual options. If you set an option to “True”, then when the corresponding command is run, fvwm displays the cursor of the WAIT context of the CursorStyle command. “False” forces to not display the cursor. The default is:

BusyCursor DynamicMenu False, ModuleSynchronous False, \

  Read False, Wait False

The * option refers to all available options.

The Read option controls the PipeRead command.

The DynamicMenu option affects the DynamicPopupAction and MissingSubmenuFunction options of the AddToMenu command. If this option is set to “False”, then the busy cursor is not displayed during a dynamic menu command even if this command is a Read or PipeRead command and the Read option is set to “True”.

The ModuleSynchronous option affects the ModuleSynchronous command. If this option is set to “False”, then the busy cursor is not displayed while fvwm waits for a module started by ModuleSynchronous to complete its startup.

The Wait option affects only the root cursor. During a wait pause the root cursor is replaced by the busy cursor and fvwm is still fully functional (you can escape from the pause, see the EscapeFunc command). If you want to use this option and if you do not use the default root cursor, you must set your root cursor with the CursorStyle command.

31.2.3. ClickTime

ClickTime [delay]

Specifies the maximum delay in milliseconds between a button press and a button release for the Function command to consider the action a mouse click. The default delay is 150 milliseconds. Omitting the delay value resets the ClickTime to the default.

31.2.4. ColorLimit

ColorLimit limit

This command is obsolete. See the –color-limit option to fvwm.

31.2.5. ColormapFocus

ColormapFocus FollowsMouse | FollowsFocus

By default, fvwm installs the colormap of the window that the cursor is in. If you use

ColormapFocus FollowsFocus

then the installed colormap is the one for the window that currently has the keyboard focus.

31.2.6. CursorStyle

CursorStyle context [ num | name | None | Tiny | file [ x y ] [ fg bg ]]

Defines a new cursor for the specified context. Note that this command can not control the shapes an applications uses, for example, to indicate that it is busy. The various contexts are:

POSITION (top_left_corner)

used when initially placing windows

TITLE (top_left_arrow)

used in a window title-bar

DEFAULT (top_left_arrow)

used in windows that do not set their cursor

SYS (hand2)

used in one of the title-bar buttons

MOVE (fleur)

used when moving or resizing windows

RESIZE (sizing)

used when moving or resizing windows

WAIT (watch)

used during certain fvwm commands (see BusyCursor for details)

MENU (top_left_arrow)

used in menus

SELECT (crosshair)

used when the user is required to select a window

DESTROY (pirate)

used for Destroy, Close, and Delete commands

TOP (top_side)

used in the top side-bar of a window

RIGHT (right_side)

used in the right side-bar of a window

BOTTOM (bottom_side)

used in the bottom side-bar of a window

LEFT (left_side)

used in the left side-bar of a window

TOP_LEFT (top_left_corner)

used in the top left corner of a window

TOP_RIGHT (top_right_corner)

used in the top right corner of a window

BOTTOM_LEFT (bottom_left_corner)

used in the bottom left corner of a window

BOTTOM_RIGHT (bottom_right_corner)

used in the bottom right corner of a window

TOP_EDGE (top_side)

used at the top edge of the screen

RIGHT_EDGE (right_side)

used at the right edge of the screen

BOTTOM_EDGE (bottom_side)

used at the bottom edge of the screen

LEFT_EDGE (left_side)

used at the left edge of the screen

ROOT (left_ptr)

used as the root cursor

STROKE (plus)

used during a StrokeFunc command.

The defaults are shown in parentheses above. If you ever want to restore the default cursor for a specific context you can omit the second argument.

The second argument is either the numeric value of the cursor as defined in the include file X11/cursorfont.h or its name (without the XC_ prefix). Alternatively, the xpm file name may be specified. The name can also be None (no cursor) or Tiny (a single pixel as the cursor).

# make the kill cursor be XC_gumby (both forms work):

CursorStyle DESTROY 56

CursorStyle DESTROY gumby

Alternatively, the cursor can be loaded from an (XPM, PNG or SVG) image file. If fvwm is compiled with Xcursor support, full ARGB is used, and (possibly animated) cursor files made with the xcursorgen program can be loaded. Otherwise the cursor is converted to monochrome.

The optional x and y arguments (following a file argument) specifies the hot-spot coordinate with 0 0 as the top left corner of the image. Coordinates within the image boundary are valid and overrides any hot-spot defined in the (XPM/Xcursor) image file. An invalid or undefined hot-spot is placed in the center of the image.

CursorStyle ROOT cursor_image.png 0 0

The optional fg and bg arguments specify the foreground and background colors for the cursor, defaulting to black and white (reverse video compared to the actual bitmap). These colors are only used with monochrome cursors. Otherwise they are silently ignored.

CursorStyle ROOT nice_arrow.xpm yellow black

31.2.7. DefaultColors

DefaultColors [foreground] [background]

DefaultColors sets the default foreground and background colors used in miscellaneous windows created by fvwm, for example in the geometry feedback windows during a move or resize operation. If you do not want to change one color or the other, use – as its color name. To revert to the built-in default colors omit both color names. Note that the default colors are not used in menus, window titles or icon titles.

31.2.8. DefaultColorset

DefaultColorset [num]

DefaultColorset sets the colorset used by the windows controlled by the DefaultColors command. To revert back to the DefaultColors colors use

DefaultColorset -1

or any variant of the DefaultColors command.

31.2.9. DefaultFont

DefaultFont [fontname]

DefaultFont sets the default font to font fontname. The default font is used by fvwm whenever no other font has been specified. To reset the default font to the built-in default, omit the argument. The default font is used for menus, window titles, icon titles as well as the geometry feedback windows during a move or resize operation. To override the default font in a specific context, use the Style * Font, Style * IconFont, or MenuStyle commands.

31.2.10. DefaultIcon

DefaultIcon filename

Sets the default icon which is used if a window has neither an client-supplied icon nor an icon supplied via the Icon option of the Style command.

31.2.11. DefaultLayers

DefaultLayers bottom put top

Changes the layers that are used for the StaysOnBottom, StaysPut, StaysOnTop Style options. Initially, the layers 2, 4 and 6 are used.

31.2.12. Deschedule

Deschedule [command_id]

Removes all commands that were scheduled with the id command_id with the Schedule command from the list of commands to be executed unless they were already executed. If the command_id is omitted, the value of the variable $[schedule.last] is used as the id.

31.2.13. Emulate

Emulate Fvwm | Mwm | Win

This command is a catch all for how miscellaneous things are done by fvwm. Right now this command affects where the move/resize feedback window appears and how window placement is aborted. To have more Mwm- or Win-like behavior you can call Emulate with Mwm or Win as its argument. With Mwm resize and move feedback windows are in the center of the screen, instead of the upper left corner. This also affects how manual placement is aborted. See the ManualPlacement description.

31.2.14. EscapeFunc


By default the key sequence Ctrl-Alt-Escape allows for escaping from a Wait pause and from a locked ModuleSynchronous command. The EscapeFunc command used with the Key command allows for configuring this key sequence. An example:

Key Escape A MC –

Key Escape A  S EscapeFunc

replaces the Ctrl-Alt-Escape key sequence with Shift-Escape for aborting a Wait pause and ModuleSynchronous command. EscapeFunc used outside the Key command does nothing.

31.2.15. FakeClick

FakeClick [ command value ]…

This command is mainly intended for debugging fvwm and no guarantees are made that it works for you. FakeClick can simulate mouse button press and release events and pass them to fvwm or the applications. The parameters are a list of commands which consist of pairs of command tokens and integer values, The press and release commands are followed by the appropriate mouse button number and generate a button press or release event on the window below the pointer. The wait commands pauses fvwm for the given number of milliseconds. The modifiers command simulates pressing or releasing modifier keys. The values 1 to 5 are mapped to Mod1 to Mod5 while 6, 7 and 8 are mapped to Shift, Lock and Control. The modifier is set for any further button events. To release a modifier key, use the corresponding negative number. The depth command determines to which window the button events are sent. With a depth of 1, all events go to the root window, regardless of the pointer’s position. With 2, the event is passed to the top level window under the pointer which is usually the frame window. With 3, events go to the client window. Higher numbers go to successive sub windows. Zero (0) goes to the smallest window that contains the pointer. Note that events propagate upward.

FakeClick depth 2 press 1 wait 250 release 1

This simulates a click with button 1 in the parent window (depth 2) with a delay of 250 milliseconds between the press and the release. Note: all command names can be abbreviated with their first letter.

31.2.16. FakeKeypress

FakeKeypress [ command value ]…

This command is mainly intended for debugging fvwm and no guarantees are made that it works for you. FakeKeypress can simulate key press and release events and pass them to fvwm or applications. The parameters are a list of commands which consist of pairs of command tokens and values. The press and release commands are followed by a key name. The key name is a standard X11 key name as defined in /usr/include/X11/keysymdef.h, (without the XK_ prefix), or the keysym database /usr/X11R6/lib/X11/XKeysymDB. The wait, modifiers and depth commands are the same as those used by FakeClick.

Save all GVim sessions with: “Esc:w\n”

All (gvim) FakeKeypress press Escape \

                        press colon \

                        press w \

                        press Return

Save & exit all GVim sessions with: “Esc:wq\n”

All (gvim) FakeKeypress press Escape \

                        press colon \

                        press w \

                        press q \

                        press Return

Send A to a specific window:

WindowId 0x3800002 FakeKeypress press A

Note: all command names can be abbreviated with their first letter.

31.2.17. GlobalOpts

GlobalOpts [options]

This command is obsolete. Please replace the global options in your configuration file according to the following table:

版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 举报,一经查实,本站将立刻删除。


【正版授权,激活自己账号】: Jetbrains全家桶Ide使用,1年售后保障,每天仅需1毛

【官方授权 正版激活】: 官方授权 正版激活 支持Jetbrains家族下所有IDE 使用个人JB账号...



  • Jmeter 安装篇

    Jmeter 安装篇Jmeter安装篇Jmeter的安装其实很简单,网上的资料也很多。这里不多说了,直接上步骤。Step1:安装JDK最好安装1.6版本以上的,如果本地安装了JDK那就查看一下是否配置了环境变量。(Jmeter是用java开发的,它的运行依赖于java环境)有关环境变量的配置,请自行百度。网上图文教程还是非常丰富的。Step2:下载Jmeterhttp://jme

  • cisco logging 配置

    cisco logging 配置

  • Elasticsearch:Painless 编程调试「建议收藏」


  • 自监督学习和无监督学习的区别


  • qlineedit输入提示_qlineedit设置不可编辑


  • Latex角标(subscript/superscript)