diff options
| author | Glenn Morris <rgm@gnu.org> | 2013-09-17 00:26:07 -0700 |
|---|---|---|
| committer | Glenn Morris <rgm@gnu.org> | 2013-09-17 00:26:07 -0700 |
| commit | 39eb0cb563f5287270f3946804456dc766386638 (patch) | |
| tree | 227dbbed9d2d039e1531b01baa96c4e8e3d87c67 | |
| parent | b7ad2f7401a22e6189d1b0a0523a3f98d1f70be5 (diff) | |
| parent | 16af23266cd8671281d89ebb2c15d3acac7ba914 (diff) | |
| download | emacs-39eb0cb563f5287270f3946804456dc766386638.tar.gz | |
Merge from emacs-24; up to 2013-01-03T02:31:36Z!rgm@gnu.org
| -rw-r--r-- | etc/CONTRIBUTE | 38 | ||||
| -rw-r--r-- | lisp/ChangeLog | 6 | ||||
| -rw-r--r-- | lisp/abbrev.el | 4 | ||||
| -rw-r--r-- | lisp/subr.el | 2 |
4 files changed, 23 insertions, 27 deletions
diff --git a/etc/CONTRIBUTE b/etc/CONTRIBUTE index 3ccd180aa0c..5d6b4238c97 100644 --- a/etc/CONTRIBUTE +++ b/etc/CONTRIBUTE @@ -60,6 +60,11 @@ answer any questions you may have (or point you to the people with the answers), at the emacs-devel@gnu.org mailing list. A copyright disclaimer is also a possibility, but we prefer an assignment. +Note that the disclaimer, like an assignment, involves you sending +signed paperwork to the FSF (simply saying "this is in the public domain" +is not enough). Also, a disclaimer cannot be applied to future work, it +has to be repeated each time you want to send something new. + We can accept small changes (roughly, fewer than 15 lines) without an assignment. This is a cumulative limit (e.g. three separate 5 line patches) over all your contributions. @@ -94,8 +99,7 @@ revise your patch, send it as a followup to the initial topic. ** Description -For bug fixes, a description of the bug and how your patch fixes this -bug. +For bug fixes, a description of the bug and how your patch fixes it. For new features, a description of the feature and your implementation. @@ -103,7 +107,7 @@ For new features, a description of the feature and your implementation. A ChangeLog entry as plaintext (separate from the patch). -See the various ChangeLog files for format and content. Note that, +See the existing ChangeLog files for format and content. Note that, unlike some other projects, we do require ChangeLogs also for documentation, i.e. Texinfo files. @@ -112,24 +116,16 @@ Manual, for how to write good log entries. ** The patch itself. -Please use "Context Diff" format. - If you are accessing the Bazaar repository, make sure your copy is up-to-date (e.g. with `bzr pull'), then use bzr diff --no-aliases --diff-options=-cp Else, use diff -cp OLD NEW -If your version of diff does not support these options, then get the -latest version of GNU Diff. - ** Mail format. -We prefer to get the patches as inline plain text. - -Please be aware of line wrapping which will make the patch unreadable -and useless for us. To avoid that, you can use MIME attachments or, -as a last resort, uuencoded gzipped text. +We prefer to get the patches as plain text, either inline (be careful +your mail client does not change line breaks) or as MIME attachments. ** Please reread your patch before submitting it. @@ -179,18 +175,12 @@ by following links from http://savannah.gnu.org/mail/?group=emacs . ** Document your changes. -Think carefully about whether your change requires updating the -documentation. If it does, you can either do this yourself or add an -item to the NEWS file. - -If you document your change in NEWS, please mark the NEWS entry with -the documentation status of the change: if you submit the changes for -the manuals, mark it with "+++"; if it doesn't need to be documented, -mark it with "---"; if it needs to be documented, but you didn't -submit documentation changes, leave the NEWS entry unmarked. (These -marks are checked by the Emacs maintainers to make sure every change -was reflected in the manuals.) +Any change that matters to end-users should have a NEWS entry. +Think about whether your change requires updating the documentation +(both manuals and doc-strings). If you know it does not, mark the NEWS +entry with "---". If you know that *all* the necessary documentation +updates have been made, mark the entry with "+++". Otherwise do not mark it. ** Understanding Emacs Internals. diff --git a/lisp/ChangeLog b/lisp/ChangeLog index 5809c2a4513..f36ed3ceebb 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,3 +1,9 @@ +2013-09-17 Stefan Monnier <monnier@iro.umontreal.ca> + + * subr.el (eval-after-load): Preserve evaluation order (bug#15389). + + * abbrev.el (abbrev--check-chars): Fix thinko (bug#15329). + 2013-09-16 Stefan Monnier <monnier@iro.umontreal.ca> * icomplete.el (icomplete-in-buffer): New var. diff --git a/lisp/abbrev.el b/lisp/abbrev.el index d7d4482693d..458d8741ac8 100644 --- a/lisp/abbrev.el +++ b/lisp/abbrev.el @@ -607,9 +607,9 @@ An obsolete but still supported calling form is: "Check if the characters in ABBREV have word syntax in either the current (if global is nil) or standard syntax table." (with-syntax-table - (cond ((null global) (standard-syntax-table)) + (cond ((null global) (syntax-table)) ;; ((syntax-table-p global) global) - (t (syntax-table))) + (t (standard-syntax-table))) (when (string-match "\\W" abbrev) (let ((badchars ()) (pos 0)) diff --git a/lisp/subr.el b/lisp/subr.el index 7df1e86b5bf..f8b5d605f91 100644 --- a/lisp/subr.el +++ b/lisp/subr.el @@ -3878,7 +3878,7 @@ This function makes or adds to an entry on `after-load-alist'." (when (equal file lfn) (remove-hook 'after-load-functions fun) (funcall func)))) - (add-hook 'after-load-functions fun))))))) + (add-hook 'after-load-functions fun 'append))))))) ;; Add FORM to the element unless it's already there. (unless (member delayed-func (cdr elt)) (nconc elt (list delayed-func))))))) |
