/etc/PROBLEMS - minor cleanup

[Steve Kemp]

I thought I'd posted this yesterday, but aparantly not.

  Minor spelling fixes, and a URL change - I think the http URL
 should be used in preference to the ftp one, personal preference
 on that one I guess.

Steve
---

*** PROBLEMS-orig       Mon Dec 10 09:12:38 2001
--- PROBLEMS    Mon Dec 17 11:59:10 2001
***************
*** 79,85 ****
  following section near the end of the file src/m/macppc.h in the Emacs
  distribution:
  
!   #if 0  /* This breaks things on PPC GNU/Linux ecept for Yellowdog,
            even with identical GCC, as, ld.  Let's take it out until we
            know what's really going on here.  */
    /* GCC 2.95 and newer on GNU/Linux PPC changed the load address to
--- 79,85 ----
  following section near the end of the file src/m/macppc.h in the Emacs
  distribution:
  
!   #if 0  /* This breaks things on PPC GNU/Linux except for Yellowdog,
            even with identical GCC, as, ld.  Let's take it out until we
            know what's really going on here.  */
    /* GCC 2.95 and newer on GNU/Linux PPC changed the load address to
***************
*** 371,377 ****
  files' data to disk quickly enough, and the Emacs executable file is
  left ``busy'' for several seconds after Emacs has finished dumping
  itself.  This causes the subsequent commands which invoke the dumped
! Emacs excutable to fail with the above message.
  
  In some of these cases, a time skew between the NFS server and the
  machine where Emacs is built is detected and reported by GNU Make
--- 371,377 ----
  files' data to disk quickly enough, and the Emacs executable file is
  left ``busy'' for several seconds after Emacs has finished dumping
  itself.  This causes the subsequent commands which invoke the dumped
! Emacs executable to fail with the above message.
  
  In some of these cases, a time skew between the NFS server and the
  machine where Emacs is built is detected and reported by GNU Make
***************
*** 447,453 ****
  vast majority of well-formatted program source files don't have such
  parens, and therefore this assumption is used to allow optimizations
  in Font Lock's syntactical analysis.  These optimizations avoid some
! patological cases where jit-lock, the Just-in-Time fontification
  introduced with Emacs 21.1, could significantly slow down scrolling
  through the buffer, especially scrolling backwards, and also jumping
  to the end of a very large buffer.
--- 447,453 ----
  vast majority of well-formatted program source files don't have such
  parens, and therefore this assumption is used to allow optimizations
  in Font Lock's syntactical analysis.  These optimizations avoid some
! pathological cases where jit-lock, the Just-in-Time fontification
  introduced with Emacs 21.1, could significantly slow down scrolling
  through the buffer, especially scrolling backwards, and also jumping
  to the end of a very large buffer.
***************
*** 464,470 ****
  * When running on KDE, colors or fonts are not as specified for Emacs,
  or messed up.
  
! For examlpe, you could see background you set for Emacs only in the
  empty portions of the Emacs display, while characters have some other
  background.
  
--- 464,470 ----
  * When running on KDE, colors or fonts are not as specified for Emacs,
  or messed up.
  
! For example, you could see background you set for Emacs only in the
  empty portions of the Emacs display, while characters have some other
  background.
  
***************
*** 911,917 ****
  This is a limitation of the Operating System, and can cause problems
  when shutting down Windows. Ensure that all subprocesses are exited
  cleanly before exiting Emacs. For more details, see the FAQ at
! ftp://ftp.gnu.org/gnu/windows/emacs/doc/index.html
  
  * Mail sent through Microsoft Exchange in some encodings appears to be
  mangled and is not seen correctly in Rmail or Gnus.  We don't know
--- 911,917 ----
  This is a limitation of the Operating System, and can cause problems
  when shutting down Windows. Ensure that all subprocesses are exited
  cleanly before exiting Emacs. For more details, see the FAQ at
! http://www.gnu.org/software/emacs/windows/
  
  * Mail sent through Microsoft Exchange in some encodings appears to be
  mangled and is not seen correctly in Rmail or Gnus.  We don't know