[slim-vim] appending confusion and input-listener problems

[Larry Clapp]

[ Top posting corrected ]

On Thu, Jun 01, 2006 at 10:43:01PM -0700, Brad Beveridge wrote:
> On 6/1/06, Brad Beveridge <brad.beveridge at gmail.com> wrote:
> > On 6/1/06, Larry Clapp <larry at theclapp.org> wrote:
> > > On Wed, May 31, 2006 at 01:45:09PM -0700, Brad Beveridge wrote:
> > > > > I will try and get around to this at some point, but as
> > > > > always I can't say when as I am still travelling at the
> > > > > moment (and will be for the next 6 months) and don't have
> > > > > much time or internet access.
> > > > >
> > > > > So sorry that this is still a problem, hopefully at least
> > > > > one of the supported guis is available on most platforms,
> > > > > for the time being the gui is a requirement.
> > > >
> > > > Just to be clear here, you think that if I build the GUI
> > > > version of Vim, I will no longer get the strange crashes when
> > > > listening asyncronously to a socket and piping output to a
> > > > buffer?  If so, guess I'd better figure out how to build a GUI
> > > > Vim :)
> > >
> > > ./configure --with-x --enable-eclinterp
> > >
> > > should cover it.  :)
> > >
> > > ... though maybe not -- you've got an Intel Mac, right?  You're on
> > > your own.  :)
> > >
> > I've built both Carbon and X11 Vim builds, and it appears that the
> > vim listener isn't called back at all.  Am I doing something
> > wrong?  The same source compiled as just a console app does
> > callback the listener.  Strange.  Any thoughts?
> >
> Actually, now that I look at it, the network_io.c code looks like it
> might only support console, motif and GTK - is this correct?

Hmm -- I do, in fact, use "--enable-gui=gtk2".  Here's my complete
configure line:

export CFLAGS="-I/usr/local/lib/ecl/ecl"
./configure --prefix=/usr --with-x --enable-gui=gtk2 --enable-eclinterp

Hope that helps.

-- L