From: Arthur Miller <arthur.miller@live.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Philip Kaludercic <philipk@posteo.net>,
hi@ypei.me, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Adding major or popular language modes to Emacs distribution
Date: Sat, 28 Aug 2021 18:55:00 +0200 [thread overview]
Message-ID: <AM9PR09MB4977C7A6CE29E52416C6697296C99@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <875yvpin00.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 28 Aug 2021 17:53:51 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Out of curiosity, I checked [0] to see what the languages are said to be
>> popular:
>
> Thanks -- interesting list.
>
>> | Language | Status |
>> |----------------------+---------------------------------------|
>> | C | Built-In |
>> | Python | Built-In |
>> | Java | Built-In |
>> | C++ | Built-In |
>> | C# | ELPA |
>
> To clarify -- when I said that C# didn't need to be in Emacs Core, it's
> not because it's not a major language (it is), but it's my opinion that
> it's unlikely that a large number of people would want to use Emacs when
> programming in C#. (Because the IDEs that come bundled with the popular
> C# compilers are what people are using, and it seems unlikely that many
> people would want to switch away from those.)
How popular is .net core on gnu/linux? Do peole write lots of C# stuff for that
runtime in gnu/linux environment?
I am sure though that Lars resoning there holds for VB/VBA/VBScript.
next prev parent reply other threads:[~2021-08-28 16:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 23:04 Adding major or popular language modes to Emacs distribution Yuchen Pei
2021-08-27 23:12 ` Philip Kaludercic
2021-08-27 23:31 ` Yuchen Pei
2021-08-28 2:38 ` Arthur Miller
2021-08-28 6:47 ` Eli Zaretskii
2021-08-28 11:34 ` Qiantan Hong
2021-08-28 11:52 ` Eli Zaretskii
2021-08-28 13:14 ` Stefan Monnier
2021-08-28 13:37 ` Eli Zaretskii
2021-08-28 13:42 ` Dmitry Gutov
2021-08-28 13:49 ` Eli Zaretskii
2021-08-28 14:16 ` Dmitry Gutov
2021-08-28 14:37 ` Eli Zaretskii
2021-08-28 14:46 ` Dmitry Gutov
2021-08-28 15:01 ` Eli Zaretskii
2021-08-28 14:59 ` Lars Ingebrigtsen
2021-08-28 15:03 ` Eli Zaretskii
2021-08-28 6:24 ` Eli Zaretskii
2021-08-28 13:45 ` Philip Kaludercic
2021-08-28 13:56 ` Eli Zaretskii
2021-08-28 14:30 ` Philip Kaludercic
2021-08-28 14:40 ` Eli Zaretskii
2021-08-28 14:45 ` Theodor Thornhill
2021-08-28 14:58 ` Eli Zaretskii
2021-08-28 15:03 ` Arthur Miller
2021-08-28 15:09 ` Eli Zaretskii
2021-08-28 15:32 ` Philip Kaludercic
2021-08-28 15:53 ` Lars Ingebrigtsen
2021-08-28 16:28 ` Theodor Thornhill
2021-08-28 20:40 ` Dmitry Gutov
2021-08-29 2:15 ` Ergus
2021-08-29 6:40 ` Eli Zaretskii
2021-08-28 16:55 ` Arthur Miller [this message]
2021-08-28 17:02 ` Theodor Thornhill
2021-08-28 6:21 ` Eli Zaretskii
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=AM9PR09MB4977C7A6CE29E52416C6697296C99@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hi@ypei.me \
--cc=larsi@gnus.org \
--cc=philipk@posteo.net \
/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).