From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 35702@debbugs.gnu.org, juri@linkov.net
Subject: bug#35702: xref revert-buffer
Date: Sat, 25 May 2019 10:39:39 +0300 [thread overview]
Message-ID: <83h89j3rus.fsf@gnu.org> (raw)
In-Reply-To: <2103dba2-60ec-9752-1ab8-71ed66fafe63@yandex.ru> (message from Dmitry Gutov on Fri, 24 May 2019 23:51:58 +0300)
> Cc: 35702@debbugs.gnu.org, juri@linkov.net
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 24 May 2019 23:51:58 +0300
>
> >> Just to be clear: I'm referring to two of the three entries I've showed
> >> in the previous email mentioning "search-type Xref commands".
> >
> > Why is that "duplication"? using the same terminology is a Good
> > Thing, as it allows the reader easier understanding what is being
> > discussed.
>
> I was thinking it would be better to coin a common term that separates
> "other" Xref commands from xref-find-definitions, so we don't have to
> enumerate them later.
>
> This distinction is also important, for instance, to make the purposes
> of xref-show-xrefs-function and xref-show-definitions-function clear in
> their docstrings.
I'm fine with coming up with some classification of these commands.
But I think the classification should be in the manual, not in NEWS.
> >> Would a docstring saying "Function that returns a list of xrefs
> >> containing the search results" change things?
> >
> > I meant a comment that would explain how things worked and in what
> > scenarios.
>
> Would you be surprised to hear that I don't even know where to begin?
Yes.
> When doing something for xref.el or project.el, lately I spend quite a
> bit of time thinking how to make the concepts more transparent, and very
> little time implementing them. So I currently feel that the ideas are
> simple (meaning, there are no behaviors that require particular extra
> commentary), and the implementations are maybe too simplistic.
>
> There are much more difficult things in this package, e.g. window
> management.
I didn't mean to imply that the stuff we were discussing is the only
one that is painful to decipher.
Thanks.
next prev parent reply other threads:[~2019-05-25 7:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 19:45 bug#35702: xref revert-buffer Juri Linkov
2019-05-24 1:51 ` Dmitry Gutov
2019-05-24 8:36 ` Eli Zaretskii
2019-05-24 10:09 ` Dmitry Gutov
2019-05-24 12:25 ` Eli Zaretskii
2019-05-24 12:57 ` Dmitry Gutov
2019-05-24 14:10 ` Eli Zaretskii
2019-05-24 14:26 ` Dmitry Gutov
2019-05-24 15:02 ` Eli Zaretskii
2019-05-24 22:35 ` Dmitry Gutov
2019-05-24 15:15 ` Dmitry Gutov
2019-05-24 19:35 ` Eli Zaretskii
2019-05-24 20:51 ` Dmitry Gutov
2019-05-25 7:39 ` Eli Zaretskii [this message]
2019-05-25 15:47 ` Dmitry Gutov
2019-05-25 16:06 ` Eli Zaretskii
2019-05-25 16:14 ` Dmitry Gutov
2019-05-25 16:49 ` Eli Zaretskii
2019-05-25 21:33 ` Dmitry Gutov
2019-05-26 16:44 ` Eli Zaretskii
2019-05-27 14:54 ` Dmitry Gutov
2019-05-27 16:31 ` Eli Zaretskii
2019-05-28 14:10 ` Dmitry Gutov
2019-05-28 18:41 ` 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=83h89j3rus.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35702@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=juri@linkov.net \
/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.