procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; Spelling fixes

Browse source
This commit is contained in:
Paul Eggert 2018-03-01 18:34:17 -08:00
parent 3968f72be8
commit dd88499e89
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
ChangeLog.3
View file

@ -38136,7 +38136,7 @@
^
* src/frame.c (x_set_frame_parameters): Drop width_changed and
height_changed variables in favour of storing that information in
height_changed variables in favor of storing that information in
width and height variables.
2016-09-12 Michal Nazarewicz <mina86@mina86.com>
@ -38193,7 +38193,7 @@
Refactor common code in {upcase,downcase,capitalize}-word functions
* src/casefiddle.c (operate_on_word): Removed in favour of…
* src/casefiddle.c (operate_on_word): Removed in favor of…
(casify_word) …new function which does what operate_on_word did plus
what all of the common code from *-word functions.
(upcase-word, downcase-word, capitalize-word): Move code common between
@ -38418,9 +38418,9 @@
alphabeticp. Because both of those functions require Unicode general
category lookup, this resulted in unnecessary lookups (if alphabeticp
return false decimalp had to perform another lookup). Drop decimalnump
in favour of alphanumericp which combines decimelnump with alphabeticp.
in favor of alphanumericp which combines decimelnump with alphabeticp.
* src/character.c (decimalnump): Remove in favour of…
* src/character.c (decimalnump): Remove in favor of…
(alphanumericp): …new function.
* src/regex.c (ISALNUM): Use alphanumericp.
@ -43563,10 +43563,10 @@
2016-06-08 Michal Nazarewicz <mina86@mina86.com>
Remove ‘ert-with-function-mocked’ macro in favour of ‘cl-letf’ macro
Remove ‘ert-with-function-mocked’ macro in favor of ‘cl-letf’ macro
* lisp/emacs-lisp/ert-x.el (ert-with-function-mocked): Remove macro
in favour of ‘cl-letf’ macro which is more generic. All existing
in favor of ‘cl-letf’ macro which is more generic. All existing
uses are migrated accordingly. The macro has not been included in
an official release yet so it should be fine to delete it.