unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#14384: mh-e non-standard names for defcustom etc
@ 2013-05-11  1:49 Glenn Morris
  2013-05-13  1:31 ` Bill Wohler
  0 siblings, 1 reply; 2+ messages in thread
From: Glenn Morris @ 2013-05-11  1:49 UTC (permalink / raw)
  To: 14384; +Cc: mh-e-devel

Package: emacs
Version: 24.3

emacs -Q
M-x customize-group RET mh TAB [no match]

Ie, none of the mh customization groups are visible to the customize interface.
This is because you use non-standard macros defgroup-mh, defcustom-mh etc.
Because of this, custom-make-dependencies fails to add any mh-e entries
to cus-load.el.

We can paper over this in the Emacs lisp/Makefile by simply
loading mh-e/mh-e when running custom-make-dependencies.

It would be simpler if mh-e used standard macros though.
Are the -mh versions still needed?
"This macro is used by Emacs versions that lack the :package-version
keyword, introduced in Emacs 22."
Do you still want to support people taking the latest mh-e and running
it on Emacs older than 22.1 (released 2007)?

I see this came up before.
http://sourceforge.net/mailarchive/forum.php?thread_name=19664.1182361165%40juniper.net&forum_name=mh-e-devel





^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#14384: mh-e non-standard names for defcustom etc
  2013-05-11  1:49 bug#14384: mh-e non-standard names for defcustom etc Glenn Morris
@ 2013-05-13  1:31 ` Bill Wohler
  0 siblings, 0 replies; 2+ messages in thread
From: Bill Wohler @ 2013-05-13  1:31 UTC (permalink / raw)
  To: 14384; +Cc: mh-e-devel

Glenn Morris <rgm@gnu.org> writes:

> Package: emacs
> Version: 24.3
>
> emacs -Q
> M-x customize-group RET mh TAB [no match]
>
> Ie, none of the mh customization groups are visible to the customize interface.
> This is because you use non-standard macros defgroup-mh, defcustom-mh etc.
> Because of this, custom-make-dependencies fails to add any mh-e entries
> to cus-load.el.
>
> We can paper over this in the Emacs lisp/Makefile by simply
> loading mh-e/mh-e when running custom-make-dependencies.

Good to know, thanks!

> It would be simpler if mh-e used standard macros though.

Agreed!

> Are the -mh versions still needed?
> "This macro is used by Emacs versions that lack the :package-version
> keyword, introduced in Emacs 22."
> Do you still want to support people taking the latest mh-e and running
> it on Emacs older than 22.1 (released 2007)?

We don't even support Emacs 22 any more. However, we support XEmacs
21.4. Let me check to see if we can drop the -mh versions there. If so,
I will. If not, I will ask you kindly to "paper over this" until further
notice. Thanks!

> I see this came up before.
> http://sourceforge.net/mailarchive/forum.php?thread_name=19664.1182361165%40juniper.net&forum_name=mh-e-devel

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD






^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-05-13  1:31 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-05-11  1:49 bug#14384: mh-e non-standard names for defcustom etc Glenn Morris
2013-05-13  1:31 ` Bill Wohler

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).