From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gran <spk121@yahoo.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Editing Scheme in the installation image
Date: Sat, 07 Jan 2017 12:54:26 +0100 [thread overview]
Message-ID: <87pojzf5l9.fsf@gnu.org> (raw)
In-Reply-To: <675307112.1056847.1483710598047@mail.yahoo.com> (Mike Gran's message of "Fri, 6 Jan 2017 13:49:58 +0000 (UTC)")
Hi Mike!
Mike Gran <spk121@yahoo.com> skribis:
> Could work, but, there are caveats.
> This Zile fork, and upstream Zile, have characters restricted to 8-bits
> in most places. It also will not do any bi-directional characters
> or double-width characters. For non-ASCII config files, Zile-on-Guile
> might be too limited.
Sure, but these are restrictions acceptable in this context (it’s just
about editing the GuixSD config file in the installation image.)
> The functions expressed in Scheme in Zile-on-Guile are the same
> as upstream Zile had. It is a fairly limited set.
> Zile-on-Guile is a Scheme, not an elisp, even though the functions
> it expresses have elisp-like names. So there is little portability
> between Emacs and this Zile.
Yes. Any idea how hard it would be to port the real Paredit to
Zile-on-Guile?
Also, would it be possible to do highlighting à la ‘show-paren-mode’?
> But, for me, putting together Zile-on-Guile was a fun project. It would
> be cool to see it used for something. I guess if somebody were
> actually going to use it, it would need a better home than my GitHub.
> I could probably help out, as time permits.
If that works, we could get in touch with the Zile folks to discuss
merging it (Guile extension would be an optional feature).
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2017-01-07 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 23:05 Editing Scheme in the installation image Ludovic Courtès
2017-01-06 1:54 ` Kei Kebreau
2017-01-06 9:09 ` Ricardo Wurmus
2017-01-06 13:49 ` Mike Gran
2017-01-07 11:54 ` Ludovic Courtès [this message]
2017-01-07 22:44 ` Maxim Cournoyer
2017-01-08 10:48 ` Ludovic Courtès
2017-01-08 18:43 ` Mike Gran
2017-01-08 22:43 ` Ludovic Courtès
2017-01-09 1:27 ` Christopher Allan Webber
2017-01-09 9:10 ` Ludovic Courtès
2017-01-07 16:00 ` Christopher Allan Webber
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pojzf5l9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=spk121@yahoo.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/guix.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).