From: Darcy Shen via Guix-patches via <guix-patches@gnu.org>
To: "Zhu Zihao" <all_but_last@163.com>, "55423" <55423@debbugs.gnu.org>
Subject: [bug#55423] What's the motivation of creating Mogan. (was Re: [bug#55423] [PATCH]: gnu: Add mogan.)
Date: Mon, 16 May 2022 18:39:22 +0800 [thread overview]
Message-ID: <180cc737bdf.aea91ada185587.5040783378682960158@zoho.com> (raw)
In-Reply-To: <86tu9qvq2x.fsf@163.com>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
Because GNU TeXmacs is still using GNU Guile 1.8.x and Qt 4.x.
As one of the developers, I want to use S7 Scheme and Qt 5.x. That's the reason why I fork GNU TeXmacs.
---- On Sun, 15 May 2022 22:12:27 +0800 Zhu Zihao <all_but_last@163.com> wrote ----
Hello, Darcy Shen!
We're planning to package mogan editor for Guix. Thanks for your work on
Mogan and GNU TeXmacs!
Please allow me to ask a question here: What's your motivation of
forking GNU TeXmacs to create Mogan?
So Guix developers don't know the difference between GNU TeXmacs and
Mogan and many articles about Mogan were written in Chinese. So we need
your help. Thank you very much.
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: Type: text/html, Size: 1496 bytes --]
next prev parent reply other threads:[~2022-05-16 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 3:21 [bug#55423] [PATCH]: gnu: Add mogan Zhu Zihao
2022-05-15 11:57 ` Maxime Devos
2022-05-15 13:56 ` Zhu Zihao
2022-05-15 11:58 ` Maxime Devos
2022-05-15 14:05 ` Zhu Zihao
2022-05-15 14:24 ` Maxime Devos
2022-05-15 11:59 ` Maxime Devos
2022-05-15 14:12 ` [bug#55423] What's the motivation of creating Mogan. (was Re: [bug#55423] [PATCH]: gnu: Add mogan.) Zhu Zihao
2022-05-16 10:39 ` Darcy Shen via Guix-patches via [this message]
2022-09-05 11:41 ` [bug#55423] [PATCH]: gnu: Add mogan Zhu Zihao
2022-09-22 5:40 ` Zhu Zihao
2022-11-07 11:06 ` bug#55423: " Zhu Zihao
2022-05-15 12:01 ` [bug#55423] " Maxime Devos
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=180cc737bdf.aea91ada185587.5040783378682960158@zoho.com \
--to=guix-patches@gnu.org \
--cc=55423@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=sadhen@zoho.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 external index
https://git.savannah.gnu.org/cgit/guix.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.