From: Tino Calancha <tino.calancha@gmail.com>
To: 31466@debbugs.gnu.org
Subject: bug#31466: 27.0.50; customize-apropos: Separate package name from its description
Date: Wed, 16 May 2018 12:51:01 +0900 [thread overview]
Message-ID: <87r2mc2r8a.fsf@gmail.com> (raw)
emacs -Q -l dired-x
M-x customize-apropos dired-x RET
;; Last line of the buffer is:
Dired XExtended directory editing (dired-x).
;; It reads better if the package name is separated from
;; the package description. For instance:
Dired X: Extended directory editing (dired-x).
;; Following patch shows the line as:
Dired X:Extended directory editing (dired-x).
;; Without the extra space because looks a bit ugly in the link.
;; If someone knows a way to add the extra space out of the link,
;; that would be better.
--8<-----------------------------cut here---------------start------------->8---
commit 2edea58d78914063bb56270774b5e02d8a1a55af
Author: Tino Calancha <tino.calancha@gmail.com>
Date: Wed May 16 12:46:09 2018 +0900
customize-apropos: Separate package name from its description
* lisp/cus-edit.el (custom-buffer-create-internal): Separate
package name from its description with a colon.
diff --git a/lisp/cus-edit.el b/lisp/cus-edit.el
index a12897e799..0a596ab331 100644
--- a/lisp/cus-edit.el
+++ b/lisp/cus-edit.el
@@ -1711,8 +1711,10 @@ custom-buffer-create-internal
(message "Creating customization items ...%2d%%"
(floor (* 100.0 count) length))
(widget-create (nth 1 entry)
- :tag (custom-unlispify-tag-name
- (nth 0 entry))
+ :tag (format "%s%s"
+ (custom-unlispify-tag-name
+ (nth 0 entry))
+ (if (eq (nth 1 entry) 'custom-group) ":" ""))
:value (nth 0 entry))
(setq count (1+ count))
(unless (eq (preceding-char) ?\n)
--8<-----------------------------cut here---------------end--------------->8---
next reply other threads:[~2018-05-16 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 3:51 Tino Calancha [this message]
2018-05-16 15:58 ` bug#31466: 27.0.50; customize-apropos: Separate package name from its description Eli Zaretskii
2018-05-17 2:57 ` Tino Calancha
2018-06-07 4:54 ` Tino Calancha
2018-06-15 7:23 ` Tino Calancha
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=87r2mc2r8a.fsf@gmail.com \
--to=tino.calancha@gmail.com \
--cc=31466@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 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.