Re: Renaming non-X x_* procedures in xdisp.c (and elsewhere)

[Eli Zaretskii]

> From: Alex <address@hidden>
> Cc: address@hidden
> Date: Sat, 30 Mar 2019 11:59:08 -0600
> 
> >> Probably not. I was thinking about the rest being terminal hooks,
> >> though. WDYT?
> >
> > Not sure what you mean by "terminal hooks".  They all accept a pointer
> > to a frame, no?
> 
> I meant being used through a function pointer in the terminal struct
> rather than in the redisplay_interface struct.

Are you talking about the arguments these functions receive now?  If
so, which ones specifically get terminal struct pointers?

> >> That would still leave the issue of it making the code
> >> single-backend-only. Though, I guess it's not going anywhere.
> >
> > What do you mean by single-backend-only?  There will be several
> > implementations, one each for every backend.  It's not a catastrophe,
> > and I don't see how to solve it without ugly ifdef's or even more
> > complications.  Doesn't sound justified, as long as no one is working
> > on allowing the same session create frames on different
> > window-systems.
> 
> The same session and different window-system case was what I was
> thinking about, but I agree that it can be put off until someone takes
> up that issue.

OK, so we agree on that.