From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: casouri@gmail.com, 67262@debbugs.gnu.org, jdtsmith@gmail.com
Subject: bug#67262: python-ts-mode cannot identify triple-quoted-strings
Date: Sat, 16 Dec 2023 17:21:55 +0200 [thread overview]
Message-ID: <b26b9fa7-89dd-d814-2327-e6d78bad92bc@gutov.dev> (raw)
In-Reply-To: <831qbmmen6.fsf@gnu.org>
On 16/12/2023 15:59, Eli Zaretskii wrote:
>> Date: Sat, 16 Dec 2023 15:37:40 +0200
>> Cc:jdtsmith@gmail.com,67262@debbugs.gnu.org
>> From: Dmitry Gutov<dmitry@gutov.dev>
>>
>> On 16/12/2023 14:47, Eli Zaretskii wrote:
>>> How should we make progress with this bug? I'd like to fix it before
>>> Emacs 29.2 is released.
>> We're currently working on the general issue in bug#66732.
> Ok, so please close this bug as well, when that general issue is
> resolved.
>
> And I hope bug#66732 will be solved soon? Because I'm waiting for
> this to be solved for Emacs 29.2. If you think I shouldn't wait,
> please tell.
We have a few more days, right?
next prev parent reply other threads:[~2023-12-16 15:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 15:52 bug#67262: python-ts-mode cannot identify triple-quoted-strings JD Smith
2023-11-18 16:29 ` Eli Zaretskii
2023-11-18 17:18 ` JD Smith
2023-11-18 22:52 ` Dmitry Gutov
2023-11-25 10:01 ` Eli Zaretskii
2023-11-25 14:42 ` JD Smith
2023-11-26 2:04 ` Dmitry Gutov
2023-11-26 14:58 ` Dmitry Gutov
2023-11-26 23:43 ` Yuan Fu
2023-11-27 0:05 ` Dmitry Gutov
2023-12-12 8:32 ` Yuan Fu
2023-12-12 21:55 ` Dmitry Gutov
2023-12-16 12:47 ` Eli Zaretskii
2023-12-16 13:37 ` Dmitry Gutov
2023-12-16 13:59 ` Eli Zaretskii
2023-12-16 15:11 ` JD Smith
2023-12-16 15:21 ` Dmitry Gutov [this message]
2023-12-16 15:57 ` Eli Zaretskii
2023-12-16 23:36 ` Yuan Fu
2023-12-17 13:46 ` Dmitry Gutov
2023-12-23 9:52 ` Eli Zaretskii
2023-12-23 18:03 ` Yuan Fu
2023-12-23 21:01 ` Dmitry Gutov
2023-12-23 23:51 ` Yuan Fu
2023-12-24 0:45 ` Dmitry Gutov
2023-12-24 3:10 ` Yuan Fu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b26b9fa7-89dd-d814-2327-e6d78bad92bc@gutov.dev \
--to=dmitry@gutov.dev \
--cc=67262@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=jdtsmith@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.