From: scame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "47673@debbugs.gnu.org" <47673@debbugs.gnu.org>
Subject: bug#47673: Absurdly long input field in Customize
Date: Mon, 12 Apr 2021 15:19:01 +0000 [thread overview]
Message-ID: <dGxotj3UTf0MzsV4kEbZJJlG8dfePAFvWZkTVlfO3Mv38Qv3tTDMDPH4T_GdjNs9ztW31IVcjJNOV22U2EelN60ZmwMXerCAQHmJNNtOO0w=@protonmail.com> (raw)
In-Reply-To: <87mtu3yg39.fsf@gnus.org>
>
> > Does this edit buffer need to appear so wide? Can't it be displayed shorter?
>
> It deletes everything up to the end of the line.
>
I checked the code, and from a cursory look the problem seems to be that the :extend property was added to the widget-field face, that's why every field became as wide as the screen, because the newline after the field has this face:
https://github.com/emacs-mirror/emacs/commit/b5781e63cbe7e4c24e4eea3a400880857348ad19
this was done to fix this bug:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37774
and apparently no one noticed this change made all customize fields very long.
next prev parent reply other threads:[~2021-04-12 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 13:20 bug#47673: Absurdly long input field in Customize scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-09 13:46 ` Eli Zaretskii
2021-04-09 13:50 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-09 14:05 ` Eli Zaretskii
2021-04-12 9:02 ` Lars Ingebrigtsen
2021-04-12 9:55 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-12 10:03 ` Lars Ingebrigtsen
2021-04-12 15:19 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-04-12 15:25 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-12 16:24 ` Juri Linkov
2021-04-12 16:53 ` Eli Zaretskii
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='dGxotj3UTf0MzsV4kEbZJJlG8dfePAFvWZkTVlfO3Mv38Qv3tTDMDPH4T_GdjNs9ztW31IVcjJNOV22U2EelN60ZmwMXerCAQHmJNNtOO0w=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=47673@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=laszlomail@protonmail.com \
/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).