From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 63896@debbugs.gnu.org
Subject: bug#63896: [PATCH] Support annotating and sorting the project list during completion
Date: Mon, 05 Jun 2023 14:23:37 +0300 [thread overview]
Message-ID: <83v8g240g6.fsf@gnu.org> (raw)
In-Reply-To: <ierpm6audpo.fsf@janestreet.com> (message from Spencer Baugh on Sun, 04 Jun 2023 17:20:19 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Sun, 04 Jun 2023 17:20:19 -0400
>
> This patch adds an annotation-function and display-sort-function to the
> completion-table used for project-prompt-project-dir and
> project-prompt-project-name, as well as a user customization variable to
> customize the behavior of the annotation and sorting functions.
Thanks. A few minor comments.
> +(defun project-annotation-numbufs (pr)
> + "Annotate PROJECT with the length of `project-buffers'."
The argument is named PR, not PROJECT.
Also, instead if too-technical "length of `project-buffers'", how
about saying "number of buffers in the project", or "number of buffers
in `project-buffers'"?
> +(defun project-annotation-mtime (pr)
> + "Annotate PROJECT with the modification time of its root directory.
PR, not PROJECT.
> +Note that the modification time will only change when files
> +directly under the root directory are added or deleted. If you
> +only add or delete files in subdirectories, or if you only modify
> +existing files, the modification time won't change."
This is not guaranteed, so I'd suggest to mention that the reliability
of this annotation is questionable, and depends on the underlying
filesystem.
> +(defun project-annotation-compilation (project)
> + "Annotate PROJECT with information from its compilation buffer if any."
I'd add here something about that "information". Right now, this doc
string is not very useful.
> + (cons (+ (* 100 compilation-num-errors-found)
> + (* 10 compilation-num-warnings-found)
Why "encode" these numbers in a single value? why not use a cons or a
vector?
> + (format-mode-line mode-line-process nil nil buf)))
Do you really need to call format-mode-line? My advice is to stay
away of that function: it could have unpleasant side effects.
next prev parent reply other threads:[~2023-06-05 11:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 21:20 bug#63896: [PATCH] Support annotating and sorting the project list during completion Spencer Baugh
2023-06-05 11:23 ` Eli Zaretskii [this message]
2023-06-13 21:19 ` Spencer Baugh
2023-06-14 12:12 ` Eli Zaretskii
2023-06-15 19:04 ` Spencer Baugh
2023-06-16 5:43 ` Eli Zaretskii
2023-06-16 14:26 ` Spencer Baugh
2023-06-16 15:23 ` Eli Zaretskii
2023-06-27 20:30 ` Spencer Baugh
2023-06-28 11:45 ` Eli Zaretskii
2023-08-24 1:54 ` Dmitry Gutov
2023-08-24 5:29 ` Eli Zaretskii
2023-08-24 13:08 ` Dmitry Gutov
2023-08-24 14:39 ` Eli Zaretskii
2023-08-24 1:47 ` Dmitry Gutov
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=83v8g240g6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63896@debbugs.gnu.org \
--cc=sbaugh@janestreet.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 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.