unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Brian Leung <bkleung89@gmail.com>, Alan Mackenzie <acm@muc.de>
Cc: 41649@debbugs.gnu.org
Subject: bug#41649: 27.0.91; beginning-of-defun doesn't work inside React markup in js-jsx-mode
Date: Wed, 3 Jun 2020 00:45:28 +0300	[thread overview]
Message-ID: <be72f3be-17a1-ce91-d553-01b2744434d5@yandex.ru> (raw)
In-Reply-To: <CAAc=MEwA0Rh_=5qPJWHVAPAv4wPJPSEYJOFK8Z8jatvivzEP+w@mail.gmail.com>

On 02.06.2020 20:27, Brian Leung wrote:
> I wasn't sure if js-beginning-of-defun was preferred here since it does 
> not seem to detect ES2015 arrow functions like what is used here, 
> whereas c-beginning-of-defun handles them fine outside of ReactJS cases: 
> if you try M-: js-beginning-of-defun on my React example, point moves 
> straight from the class declaration to the imports, which is not 
> desirable. Should I file a separate ticket for that?

A separate ticked is probably better.

The fix shouldn't be too hard, but there are a lot of "\\_<function" 
regexps to change or augment in there.





  reply	other threads:[~2020-06-02 21:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 17:59 bug#41649: 27.0.91; beginning-of-defun doesn't work inside React markup in js-jsx-mode Brian Leung
     [not found] ` <mailman.928.1591034465.2541.bug-gnu-emacs@gnu.org>
2020-06-02 17:12   ` Alan Mackenzie
2020-06-02 17:27     ` Brian Leung
2020-06-02 21:45       ` Dmitry Gutov [this message]
2020-06-02 21:43     ` Dmitry Gutov
2020-06-03 19:39       ` Alan Mackenzie
2020-06-03 20:08         ` Dmitry Gutov
2020-06-04 16:23           ` Alan Mackenzie
2020-06-04 16:26             ` Dmitry Gutov
2020-06-04 16:40               ` Brian Leung
2020-06-07 15:23                 ` Alan Mackenzie

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=be72f3be-17a1-ce91-d553-01b2744434d5@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=41649@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=bkleung89@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).