From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: jidanni@jidanni.org, 33529@debbugs.gnu.org
Subject: bug#33529: customize-changed-options: each item is stuck to the part after it
Date: Sun, 02 Dec 2018 09:12:53 +0200 [thread overview]
Message-ID: <838t18bdvu.fsf@gnu.org> (raw)
In-Reply-To: <0r7egshh2q.fsf@fencepost.gnu.org> (message from Glenn Morris on Sat, 01 Dec 2018 20:07:25 -0500)
> From: Glenn Morris <rgm@gnu.org>
> Cc: jidanni@jidanni.org, 33529@debbugs.gnu.org
> Date: Sat, 01 Dec 2018 20:07:25 -0500
>
> Eli Zaretskii wrote:
>
> >> Display Line Numbers Display line numbers in the buffer.
> >> Less CssLess CSS mode.
> >> Python FlymakeIntegration between Python and Flymake.
> >>
> >> ie, no space between (some) versioned defgroups and their descriptions.
> >
> > I see only the first one, and there are 2 spaces between the group
> > name and its description. I don't see the others, so I wonder why the
> > difference.
>
> Don't you have a line in cus-load:
> (custom-put-if-not 'less-css 'custom-version '"26.1")
I do have this in Emacs 26.1 and 26.1.90, but not in the current
emacs-26 branch I build locally. I also don't have less-css mentioned
in cus-load.el at all in the current emacs-26 branch I've built on
GNU/Linux. Why is that file not 100% reproducible?
When the above is in cus-load, then yes, I do see the spliced strings
for those two groups.
next prev parent reply other threads:[~2018-12-02 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 17:19 bug#33529: customize-changed-options: each item is stuck to the part after it 積丹尼 Dan Jacobson
2018-12-01 9:36 ` Eli Zaretskii
2018-12-01 10:51 ` 積丹尼 Dan Jacobson
2018-12-01 18:46 ` Glenn Morris
2018-12-01 19:04 ` Eli Zaretskii
2018-12-02 1:07 ` Glenn Morris
2018-12-02 7:12 ` Eli Zaretskii [this message]
2018-12-03 19:09 ` Glenn Morris
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=838t18bdvu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33529@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=rgm@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).