From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 15682@debbugs.gnu.org, 52@debbugs.gnu.org
Subject: bug#15682: 24.3.50; `:link' in `defgroup' does not respect `mouse-1-click-follows-link'
Date: Wed, 27 Apr 2016 10:18:09 -0700 (PDT) [thread overview]
Message-ID: <3c72ce34-13d3-4ecd-8731-8408fa1a023a@default> (raw)
In-Reply-To: <87potbgfia.fsf@gnus.org>
> I kinda think it might be time to consider doing a rewrite from scratch
> using modern Emacs features, and then things like this bug report would
> start working automatically.
>
> How big a task would this be? I mean, of course we'd keep compatibility
> (the defcustom language is fine), but just rewrite the UI `M-x
> customize' bits... Hm...
I can't speak to this, sorry. I'll just mention that I think:
(1) it could be a large undertaking and (2) there is existing
code out there that depends on or enhances cus*.el and wid*.el
code.
Personally, I would prefer that we live with it, and try to
improve it incrementally, rather than opting for a rewrite or
replacement. I'd like to see a resident Emacs expert on wid*
and cus*, rather than someone who doesn't master it just trying
for a replacement.
(Yes, I'm conservative wrt this stuff. Emacs is one of the
few things I'm conservative about. ;-))
next prev parent reply other threads:[~2016-04-27 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 15:28 bug#15682: 24.3.50; `:link' in `defgroup' does not respect `mouse-1-click-follows-link' Drew Adams
2016-04-27 16:09 ` bug#52: " Lars Ingebrigtsen
2016-04-27 16:24 ` Drew Adams
2016-04-27 16:53 ` bug#52: " Lars Ingebrigtsen
2016-04-27 17:18 ` Drew Adams [this message]
2019-08-23 20:41 ` Mauro Aranda
2019-08-25 5:47 ` Lars Ingebrigtsen
2019-08-25 15:07 ` Mauro Aranda
2019-08-25 16:19 ` Drew Adams
2019-08-25 16:22 ` Drew Adams
2019-08-25 16:41 ` Eli Zaretskii
2019-08-25 16:50 ` Noam Postavsky
2019-08-25 16:58 ` Mauro Aranda
2019-08-27 6:42 ` Lars Ingebrigtsen
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=3c72ce34-13d3-4ecd-8731-8408fa1a023a@default \
--to=drew.adams@oracle.com \
--cc=15682@debbugs.gnu.org \
--cc=52@debbugs.gnu.org \
--cc=larsi@gnus.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.