From: Ergus <spacibba@aol.com>
To: "andres.ramirez" <rrandresf@gmail.com>
Cc: Ulrich Mueller <ulm@gentoo.org>,
Jeffrey Walton <noloader@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Lightweight, C-only implementation of Emacs
Date: Fri, 7 Aug 2020 10:38:20 +0200 [thread overview]
Message-ID: <20200807083820.olmsw537tjpewnu5@Ergus> (raw)
In-Reply-To: <86pn87wh3p.fsf@gmail.com>
On Mon, Aug 03, 2020 at 09:32:26PM +0000, andres.ramirez wrote:
>Hi. Ulrich.
>
>>>>>> "Ulrich" == Ulrich Mueller <ulm@gentoo.org> writes:
>
>
> Ulrich> *shrug* It compiles and works, and upstream appears to be responsive. No good reason
> Ulrich> for dropping it from a distro (and breaking existing users' workflows).
>
>
>qemacs could be an alternative. qemacs has basic suppor for org-mode as
>a bonus.
>
>Best Regards
>
Some time ago I came with this same question. After some tests and forks
I found that qemacs was a better alternative compared to Zile for
different reasons:
1) The code was cleaner and simpler to extend, understand and maintain.
2) It does not depend on gnulib or any external tool, which considering
I wanted to port it to cmake was a key plus. (gnulib only supports
autotools)
3) The support for color and syntax highlight was finished and fully
working with extension possibilities.
4) It had all the infrastructure to create extension in C (with dynamic
libraries and an exposed API), like the emacs C-modules.
5) Basic support implemented for some major modes like org-mode, and
others. (this can be extended with modules as mentioned in point 4)
6) gui interface with xlibs and terminal version.
In general I made a request to add some functionalities to Zile and
Qemacs and I never received any answer from any of them so I just made
my personal forks:
https://github.com/Ergus/Zile
https://github.com/Ergus/Qemacs
next prev parent reply other threads:[~2020-08-07 8:38 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.
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 [this message]
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
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=20200807083820.olmsw537tjpewnu5@Ergus \
--to=spacibba@aol.com \
--cc=emacs-devel@gnu.org \
--cc=noloader@gmail.com \
--cc=rrandresf@gmail.com \
--cc=ulm@gentoo.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 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).