From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master b02c9bc: Improve documentation of new Xref options
Date: Tue, 7 Sep 2021 19:06:29 +0300 [thread overview]
Message-ID: <bbdccf10-16f4-55d4-a822-9fd0a1dc336d@yandex.ru> (raw)
In-Reply-To: <83a6kopeye.fsf@gnu.org>
On 07.09.2021 18:45, Eli Zaretskii wrote:
>> From: Dmitry Gutov <dgutov@yandex.ru>
>> Date: Tue, 7 Sep 2021 18:21:24 +0300
>>
>>> @findex project-search
>>> - @kbd{M-x project-search} is an interactive variant of
>>> + @kbd{M-x project-search} is an incremental variant of
>>
>> Is it really incremental? Maybe call it "iterative".
>
> Is "sequential" better? "Iterative" sounds too "mathematical".
Yes, I think it's a fine choice.
>>> -@c Sadly, the new-and-improved Xref feature doesn't provide anything
>>> -@c close to the described below features of the now-obsoleted
>>> -@c tags-apropos. I'm leaving this here to encourage enhancements to
>>> -@c xref.el.
>>> +@c Sadly, the new-and-improved Xref feature doesn't provide some
>>> +@c of the features of the now-obsoleted tags-apropos. I'm leaving
>>> +@c this here to encourage enhancements to xref.el.
>>
>> Is that about the display of tag file names in the apropos output buffer?
>
> No, it's about the features listed after the shown hunk. I just made
> its language less extreme, because xref-find-apropos does exist.
tags-apropos-additional-actions, then? That seems easier to support.
>>> The new user option 'xref-auto-jump-to-first-definition' controls the
>>> -behavior of 'xref-find-definitions' and related commands: if it's t or
>>> -'show', the first match is automatically displayed; if it's 'move',
>>> -point in the "*xref*" buffer is automatically moved to the first match
>>> -without displaying it.
>>> -The new user option 'xref-auto-jump-to-first-xref' changes the behavior of
>>> -all Xref commands in the same way as 'xref-auto-jump-to-first-definition'
>>> -affects the "find-definitions" commands.
>>> +behavior of 'xref-find-definitions' and related commands, like
>>
>> Maybe "similar" rather than related? The point is that those commands
>> use the same UI (to show, sometimes, very different information), rather
>> than that are united by subject matter.
>
> I went with "variants", okay?
Thanks.
next prev parent reply other threads:[~2021-09-07 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210907130400.31609.90502@vcs0.savannah.gnu.org>
[not found] ` <20210907130401.D074320A10@vcs0.savannah.gnu.org>
2021-09-07 15:21 ` master b02c9bc: Improve documentation of new Xref options Dmitry Gutov
2021-09-07 15:45 ` Eli Zaretskii
2021-09-07 16:06 ` Dmitry Gutov [this message]
2021-09-07 16:23 ` Eli Zaretskii
2021-09-08 0:24 ` Dmitry Gutov
2021-09-08 6:18 ` Eli Zaretskii
2021-09-09 1:22 ` Dmitry Gutov
2021-09-09 6:26 ` Eli Zaretskii
2021-09-10 0:18 ` Dmitry Gutov
2021-09-10 12:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bbdccf10-16f4-55d4-a822-9fd0a1dc336d@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.