unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#37639: (elisp manual) About description of markers in strunct buffer_text.
@ 2019-10-06 17:22 Takesi Ayanokoji
  2019-10-07  2:36 ` Basil L. Contovounesios
  2019-10-09  9:30 ` Eli Zaretskii
  0 siblings, 2 replies; 3+ messages in thread
From: Takesi Ayanokoji @ 2019-10-06 17:22 UTC (permalink / raw)
  To: 37639

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

Hi.

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 '.

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

Thanks.

[-- Attachment #2: Type: text/html, Size: 1375 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#37639: (elisp manual) About description of markers in strunct buffer_text.
  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
  2019-10-09  9:30 ` Eli Zaretskii
  1 sibling, 0 replies; 3+ messages in thread
From: Basil L. Contovounesios @ 2019-10-07  2:36 UTC (permalink / raw)
  To: Takesi Ayanokoji; +Cc: 37639

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





^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#37639: (elisp manual) About description of markers in strunct buffer_text.
  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
@ 2019-10-09  9:30 ` Eli Zaretskii
  1 sibling, 0 replies; 3+ messages in thread
From: Eli Zaretskii @ 2019-10-09  9:30 UTC (permalink / raw)
  To: Takesi Ayanokoji; +Cc: 37639-done

> From: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
> Date: Mon, 7 Oct 2019 02:22:56 +0900
> 
> 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.

Thanks, fixed.





^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-10-09  9:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2019-10-09  9:30 ` Eli Zaretskii

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).