From: Eli Zaretskii <eliz@gnu.org>
To: Alex Branham <alex.branham@gmail.com>
Cc: 21074@debbugs.gnu.org, mbork@mbork.pl
Subject: bug#21074: [PATCH] Add docs for two tabulated-list functions
Date: Mon, 21 Jan 2019 18:32:50 +0200 [thread overview]
Message-ID: <83munu9djh.fsf@gnu.org> (raw)
In-Reply-To: <875zuic7mh.fsf@gmail.com> (message from Alex Branham on Mon, 21 Jan 2019 10:12:22 -0600)
> From: Alex Branham <alex.branham@gmail.com>
> Cc: Marcin Borkowski <mbork@mbork.pl>, 21074@debbugs.gnu.org
> Date: Mon, 21 Jan 2019 10:12:22 -0600
>
> I'm not sure there's a great way to decide what needs documentation and
> what doesn't. Glancing through the code in the Emacs tree, these are the
> functions that seem to get used fairly often by modes that derive from
> tabulated-list-mode:
>
> - tabulated-list-delete-entry
> - tabulated-list-get-entry
> - tabulated-list-get-id
> - tabulated-list-header-overlay-p
> - tabulated-list-put-tag
> - tabulated-list-set-col
>
> So perhaps start with those?
Yes, I think so.
> I got the rest of your comments (thanks!) and will incorporate them into
> a follow-up patch once we decide what exactly needs to get documented.
Thanks.
next prev parent reply other threads:[~2019-01-21 16:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 9:05 bug#21074: 25.0.50; Incomplete docs for tabulated-list-mode Marcin Borkowski
2019-01-15 18:19 ` bug#21074: [PATCH] Add docs for two tabulated-list functions Alex Branham
2019-01-15 19:06 ` Eli Zaretskii
2019-01-15 19:41 ` Alex Branham
2019-01-19 8:25 ` Eli Zaretskii
2019-01-21 16:12 ` Alex Branham
2019-01-21 16:32 ` Eli Zaretskii [this message]
2019-01-22 21:03 ` Alex Branham
2019-02-01 9:28 ` Eli Zaretskii
2019-02-02 16:03 ` Alex Branham
2019-02-02 16:33 ` Eli Zaretskii
2019-02-02 17:28 ` Alex Branham
2019-02-02 18:06 ` Eli Zaretskii
2019-02-05 20:08 ` Alex Branham
2019-02-05 20:26 ` Eli Zaretskii
2019-02-05 20:50 ` Alex Branham
2019-02-06 3:32 ` 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=83munu9djh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21074@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=mbork@mbork.pl \
/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).