From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: larsi@gnus.org, 30692@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#30692: list-buffers has hardwired 80 character width from the 80's
Date: Sat, 08 Aug 2020 13:23:38 +0300 [thread overview]
Message-ID: <83wo295tcl.fsf@gnu.org> (raw)
In-Reply-To: <87pn81xx5q.fsf@tcd.ie> (contovob@tcd.ie)
> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Cc: Eli Zaretskii <eliz@gnu.org>, 30692@debbugs.gnu.org, jidanni@jidanni.org
> Date: Sat, 08 Aug 2020 11:13:53 +0100
>
> > which requires a rebuild of loaddefs.el to get rid of the
> > compilation warning. Is there anything a check-in can do to trigger a
> > rebuild of that file automatically?
>
> Like send an automated email to Glenn? :)
I think you had ldefs-boot.el in mind.
next prev parent reply other threads:[~2020-08-08 10:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 23:12 bug#30692: list-buffers has hardwired 80 character width from the 80's 積丹尼 Dan Jacobson
2018-03-04 3:40 ` Eli Zaretskii
2018-03-05 0:23 ` 積丹尼 Dan Jacobson
2018-03-05 3:35 ` Eli Zaretskii
2018-04-14 19:23 ` Lars Ingebrigtsen
2018-04-15 10:35 ` 積丹尼 Dan Jacobson
2018-04-15 12:43 ` Lars Ingebrigtsen
2020-08-07 9:03 ` Lars Ingebrigtsen
2020-08-07 9:08 ` Robert Pluim
2020-08-07 11:44 ` Eli Zaretskii
2020-08-07 11:51 ` Lars Ingebrigtsen
2020-08-07 12:09 ` Eli Zaretskii
2020-08-07 12:19 ` Lars Ingebrigtsen
2020-08-07 13:54 ` Eli Zaretskii
2020-08-08 9:39 ` Lars Ingebrigtsen
2020-08-08 9:50 ` Eli Zaretskii
2020-08-08 10:13 ` Basil L. Contovounesios
2020-08-08 10:23 ` Eli Zaretskii [this message]
2020-08-08 10:28 ` Lars Ingebrigtsen
2020-08-08 10:41 ` Eli Zaretskii
2020-08-08 10:59 ` Lars Ingebrigtsen
2020-08-08 10:30 ` Lars Ingebrigtsen
2020-08-08 10:37 ` Basil L. Contovounesios
2020-08-08 11:02 ` Lars Ingebrigtsen
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=83wo295tcl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30692@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=jidanni@jidanni.org \
--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 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.