From: Eli Zaretskii <eliz@gnu.org>
To: Tobias Gerdin <tgerdin@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Spending time on Guile Emacs?
Date: Fri, 02 Dec 2016 09:20:18 +0200 [thread overview]
Message-ID: <83r35qokzx.fsf@gnu.org> (raw)
In-Reply-To: <96C4AEF9-2D74-47C9-848C-780454CB9DE4@gmail.com> (message from Tobias Gerdin on Thu, 1 Dec 2016 21:48:05 +0100)
> From: Tobias Gerdin <tgerdin@gmail.com>
> 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?
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).
As for statically linking Emacs with Guile, I'm not sure it's a good
idea, as Guile is a very large library.
next prev parent reply other threads:[~2016-12-02 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 20:48 Spending time on Guile Emacs? Tobias Gerdin
2016-12-02 7:20 ` Eli Zaretskii [this message]
2016-12-02 20:56 ` Tobias Gerdin
-- strict thread matches above, loose matches on Subject: below --
2016-11-30 21:58 Preview: portable dumper Tobias Gerdin
2016-11-30 22:22 ` Spending time on Guile Emacs? (was: Preview: portable dumper) John Wiegley
2016-11-30 22:24 ` Spending time on Guile Emacs? Daniel Colascione
2016-11-30 22:38 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r35qokzx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tgerdin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).