From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Byte compilation warnings in cc-mode.el
Date: Sun, 16 Feb 2020 12:29:52 +0000 [thread overview]
Message-ID: <20200216122952.GA29449@ACM> (raw)
In-Reply-To: <834kvtpjbx.fsf@gnu.org>
Hello, Eli.
On Fri, Feb 14, 2020 at 12:13:54 +0200, Eli Zaretskii wrote:
> On the master branch:
> ELC progmodes/cc-mode.elc
> In c-init-language-vars-for:
> progmodes/cc-mode.el:205:13: Warning: `c-last-open-c-comment-start-on-line-re'
> is an obsolete variable (as of 5.35); use
> `c-open-c-comment-on-logical-line-re' instead.
> progmodes/cc-mode.el:199:20: Warning: `c-last-open-c-comment-start-on-line-re'
> is an obsolete variable (as of 5.35); use
> `c-open-c-comment-on-logical-line-re' instead.
> progmodes/cc-mode.el:200:20: Warning: `c-last-open-c-comment-start-on-line-re'
> is an obsolete variable (as of 5.35); use
> `c-open-c-comment-on-logical-line-re' instead.
> progmodes/cc-mode.el:201:20: Warning: `c-last-open-c-comment-start-on-line-re'
> is an obsolete variable (as of 5.35); use
> `c-open-c-comment-on-logical-line-re' instead.
> progmodes/cc-mode.el:202:20: Warning: `c-last-open-c-comment-start-on-line-re'
> is an obsolete variable (as of 5.35); use
> `c-open-c-comment-on-logical-line-re' instead.
> progmodes/cc-mode.el:203:20: Warning: `c-last-open-c-comment-start-on-line-re'
> is an obsolete variable (as of 5.35); use
> `c-open-c-comment-on-logical-line-re' instead.
> progmodes/cc-mode.el:204:20: Warning: `c-last-open-c-comment-start-on-line-re'
> is an obsolete variable (as of 5.35); use
> `c-open-c-comment-on-logical-line-re' instead.
Yes. This wasn't a good idea. I've completely removed the variables
causing the trouble, committing to the emacs-27 branch (fixing a
bug-fix).
Funnily enough, compiling from the command line didn't produce these
warnings.
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2020-02-16 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 10:13 Byte compilation warnings in cc-mode.el Eli Zaretskii
2020-02-16 12:29 ` Alan Mackenzie [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=20200216122952.GA29449@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).