unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: 68664@debbugs.gnu.org, brownts@troybrown.dev, mardani29@yahoo.es
Subject: bug#68664: 29.1.50; treesit defun commands broken with nested functions
Date: Sun, 28 Jan 2024 09:43:40 +0200	[thread overview]
Message-ID: <86h6ix6gyb.fsf@gnu.org> (raw)
In-Reply-To: <A5C20B7D-8465-4A33-8F33-B96273D6D6B1@gmail.com> (message from Yuan Fu on Sat, 27 Jan 2024 23:29:36 -0800)

> From: Yuan Fu <casouri@gmail.com>
> Date: Sat, 27 Jan 2024 23:29:36 -0800
> Cc: Troy Brown <brownts@troybrown.dev>,
>  68664@debbugs.gnu.org,
>  mardani29@yahoo.es
> 
> >> I feel like I missed something, surely you know they already have interactive args :-)
> > 
> > "C-u" and "C-u 4" are not the same, and can be distinguished by the
> > function's body, right?
> 
> Ah, you’re right. I didn’t know that. If I use (interactive "P”), C-u gives my '(4) and C-u 4 give me 4. That’s what you mean right?

Yes.

> In that case, yeah I think it could be useful for C-u mark-defun to mark the encoding parent rather than next sibling, and C-u beginning-of-defun to go straight to beg of parent.





      reply	other threads:[~2024-01-28  7:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 23:10 bug#68664: 29.1.50; treesit defun commands broken with nested functions Troy Brown
2024-01-23  0:32 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-23 14:30   ` Troy Brown
2024-01-24  6:29     ` Yuan Fu
2024-01-24 14:13       ` Troy Brown
2024-01-24 17:25         ` Troy Brown
2024-01-27  4:26           ` Yuan Fu
2024-01-27  7:32             ` Eli Zaretskii
2024-01-28  4:03               ` Yuan Fu
2024-01-28  6:53                 ` Eli Zaretskii
2024-01-28  7:29                   ` Yuan Fu
2024-01-28  7:43                     ` Eli Zaretskii [this message]

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=86h6ix6gyb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68664@debbugs.gnu.org \
    --cc=brownts@troybrown.dev \
    --cc=casouri@gmail.com \
    --cc=mardani29@yahoo.es \
    /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).