Convice讨论 | 贡献2007年12月23日 (日) 14:28的版本

跳转至: 导航, 搜索

FVWM is an extremely customizable window manager, many would say it is pathologically customizable. It is also very extensible, lightweight, and fast. It is not for the non-technical. It is for those who know what they want and want the freedom to implement it. It can be as ugly and functional or as beautiful and full of gee-whiz embellishments as you like. The limits are your imagination and your skill. There are 3rd party projects to provide automatic configuration and themes (fvwm-themes and fvwm-crystal). FVWM itself provides a default configuration file generator, in which certain options can be chosen. The expectation, however, is that you want a configuration of your very own, and you can use these tools and others' configs as a starting point (further explanation).

FVWM是一种高度可配置的窗口管理器,我们甚至可说它是“病态”的可配置。它也是可扩展的,轻量级的,快速的窗口管理器。它不适合非技术人士,只适合于那些知道他们想要什么并希望能自由的实现的那些人。它可以是很丑陋但功能强大,或者是充满了很多奇特的装饰,只要你喜欢。唯一的限制是你的想像力和技巧。有一些第三方项目提供了自动化的配置和主题(fvwm-themes和fvwm-crystal)。FVWM也提供一些配置文件产生器,它给你提供了一些特定的选项。如果你希望创建你自己的配置文件,你可以使用这些工具和别人的配置做为一个起点。 (further explanation).

Ubuntu specifics


从 Apt

FVWM is easily installed into Ubuntu, as there is an fvwm package in the repositories. There are additional packages like fvwm-themes, which is a collection of canned FVWM configurations for those who want something that works right away.



FVWM is an active project. Updates with bug fixes and new features are fairly frequent. Currently, FVWM maintains two states: a stable release (versions 2.4.X) and an unstable release (2.5.X). The unstable branch is the one that will eventually form the new stable set (and hence will evolve to 2.6.X as stable, and 2.7.X as being unstable). Given that the FVWM stable branch is quite old, a lot of the more "established" actions one would expect from a window manager is really only in the unstable branch at the moment. Not that "unstable" really means that it crashes every five minutes; it's just an indication that the branch is subject to development and change. Unless there's a very good reason (unlikely) then the 2.5.X branch is the one that should be used, as many people tailor their configs to use it, and usually give no consideration to FVWM 2.4.X. Prerequisite packages are

FVWM是一个活跃的项目。Bug修正和新功能的升级十分频繁。目前,FVWM维护着两个版本分支:稳定版本(2.4.X)和不稳定版本(2.5.X)。不稳定分支最终会形成稳定版本。(2.6.X将会是下一个稳定版本分支,而2.7.X则是下一个非稳定版本)。FVWM的稳定分支已经很老了,目前,很多作为窗口管理器被期望的并已经完成的功能只有非稳定版本才有。“不稳定”并不意味着它将每五分钟崩溃一次,它只是表明了这个分支是被用于开发和改进的。除非有很好的理由不用它(未必有),2.5.X应该是我们使用的版本,因为很多人用它制作自己的配置,他们通常都不会考虑FVWM 2.4.X。需要预先安装的软件包有:build-essential,xorg-dev,fakeroot (用来制作 .deb包),debhelper (也是用于制作 .deb包). 一些几乎每个人都想要用的软件包有:libpng-dev (让 .png 格式的图片能用于图标) 和 libreadline-dev (它使 FvwmConsole 更好用). 下载tar包,像平常一样解压和configure. 不要简单的就使用make,用make deb-inplace来制作 .deb包, 然后用dpkg 安装.


If you install from apt, then FVWM is already in GDM's list of sessions. If you install from source, you will have to choose "Default X session". You will also have to make a .xsession file. The simplest .xsession file simply contains the line "fvwm". .xsession is simply a shell script that is run when you log in from GDM. If there are any programs that you need to start before fvwm, put them in .xsession before "fvwm". It is also wise to make a .xinitrc that is a symlink to .xsession, so that fvwm starts up when you log in from the console. As an example, your ~/.xsesssion file might look like the following:



# Various other commands here, ensuring that they're backgrounded where necessary
# i.e.:
# foo &

# Start FVWM
exec fvwm

Symlinking the above to ~/.xinitrc can be done as follows:


ln -s ~/.xsession ~/.xinitrc

You can have a menu of most installed applications with Debian's menu system. Install the menu package


sudo apt-get install menu

Then, to your

~/.fvwm/config add



Read /etc/X11/fvwm/menudefs.hook

Now you have access to a menu of installed programs, automatically categorized and updated. You can access this menu with the FVWM commands


Menu /Debian


Popup /Debian


There are reports of FVWM not working well under Xgl. This will be corrected when the users complain loudly enough, or someone submits a patch. FVWM works reasonably well with xcompmgr and the composite extension. If you use xcompmgr: Do not give icons titles:


Style * !IconTitle

Restart FVWM after starting or stopping xcompmgr:


# xcompmgr is finally pretty stable, but occasionally it gets screwy or dies
# FVWM must be restarted after xcompmgr, otherwise edges don't work
DestroyFunc RestartXCompMgr
AddToFunc RestartXCompMgr
+ I PipeRead 'killall xcompmgr && exec xcompmgr -n & ; echo Restart'