unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: kixtart-mode
Date: Mon, 12 Dec 2022 14:14:57 +0200	[thread overview]
Message-ID: <83pmcostry.fsf@gnu.org> (raw)
In-Reply-To: <E1p4VpC-0000bR-UF@fencepost.gnu.org> (message from Richard Stallman on Sun, 11 Dec 2022 18:33:38 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Sun, 11 Dec 2022 18:33:38 -0500
> 
> If we want to provide better support in Emacs for some nonfree Windows
> scripting language, for the same of encouraging use of Emacs on the widely
> used system Windows, which Windows scripting language should it be?

I don't know.  I don't use scripting much, neither on Windows nor
anywhere else.



  reply	other threads:[~2022-12-12 12:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 20:55 [ELPA] New package: kixtart-mode morgan
2022-11-09 21:10 ` Philip Kaludercic
2022-11-09 21:24   ` Morgan Willcock
2022-11-09 22:04 ` Stefan Monnier
2022-11-09 22:48   ` Morgan Willcock
2022-11-09 23:58     ` Stefan Monnier
2022-11-10  0:20       ` Morgan Willcock
2022-11-10  0:40         ` Juanma Barranquero
2022-11-13  4:18       ` Richard Stallman
2022-11-13  7:09         ` Eli Zaretskii
2022-12-11 23:33           ` Richard Stallman
2022-12-12 12:14             ` Eli Zaretskii [this message]
2022-12-11 23:50           ` Óscar Fuentes
2022-12-12  6:17             ` North Year
2022-12-12 12:21             ` Eli Zaretskii
2022-12-12 14:00               ` Óscar Fuentes
2022-12-20 23:59                 ` Morgan Willcock
2022-11-10  8:16   ` Akib Azmain Turja
2022-11-10  8:25     ` Eli Zaretskii
2022-11-10  9:00       ` Akib Azmain Turja

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=83pmcostry.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.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).