unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: acm@muc.de, 20180@debbugs.gnu.org
Subject: bug#20180: Missing documentation about redisplay.
Date: Thu, 02 Dec 2021 23:29:37 -0500	[thread overview]
Message-ID: <E1mt0CX-0003N6-3k@fencepost.gnu.org> (raw)
In-Reply-To: <87h7br5n7z.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu,  02 Dec 2021 11:13:04 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Reading this thread, I think the conclusion here is that the redisplay
  > stuff is just too low-level and finicky to be meaningfully documented in
  > the lispref manual.  You really have to read xdisp.c to start to
  > understand how that works.

I think that's right.  And there's no need to document this there.
The Lisp Ref manual is annoyingly big already.

Maybe we should remove all the internal C-level documentation
from there and put it somewhere else.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







      reply	other threads:[~2021-12-03  4:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 16:08 bug#20180: Missing documentation about redisplay Alan Mackenzie
2015-03-23 16:49 ` Eli Zaretskii
2015-03-23 17:55   ` Alan Mackenzie
2015-03-23 18:29     ` Eli Zaretskii
2015-03-23 20:17       ` Alan Mackenzie
2015-03-23 20:52         ` Eli Zaretskii
2021-12-02 10:13           ` Lars Ingebrigtsen
2021-12-03  4:29             ` Richard Stallman [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

  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=E1mt0CX-0003N6-3k@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=20180@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=larsi@gnus.org \
    /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).