On Sat, 2007-03-10 at 13:49 +0100, Tomas Janousek wrote: > Hi, > > On Fri, Mar 09, 2007 at 10:57:57AM -0500, Adam Jackson wrote: > > The one major reason to not want X support in your editor is so you > > don't block on the XOpenDisplay, which can take much longer than you > > want when using ssh with a forwarded display. But I'd assert that the > > right way to fix that is to teach vim about xcb so the open can fail > > asynchronously. > > I want vim to open an X connection over forwarded X. And it does not fail. I want this, when it works. I want vim to have a connection to the X server when it's available, because "*y is awesome. I want it to maybe give me a warning when I forgot to set $DISPLAY before launching ssh -Y, whatever, not a big deal. But most importantly, I don't want to have to wait for vim to connect to the X server, because I _could_ start editing immediately, instead of waiting for five seconds of round-trips. Hence, XCB. vim should try to do an asynchronous connect. - ajax -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
