Re: Spending time on Guile Emacs?

[Tobias Gerdin]

2016-12-02 8:20 GMT+01:00 Eli Zaretskii <address@hidden>:

> From: Tobias Gerdin <address@hidden>
> Date: Thu, 1 Dec 2016 21:48:05 +0100
>
> In addition there is the text properties support. Unless one unifies the two representations (perhaps via a compile-time flag if Emacs will be statically linked with Guile) I think the challenge is to make it easy and not too expensive to convert between them.

Why would Guile want to know about text properties?  What would it do
with them?

 

If one would like to be able to use the standard Scheme string manipulation procedures I believe Guile would need to know about the text properties since they should be preserved. One option would be to have special implementations of these when called from Emacs, or just provide some other Emacs-only string library alltogether.
 

AFAIU, Guile should receive only the text part of the Emacs strings,
with or without encoding conversion (probably with, because there are
some quirks in Emacs internal representation of text that Guile
neither can nor should care about).  

Right, keeping string Unicode-only makes a lot of sense for Guile in general.

As for statically linking Emacs with Guile, I'm not sure it's a good
idea, as Guile is a very large library.

Dynamically linked would be best of course, provided one could work out the other issues without resorting to any compile-time configuration.