From: Drew Adams <drew.adams@oracle.com>
To: 35152@debbugs.gnu.org
Subject: bug#35152: 26.1; Value-menu item name "EOl" in `M-x customize-option commment-empty-line'
Date: Thu, 4 Apr 2019 14:58:57 -0700 (PDT) [thread overview]
Message-ID: <66925fdf-0384-4806-8a72-7b478bce6161@default> (raw)
The name should be EOL-terminated, EOL-terminated, or eol-terminated,
but not EOl-terminated.
In GNU Emacs 26.1 (build 1, x86_64-w64-mingw32)
of 2018-05-30
Repository revision: 07f8f9bc5a51f5aa94eb099f3e15fbe0c20ea1ea
Windowing system distributor `Microsoft Corp.', version 10.0.17134
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next reply other threads:[~2019-04-04 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 21:58 Drew Adams [this message]
2019-04-04 22:56 ` bug#35152: 26.1; Value-menu item name "EOl" in `M-x customize-option commment-empty-line' Basil L. Contovounesios
2019-04-05 0:05 ` Drew Adams
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=66925fdf-0384-4806-8a72-7b478bce6161@default \
--to=drew.adams@oracle.com \
--cc=35152@debbugs.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).