From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 68664@debbugs.gnu.org, Troy Brown <brownts@troybrown.dev>,
mardani29@yahoo.es
Subject: bug#68664: 29.1.50; treesit defun commands broken with nested functions
Date: Sat, 27 Jan 2024 23:29:36 -0800 [thread overview]
Message-ID: <A5C20B7D-8465-4A33-8F33-B96273D6D6B1@gmail.com> (raw)
In-Reply-To: <86r0i254p9.fsf@gnu.org>
> On Jan 27, 2024, at 10:53 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sat, 27 Jan 2024 20:03:30 -0800
>> Cc: Troy Brown <brownts@troybrown.dev>,
>> 68664@debbugs.gnu.org,
>> mardani29@yahoo.es
>>
>>> Maybe we could support both behaviors via specially-valued prefix
>>> arguments? Like "C-u" means something, "C-u C-u" means something
>>> else, etc.?
>>
>> Beginning/end-of-defun already take a numerical interactive arg, unless I missed something we can’t add another. If we want to change behavior interactively we would need something more elaborate, maybe transient maps.
>>
>>>
>>>> As for mark-defun, I think it’s similarly equally valid to either mark the next sibling or the parent. Right now mark-defun doesn’t really have a notion of nested defun, we should upgrade it to support nested defun like we did beginning/end-of-defun, either by a toggle like mark-defun-tactic or let user control which defun to mark interactively.
>>>
>>> Same here.
>>>
>>> WDYT?
>>
>> Same for mark-defun, it also has an interactive arg already.
>>
>> 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?
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.
Yuan
next prev parent reply other threads:[~2024-01-28 7:29 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 [this message]
2024-01-28 7:43 ` 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=A5C20B7D-8465-4A33-8F33-B96273D6D6B1@gmail.com \
--to=casouri@gmail.com \
--cc=68664@debbugs.gnu.org \
--cc=brownts@troybrown.dev \
--cc=eliz@gnu.org \
--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).