From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39789-done@debbugs.gnu.org, nuclearspace@gmail.com
Subject: bug#39789: eieio Info misspells slot name in eieio-instance-tracker
Date: Wed, 26 Feb 2020 15:48:58 -0500 [thread overview]
Message-ID: <878skpxef9.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <02D80411-CEE8-4028-9695-F24351097980@gnu.org> (Eli Zaretskii's message of "Wed, 26 Feb 2020 18:01:28 +0000")
Eli Zaretskii <eliz@gnu.org> writes:
> On February 26, 2020 5:20:22 PM GMT, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>> akater <nuclearspace@gmail.com> writes:
>>
>> > I'm using Emacs 28 from git master.
>> >
>> > Excerpt from EIEIO entry in Info Directory:
>> >> Sometimes it is useful to keep a master list of all instances of a
>> >> given class. The class ‘eieio-instance-tracker’ performs this
>> task.
>> >
>> >> -- Class: eieio-instance-tracker tracker-symbol
>> >> Enable instance tracking for this class. The slot
>> TRACKER-SYMBOL
>> >> should be initialized in inheritors of this class to a symbol
>> >> created with ‘defvar’. This symbol will serve as the variable
>> used
>> >> as a master list of all objects of the given class.
>> >
>> > At the moment, eieio-instance-tracker is defined in eieio-base with
>> slot
>> > named
>> >
>> >> TRACKING-SYMBOL
>> >
>> > not
>> >
>> >> TRACKER-SYMBOL
>> >
>> > EIEIO entry in Info Directory should thus be patched to refer to
>> slot's
>> > actual name `tracking-symbol'. These are the only two mentions of
>> the
>> > slot in eieio.info.bz2
>>
>> This would be easy enough to fix -- we're doing documentation fixes on
>> the 27 branch, right?
>
> Yes, thanks.
Done, thanks for reporting.
Eric
prev parent reply other threads:[~2020-02-26 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 16:05 bug#39789: eieio Info misspells slot name in eieio-instance-tracker akater
2020-02-26 17:20 ` Eric Abrahamsen
2020-02-26 18:01 ` Eli Zaretskii
2020-02-26 20:48 ` Eric Abrahamsen [this message]
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=878skpxef9.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=39789-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=nuclearspace@gmail.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.