From: Eli Zaretskii <eliz@gnu.org>
To: Randy Taylor <dev@rjt.dev>
Cc: yordanm@proton.me, casouri@gmail.com, 63708@debbugs.gnu.org
Subject: bug#63708: 29.0.60; rust-ts-mode not properly handling apostrophe
Date: Mon, 29 May 2023 16:13:15 +0300 [thread overview]
Message-ID: <83leh7gu1g.fsf@gnu.org> (raw)
In-Reply-To: <2f72DkG-al7xrS0OaLtReoi4_HyZXNN0xIyCD8l3NdzTHgOUyyJtrANHSrAKuqzhyR4G9IYymP86mY5ss-GufnoUPc9MVOXCQNXnA2VGyjA=@rjt.dev> (message from Randy Taylor on Mon, 29 May 2023 12:18:38 +0000)
> Date: Mon, 29 May 2023 12:18:38 +0000
> From: Randy Taylor <dev@rjt.dev>
> Cc: yordanm@proton.me, 63708@debbugs.gnu.org, casouri@gmail.com
>
> On Monday, May 29th, 2023 at 08:12, Eli Zaretskii <eliz@gnu.org> wrote:
> > > Date: Mon, 29 May 2023 01:29:31 +0000
> >
> > > From: Randy Taylor dev@rjt.dev
> > > Cc: Eli Zaretskii eliz@gnu.org, 63708@debbugs.gnu.org, casouri@gmail.com
> > >
> > > I won't be committing them (don't have the ability) but Eli likely will.
> > >
> > > If you'd like to go through them all and check, that would be great. However, for non-trivial contributions (i.e. more than 15 lines of code changes across all your contributions I believe) you will need to assign copyright to the FSF, otherwise the changes can't be accepted. Eli can send you the form to fill out if you're interested.
> >
> >
> > It is unfortunate that the patch was posted before asking about such
> > non-trivial submissions, because we are now stuck due to lack of
> > copyright assignment, and the release branch must either wait for the
> > assignment or live with the bug.
> >
> > Йордан, can you think of a way of rewriting the go-ts-mode patch so
> > that it uses fewer than 15 lines?
>
> The go-ts-mode patch can be rewritten in a single line by just updating the syntax table directly like I suggested. Then we should be OK.
Thanks, then please post such a patch.
What about rust-ts-mode?
next prev parent reply other threads:[~2023-05-29 13:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 21:40 bug#63708: 29.0.60; rust-ts-mode not properly handling apostrophe yordanm--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-24 22:05 ` bug#63709: " yordanm--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-25 5:28 ` Eli Zaretskii
2023-05-25 5:31 ` bug#63708: " Eli Zaretskii
2023-05-25 12:52 ` Randy Taylor
2023-05-25 13:13 ` Eli Zaretskii
2023-05-26 2:21 ` Randy Taylor
2023-05-26 19:14 ` yordanm--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-27 3:00 ` Randy Taylor
2023-05-28 19:51 ` yordanm--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-28 19:52 ` yordanm--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-29 11:25 ` Eli Zaretskii
2023-05-29 13:34 ` Randy Taylor
2023-05-29 1:29 ` Randy Taylor
2023-05-29 12:13 ` Eli Zaretskii
2023-05-29 12:18 ` Randy Taylor
2023-05-29 13:13 ` Eli Zaretskii [this message]
2023-05-29 13:20 ` Randy Taylor
2023-05-29 14:13 ` yordanm--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-29 14:27 ` Eli Zaretskii
2023-05-29 14:54 ` Йордан Миладинов
2023-05-29 14:59 ` Eli Zaretskii
2023-05-30 0:14 ` Randy Taylor
2023-05-30 9:44 ` yordanm--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 8:35 ` Eli Zaretskii
2023-05-30 9:10 ` Йордан Миладинов
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=83leh7gu1g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63708@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=dev@rjt.dev \
--cc=yordanm@proton.me \
/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).