From: Gregory Heytings via "Emacs development discussions." <emacs-devel@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Lightweight, C-only implementation of Emacs
Date: Mon, 3 Aug 2020 23:55:09 +0200 (CEST) [thread overview]
Message-ID: <alpine.NEB.2.21.2008032336490394.3307@sdf.lonestar.org> (raw)
In-Reply-To: <jwvy2mv8ljp.fsf-monnier+emacs@gnu.org>
>
>> *shrug* The author told you not to use it. What don't you understand
>> about the statement?
>
> FWIW, I use it very happily. It might be worthwhile trying to find out
> why he doesn't recommend its use and what he recommends instead. Maybe
> the issue is simply that he lost interest and we should be looking for
> another maintainer.
>
The main (and serious) limitation of Zile is that it has no support for
Unicode. In fact it is in practice limited to ASCII characters. There
should apparently be a "displayable-characters" configuration variable to
use 8-bit character sets, but it is nowhere documented how it should be
set.
Gregory
next prev parent reply other threads:[~2020-08-03 21:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 1:26 Lightweight, C-only implementation of Emacs Jeffrey Walton
2019-08-18 3:16 ` Bob Newell
2019-08-18 3:21 ` Noam Postavsky
2019-08-18 7:48 ` Stefan Monnier
2019-08-19 5:36 ` Ulrich Mueller
2020-08-03 18:38 ` Jeffrey Walton
2020-08-03 19:37 ` Ulrich Mueller
2020-08-03 19:42 ` Jeffrey Walton
2020-08-03 19:56 ` Ulrich Mueller
2020-08-03 19:58 ` Jeffrey Walton
2020-08-03 21:32 ` Stefan Monnier
2020-08-03 21:55 ` Gregory Heytings via Emacs development discussions. [this message]
2020-08-03 21:52 ` Amin Bandali
2020-08-03 22:31 ` Daniele Nicolodi
2020-08-03 23:56 ` Amin Bandali
2020-08-04 1:24 ` Daniele Nicolodi
2020-08-03 21:32 ` andres.ramirez
2020-08-07 8:38 ` Ergus
2019-08-21 22:58 ` chad
2019-09-21 15:01 ` Ergus via Emacs development discussions.
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.21.2008032336490394.3307@sdf.lonestar.org \
--to=emacs-devel@gnu.org \
--cc=ghe@sdf.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.