From: Robert Pluim <rpluim@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, gregory@heytings.org
Subject: Re: feature/fix-the-long-lines-display-bug e7b5912b23: Improvements to long lines handling.
Date: Sun, 24 Jul 2022 13:14:21 +0200 [thread overview]
Message-ID: <878roiahki.fsf@gmail.com> (raw)
In-Reply-To: <87mtd0aqea.fsf@tcd.ie> (Basil L. Contovounesios's message of "Sat, 23 Jul 2022 16:51:25 +0300")
>>>>> On Sat, 23 Jul 2022 16:51:25 +0300, "Basil L. Contovounesios" <contovob@tcd.ie> said:
Basil> Eli Zaretskii [2022-07-23 16:20 +0300] wrote:
>>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>>> Cc: Gregory Heytings <gregory@heytings.org>
>>> Date: Sat, 23 Jul 2022 14:40:53 +0300
>>>
>>> This seems to have given rise to the following build error with
>>> --enable-checking=structs:
>>>
>>> pdumper.c: In function ‘dump_buffer’:
>>> pdumper.c:2705:3: error: #error "buffer changed. See CHECK_STRUCTS comment in config.h."
>>> 2705 | # error "buffer changed. See CHECK_STRUCTS comment in config.h."
>>> | ^~~~~
>>>
>>> Is this the right fix?
>>
>> Yes, thanks.
Basil> Thanks, pushed.
Apropos, is there an ʼupdating pdumper stuff for dummiesʼ guide
somewhere? Something along the lines of:
- if you add an int to struct <foo>, do <bar>
- if you add a Lisp_Object to struct <baz>, do <frot>
I ask, because Iʼm playing with struct buffer_text, and Iʼm very
successfully causing 'failure to dump' :-)
Robert
--
next prev parent reply other threads:[~2022-07-24 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165799889678.19490.7919197387382513250@vcs2.savannah.gnu.org>
[not found] ` <20220716191457.3B0FAC00095@vcs2.savannah.gnu.org>
2022-07-23 11:40 ` feature/fix-the-long-lines-display-bug e7b5912b23: Improvements to long lines handling Basil L. Contovounesios
2022-07-23 13:20 ` Eli Zaretskii
2022-07-23 13:51 ` Basil L. Contovounesios
2022-07-24 11:14 ` Robert Pluim [this message]
2022-07-24 11:45 ` Eli Zaretskii
2022-07-24 12:10 ` Robert Pluim
2022-07-25 20:50 ` Gregory Heytings
2022-07-26 11:07 ` Eli Zaretskii
2022-07-26 11:28 ` Gregory Heytings
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=878roiahki.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.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).