unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: stefankangas@gmail.com, rahuljuliato@gmail.com
Cc: emacs-devel@gnu.org, acorallo@gnu.org, casouri@gmail.com
Subject: Re: [PATCH] feat: add markdown-ts-mode
Date: Thu, 04 Jul 2024 09:23:35 +0300	[thread overview]
Message-ID: <86a5ixad5k.fsf@gnu.org> (raw)
In-Reply-To: <86o77dag6z.fsf@gnu.org> (message from Eli Zaretskii on Thu, 04 Jul 2024 08:17:56 +0300)

> Date: Thu, 04 Jul 2024 08:17:56 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: rahuljuliato@gmail.com, emacs-devel@gnu.org, acorallo@gnu.org,
>  casouri@gmail.com
> 
> I'm not sure this is important enough to make exception of the rule
> that no new features are installed on the release branch.
> 
> Moreover, given the proliferation of Markdown style in contexts other
> than just *.md files, I think we should have Markdown support in other
> places, such as email modes and in what looks like plain text files.
> We need some reliable auto-detection of Markdown markup that turns on
> this mode, or maybe a markdown-minor-mode.  It is also possible that
> Text mode should support some of the more popular Markdown styles
> (like quoting `like this`) OOTB.
> 
> IOW, I think we should do more work here than just add a mode for
> editing *.md files, and that will take some time and discussions to
> figure out and integrate.

To clarify: the above doesn't mean we need to wait with installing the
mode as it was submitted (with the few minor nits that need to be
fixed).  It just means that good integration with Emacs will take
time and more work, and therefore installing this on the emacs-30
release branch is not necessarily urgent.



  reply	other threads:[~2024-07-04  6:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-20  3:23 [PATCH] feat: add markdown-ts-mode Rahul Martim Juliato
2024-04-20  6:44 ` Eli Zaretskii
2024-04-20 17:45   ` Jostein Kjønigsen
2024-04-21  5:50     ` Rahul Martim Juliato
2024-04-22  7:02       ` Philip Kaludercic
2024-04-23  1:20         ` Rahul Martim Juliato
2024-04-27 10:18           ` Philip Kaludercic
2024-06-29  2:09             ` Rahul Martim Juliato
2024-07-03 19:13               ` Rahul Martim Juliato
2024-07-03 20:13                 ` Stefan Kangas
2024-07-04  5:17                   ` Eli Zaretskii
2024-07-04  6:23                     ` Eli Zaretskii [this message]
2024-07-04 13:19                       ` Andrea Corallo
2024-07-26  3:59                         ` Rahul Martim Juliato
2024-07-26 22:51                           ` Stefan Kangas
2024-07-04  5:08                 ` 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=86a5ixad5k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acorallo@gnu.org \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rahuljuliato@gmail.com \
    --cc=stefankangas@gmail.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 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).