Cygwin X11R7.4 更新支持
我刚刚被 Cygwin X11R7.4 更新所困扰 我发现官方邮件列表充满敌意且笨拙。 所以我想我会在这里问。
如果您在升级中幸存下来（或者至少在修复问题上取得了进展），您采取了哪些步骤来使事情正常进行？
I just got burned by the Cygwin X11R7.4 update and I find the official mailing lists hostile and clunky. So I thought I'd ask here.
If you have survived the upgrade (or at least made progress on fixing things), what steps did you take to make things work?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
此升级将 X Window 系统的各个部分拆分为单独的包。 例如，如果您需要字体，则需要在运行 Cygwin 安装程序时安装这些字体。 对于您需要哪些空间，没有简单的答案，但除了所使用的空间之外，没有理由不获得超出您需要的空间。 我添加了所有看似有用的东西。
如果您使用
startx脚本执行过任何操作，我很遗憾地告诉您，您将不得不重做该工作。 请注意，这对那些遵循该脚本顶部建议的人来说是不利的：“强烈敦促站点管理员编写更好的版本。” （是的，我应该使用源代码控制，是的，我不应该盲目升级 Cygwin，但谁会想到安装过程会从一个版本到下一个版本发生巨大的变化。为什么安装不能保存一份副本我？）对我来说，Windows“开始”菜单中的快捷方式比从命令行运行
startx效果更好，因为默认配置更接近我过去使用的配置。 请注意，startxwin.bat假设您已将 Cygwin 安装在\cygwin中，这可能正确，也可能不正确。 首先检查快捷方式是否闪烁控制台窗口并悄然失败。更新：我现在决定
startxwin.sh是我最喜欢的启动脚本版本。 我使用-multiwindow启动 X，并且仅启动一个xterm。 与startxwin.bat不同，它不会对 Cygwin 的安装位置做出任何潜在错误的假设，因此不需要在每次升级时进行编辑。最初，数字锁键被搞砸了，但当我再次更新时，似乎已经解决了。
This upgrade splits bits of the X Window System into separate packages. For instance, if you need fonts, you'll need to install those when you run the Cygwin setup program. There's no easy answer for which ones you'll need, but beyond the space used, there's no reason not to get more than you need. I added everything that seemed even remotely useful.
If you've done anything with the
startxscript, I'm sorry to say you'll have to redo that work. Note that this bites people who followed the advice at the top of that script: "Site administrators are STRONGLY urged to write nicer versions." (Yes, I should have used source control and yes, I should not blindly upgrade Cygwin, but who would have thought the install process would be dramatically altered from one release to the next. And why couldn't the install save off a copy for me?)For me, the shortcut in the Windows Start menu worked better than running
startxfrom a command line because the default configuration is much closer to what I used in the past. Note thatstartxwin.batassumes you've installed Cygwin in\cygwin, which may or may not be correct. Check that first if the shortcut flashes a console window and quietly fails.Update: I've now decided that
startxwin.shis the version of the startup script I like best. I starts X with the-multiwindowand only launches onexterm. Unlikestartxwin.bat, it does not make any potentially erroneous assumptions about where Cygwin has been installed so it doesn't need to be edited each time it's upgraded.Initially, the number lock key was screwed up, but it seems to have been resolved when I did a another update.
在某些时候，startx 的默认设置已从无根/多窗口更改为 Cygwin 多年前使用的单窗口选项。
哎呀！ 我认为这与更新世界以使用 X.org 的东西而不是旧的 XFree86/X11 或其他任何东西有关。 不管是什么原因，这都是令人难以置信的烦人！ 我想从某人的角度来看，这是“正确的”，有一天我可能会喜欢它。 我想我已经喜欢我在调查时所看到的一些内容：联机帮助页正在更新，并且看起来相当清晰。
暂时我仍然想运行startx。 我不想运行 .bat 脚本，我不想运行自定义脚本。
startx 通过 xinitrc 包中描述的过程启动 X。 根据这个过程，您可以在主目录中创建一个 .xserverrc 文件来控制启动的服务器进程，包括其命令行参数。 （显然，您也可以在 startx 命令行上指定。）正确的做法似乎是将以下内容放入 $HOME/.xserverrc 中：
您可能仍然希望创建一个 .xinitrc 来控制在其中启动的内容你的会议。 我不喜欢 xterm 成为长时间运行的进程，这会导致 X 会话在我退出时终止，但目前我不记得我做了什么来纠正这种情况，并且没有任何示例看看这里。
At some point, the default for startx has changed from rootless/multiwindow to the single-window option that Cygwin used years ago.
Yuck! I presume this was related to updating the world to use X.org stuff instead of the old XFree86/X11, or whatever it was. Whatever the reason, it's mind-bogglingly annoying! I suppose in someone's point of view, it's "right," and I may like it some day. I think I already like some of what I'm seeing as I investigate this: manpages are being updated, and seem fairly clear.
I still want to run startx, for the time being. I don't want to run a .bat script, I don't want to run a custom script.
startx starts up X by means of the process described in the xinitrc package. According to this process, you can create a .xserverrc file in your home directory to control the server process that is started up, including its command-line arguments. (You can also specify on the startx command-line, apparently.) The correct thing to do seems to be to put the following in $HOME/.xserverrc :
You still probably want to create a .xinitrc to control what gets start up within your session. I don't like the way one xterm becomes the long-running process which causes the X session to terminate when I exit, but at the moment I can't remember what I do to correct that situation, and don't have any examples to look at here.