1. 20 Apr, 2019 1 commit
  2. 19 Apr, 2019 4 commits
  3. 18 Apr, 2019 1 commit
    • Basil L. Contovounesios's avatar
      Fix off-by-one-link error in image--set-property · a4ad7bed
      Basil L. Contovounesios authored
      * lisp/image.el (image--set-property): Ensure new value is set even
      in the unlikely case that the plist is empty.  Fix off-by-one-link
      error when deleting a property. (bug#35285)
      * test/lisp/image-tests.el: New file.
      (image--set-property): New test.
      a4ad7bed
  4. 16 Apr, 2019 4 commits
  5. 15 Apr, 2019 1 commit
    • Eli Zaretskii's avatar
      Fix the MSDOS build when running under CWSDPMI · 70ec3928
      Eli Zaretskii authored
      * src/msdos.c (the_only_tty_output): Define.
      * src/msdos.h (the_only_tty_output): Declare.
      * src/frame.c (make_terminal_frame) [MSDOS]:
      * src/dispnew.c (init_display) [MSDOS]: Set up
      f->output_data.tty pointer using the_only_tty_output, before
      dereferencing the pointer.  This prevents crashes with DPMI
      servers that provide NULL pointer protection.
      70ec3928
  6. 14 Apr, 2019 5 commits
  7. 12 Apr, 2019 1 commit
  8. 11 Apr, 2019 9 commits
  9. 10 Apr, 2019 2 commits
  10. 09 Apr, 2019 2 commits
    • Gemini Lasswell's avatar
      Address name conflicts in EIEIO documentation (bug#31660) · 8d2f1df5
      Gemini Lasswell authored
      * doc/misc/eieio.texi (Quick Start): Rename the class used in the
      example from 'record' to 'person'.
      (Building Classes): Advise user to check for name conflicts before
      naming a class.  Add a missing apostrophe.
      (Making New Objects): Correct grammar.  Rename the class used in the
      example from 'record' to 'my-class'.
      8d2f1df5
    • Mattias Engdegård's avatar
      Clarify the TESTFN argument to `alist-get' · 00a2d57a
      Mattias Engdegård authored
      * lisp/subr.el (alist-get):
      Rephrase the initial text to clarify the meaning of the TESTFN argument.
      It's an equality predicate, not a look-up function (Bug#35206).
      
      (cherry picked from commit c8146558)
      00a2d57a
  11. 08 Apr, 2019 1 commit
  12. 06 Apr, 2019 5 commits
  13. 04 Apr, 2019 1 commit
  14. 20 Mar, 2019 3 commits
    • Paul Eggert's avatar
      Say which regexp ranges should be avoided · 0924b27b
      Paul Eggert authored
      * doc/lispref/searching.texi (Regexp Special): Say that
      regular expressions like "[a-m-z]" and "[[:alpha:]-~]" should
      be avoided, for the same reason that regular expressions like
      "+" and "*" should be avoided: POSIX says their behavior is
      undefined, and they are confusing anyway.  Also, explain
      better what happens when the bound of a range is a raw 8-bit
      byte; the old explanation appears to have been obsolete
      anyway.  Finally, say that ranges like "[\u00FF-\xFF]" that
      mix non-ASCII characters and raw 8-bit bytes should be
      avoided, since it’s not clear what they should mean.
      0924b27b
    • NicolasPetton's avatar
      ; * lisp/ldefs-boot.el: Update. · 297a141c
      NicolasPetton authored
      297a141c
    • NicolasPetton's avatar
      * etc/AUTHORS: Update. · 24b6e6ed
      NicolasPetton authored
      24b6e6ed