Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
e9b28650
Commit
e9b28650
authored
Oct 13, 2005
by
Bill Wohler
Browse files
(MH_E_SRC): Renamed from MH-E-SRC per NMAKE restrictions. Suggested by
David Robinow <drobinow@gmail.com>.
parent
b4a63d75
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
2 deletions
+7
-2
lisp/ChangeLog
lisp/ChangeLog
+5
-0
lisp/makefile.w32-in
lisp/makefile.w32-in
+2
-2
No files found.
lisp/ChangeLog
View file @
e9b28650
2005-10-13 Bill Wohler <wohler@newt.com>
* makefile.w32-in (MH_E_SRC): Renamed from MH-E-SRC per NMAKE
restrictions. Suggested by David Robinow <drobinow@gmail.com>.
2005-10-13 Kenichi Handa <handa@m17n.org>
* international/utf-8.el (utf-8-compose): Display an invalid UTF-8
...
...
lisp/makefile.w32-in
View file @
e9b28650
...
...
@@ -288,7 +288,7 @@ recompile: mh-autoloads doit
# Update MH-E internal autoloads. These are not to be confused with
# the autoloads for the MH-E entry points, which are already in
# loaddefs.el.
MH
-E-
SRC
=
$(lisp)
/mh-e/mh-acros.el
$(lisp)
/mh-e/mh-alias.el
\
MH
_E_
SRC
=
$(lisp)
/mh-e/mh-acros.el
$(lisp)
/mh-e/mh-alias.el
\
$(lisp)
/mh-e/mh-comp.el
$(lisp)
/mh-e/mh-customize.el
\
$(lisp)
/mh-e/mh-e.el
$(lisp)
/mh-e/mh-funcs.el
\
$(lisp)
/mh-e/mh-mime.el
$(lisp)
/mh-e/mh-pick.el
\
...
...
@@ -299,7 +299,7 @@ MH-E-SRC = $(lisp)/mh-e/mh-acros.el $(lisp)/mh-e/mh-alias.el \
$(lisp)
/mh-e/mh-utils.el
mh-autoloads
:
$(lisp)/mh-e/mh-loaddefs.el
$(lisp)/mh-e/mh-loaddefs.el
:
$(MH
-E-
SRC)
$(lisp)/mh-e/mh-loaddefs.el
:
$(MH
_E_
SRC)
echo
";;; mh-loaddefs.el --- automatically extracted autoloads"
>
$@
echo
";;"
>>
$@
echo
";;; Copyright (C) 2003, 2004, 2005 Free Software Foundation, Inc."
>>
$@
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment