unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
Cc: 37639@debbugs.gnu.org
Subject: bug#37639: (elisp manual) About description of markers in strunct buffer_text.
Date: Mon, 07 Oct 2019 03:36:02 +0100	[thread overview]
Message-ID: <87eezpnuy5.fsf@tcd.ie> (raw)
In-Reply-To: <CAN7WbiZ-DpkNDmvZxV36YY3XUM68zBVZGQbuB=BDwvP0xumwSw@mail.gmail.com> (Takesi Ayanokoji's message of "Mon, 7 Oct 2019 02:22:56 +0900")

severity 37639 minor
quit

Takesi Ayanokoji <ayanokoji.takesi@gmail.com> writes:

> At @item markers
>   , in @subsection Buffer Internals
>   , in @section Object Internals
>   , in internals.texi
>   , in lispref manual, the manual says,
>
> This is actually a single marker, and successive elements in its marker
> @code{chain} are the other markers referring to this buffer text.
>
> http://git.savannah.gnu.org/cgit/emacs.git/tree/doc/lispref/internals.texi#n2023
>
> But I think @code{chain} should be markup-ed with @dfn, @emph, or quoted with ` and '.

Indeed, @code doesn't seem right here.  I would go with either
``quotes'' or no markup at all, like the 'next' entry further down that
page:

  ‘next’
       A pointer to the next buffer, in the chain of all buffers,
       including killed buffers.  This chain is used only for allocation
       and garbage collection, in order to collect killed buffers
       properly.

> (Or "chain" is some kind of symbol defined in source files? I can't find it.)

No, it's just a metaphor.

Thanks,

-- 
Basil





  reply	other threads:[~2019-10-07  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 17:22 bug#37639: (elisp manual) About description of markers in strunct buffer_text Takesi Ayanokoji
2019-10-07  2:36 ` Basil L. Contovounesios [this message]
2019-10-09  9:30 ` 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=87eezpnuy5.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=37639@debbugs.gnu.org \
    --cc=ayanokoji.takesi@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 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).