From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: problems with Emacs 28
Date: Fri, 23 Oct 2020 20:33:45 +0300 [thread overview]
Message-ID: <X5MT+ZqcAF87mpcv@protected.rcdrun.com> (raw)
In-Reply-To: <87lffwhop1.fsf@zoho.eu>
* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2020-10-23 20:08]:
> I rebuilt a new Emacs, namely
>
> GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
> 3.24.5, cairo version 1.16.0) of 2020-10-23
>
> because I wanted an Emacs with support for modules (in particular,
> vterm), which isn't possible to get from the Debian repos, IIUC.
>
> Two issues:
>
> 1) suddenly no `markdown-mode'? but there is a markdown-mode pack in
> MELPA, which seems to work OOTB. but as a side not, to move major
> modes out of core Emacs seems like a bad idea, since they are
> Emacs' back bone, and besides cannot amount to many bytes, as they
> are just text. I take it spcific reasons made you do it?
I don't think it was ever in Emacs or in GNU ELPA. I have kindly asked
author of markdown-mode to maybe contribute it to GNU ELPA, no answer
yet, maybe email address is outdated, and there are various other
contributors.
--
Jean Louis
next prev parent reply other threads:[~2020-10-23 17:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 16:50 problems with Emacs 28 Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 17:33 ` Jean Louis [this message]
2020-10-23 18:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 1:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 12:56 ` Stefan Monnier
2020-10-24 12:57 ` Stefan Monnier
2020-10-24 9:46 ` Michael Heerdegen
2020-10-24 17:00 ` Drew Adams
2020-10-24 19:26 ` Michael Heerdegen
2020-10-24 22:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 22:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-25 12:13 ` Michael Heerdegen
2020-10-25 14:15 ` Drew Adams
2020-10-27 0:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-27 10:22 ` Michael Heerdegen
2020-10-28 16:21 ` Jens C. Jensen
2020-10-28 17:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-28 17:18 ` Stefan Monnier
2020-10-31 18:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 13:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:16 ` Eli Zaretskii
2020-10-23 18:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:44 ` Stefan Monnier
2020-10-24 0:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 19:09 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-10-24 0:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=X5MT+ZqcAF87mpcv@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@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.
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).