[Emacs-diffs] Changes to emacs/etc/NEWS

[Richard M . Stallman]

Index: emacs/etc/NEWS
diff -c emacs/etc/NEWS:1.1113 emacs/etc/NEWS:1.1114
*** emacs/etc/NEWS:1.1113       Mon Jan 31 23:15:28 2005
--- emacs/etc/NEWS      Thu Feb  3 06:45:26 2005
***************
*** 126,147 ****
  boundries etc.  For more info, see the documentation of the variable
  `calculator-radix-grouping-mode'.
  
  ** You can now follow links by clicking Mouse-1 on the link.
  
  Traditionally, Emacs uses a Mouse-1 click to set point and a Mouse-2
  click to follow a link, whereas most other applications use a Mouse-1
  click for both purposes, depending on whether you click outside or
! inside a link.  With release 21.4, the behaviour of a Mouse-1 click
! has been changed to match this context-sentitive dual behaviour.
  
  Depending on the current mode, a Mouse-2 click in Emacs may do much
! more than just follow a link, so the new Mouse-1 behaviour is only
  activated for modes which explicitly mark a clickable text as a "link"
! (see the new function `mouse-on-link-p' for details).  The lisp
  packages that are included in release 21.4 have been adapted to do
  this, but external packages may not yet support this.  However, there
  is no risk in using such packages, as the worst thing that could
! happen is that you get the original Mouse-1 behaviour when you click
  on a link, which typically means that you set point where you click.
  
  If you want to get the original Mouse-1 action also inside a link, you
--- 126,148 ----
  boundries etc.  For more info, see the documentation of the variable
  `calculator-radix-grouping-mode'.
  
+ +++
  ** You can now follow links by clicking Mouse-1 on the link.
  
  Traditionally, Emacs uses a Mouse-1 click to set point and a Mouse-2
  click to follow a link, whereas most other applications use a Mouse-1
  click for both purposes, depending on whether you click outside or
! inside a link.  Now the behavior of a Mouse-1 click has been changed
! to match this context-sentitive dual behavior.
  
  Depending on the current mode, a Mouse-2 click in Emacs may do much
! more than just follow a link, so the new Mouse-1 behavior is only
  activated for modes which explicitly mark a clickable text as a "link"
! (see the new function `mouse-on-link-p' for details).  The Lisp
  packages that are included in release 21.4 have been adapted to do
  this, but external packages may not yet support this.  However, there
  is no risk in using such packages, as the worst thing that could
! happen is that you get the original Mouse-1 behavior when you click
  on a link, which typically means that you set point where you click.
  
  If you want to get the original Mouse-1 action also inside a link, you
***************
*** 152,158 ****
  Dragging the Mouse-1 inside a link still performs the original
  drag-mouse-1 action, typically copy the text.
  
! You can customize the new Mouse-1 behaviour via the new user option
  `mouse-1-click-follows-link'.
  
  +++
--- 153,159 ----
  Dragging the Mouse-1 inside a link still performs the original
  drag-mouse-1 action, typically copy the text.
  
! You can customize the new Mouse-1 behavior via the new user option
  `mouse-1-click-follows-link'.
  
  +++
***************
*** 476,482 ****
  cursor will be displayed in the fringe when positioned on that newline.
  
  The new user option 'overflow-newline-into-fringe' may be set to nil to
! revert to the old behaviour of continuing such lines.
  
  +++
  ** The buffer boundaries (i.e. first and last line in the buffer) may
--- 477,483 ----
  cursor will be displayed in the fringe when positioned on that newline.
  
  The new user option 'overflow-newline-into-fringe' may be set to nil to
! revert to the old behavior of continuing such lines.
  
  +++
  ** The buffer boundaries (i.e. first and last line in the buffer) may
***************
*** 1538,1544 ****
  
  ** Unexpected yanking of text due to accidental clicking on the mouse
  wheel button (typically mouse-2) during wheel scrolling is now avoided.
! This behaviour can be customized via the mouse-wheel-click-event and
  mouse-wheel-inhibit-click-time variables.
  
  +++
--- 1539,1545 ----
  
  ** Unexpected yanking of text due to accidental clicking on the mouse
  wheel button (typically mouse-2) during wheel scrolling is now avoided.
! This behavior can be customized via the mouse-wheel-click-event and
  mouse-wheel-inhibit-click-time variables.
  
  +++
***************
*** 2370,2376 ****
  
  In addition, when ending or calling a macro with C-x e, the macro can
  be repeated immediately by typing just the `e'.  You can customize
! this behaviour via the variable kmacro-call-repeat-key and
  kmacro-call-repeat-with-arg.
  
  Keyboard macros can now be debugged and edited interactively.
--- 2371,2377 ----
  
  In addition, when ending or calling a macro with C-x e, the macro can
  be repeated immediately by typing just the `e'.  You can customize
! this behavior via the variable kmacro-call-repeat-key and
  kmacro-call-repeat-with-arg.
  
  Keyboard macros can now be debugged and edited interactively.
***************
*** 3152,3158 ****
  buffer is multibyte, the output of the process is at first converted
  to multibyte by `string-to-multibyte' then inserted in the buffer.
  Previously, it was converted to multibyte by `string-as-multibyte',
! which was not compatible with the behaviour of file reading.
  
  +++
  ** New function `string-to-multibyte' converts a unibyte string to a
--- 3153,3159 ----
  buffer is multibyte, the output of the process is at first converted
  to multibyte by `string-to-multibyte' then inserted in the buffer.
  Previously, it was converted to multibyte by `string-as-multibyte',
! which was not compatible with the behavior of file reading.
  
  +++
  ** New function `string-to-multibyte' converts a unibyte string to a
***************
*** 3640,3646 ****
  The `insert-for-yank' function looks for a yank-handler property on
  the first character on its string argument (typically the first
  element on the kill-ring).  If a yank-handler property is found,
! the normal behaviour of `insert-for-yank' is modified in various ways:
  
    When FUNCTION is present and non-nil, it is called instead of `insert'
  to insert the string.  FUNCTION takes one argument--the object to insert.
--- 3641,3647 ----
  The `insert-for-yank' function looks for a yank-handler property on
  the first character on its string argument (typically the first
  element on the kill-ring).  If a yank-handler property is found,
! the normal behavior of `insert-for-yank' is modified in various ways:
  
    When FUNCTION is present and non-nil, it is called instead of `insert'
  to insert the string.  FUNCTION takes one argument--the object to insert.
***************
*** 3728,3734 ****
  
  On some systems, when emacs reads the output from a subprocess, the
  output data is read in very small blocks, potentially resulting in
! very poor performance.  This behaviour can be remedied to some extent
  by setting the new variable process-adaptive-read-buffering to a
  non-nil value (the default), as it will automatically delay reading
  from such processes, to allowing them to produce more output before
--- 3729,3735 ----
  
  On some systems, when emacs reads the output from a subprocess, the
  output data is read in very small blocks, potentially resulting in
! very poor performance.  This behavior can be remedied to some extent
  by setting the new variable process-adaptive-read-buffering to a
  non-nil value (the default), as it will automatically delay reading
  from such processes, to allowing them to produce more output before
***************
*** 4242,4248 ****
  If you want the old behavior, set selection-coding-system to
  compound-text, which may be significantly more efficient.  Using
  compound-text-with-extensions seems to be necessary only for decoding
! text from applications under XFree86 4.2, whose behaviour is actually
  contrary to the compound text specification.
  
  
--- 4243,4249 ----
  If you want the old behavior, set selection-coding-system to
  compound-text, which may be significantly more efficient.  Using
  compound-text-with-extensions seems to be necessary only for decoding
! text from applications under XFree86 4.2, whose behavior is actually
  contrary to the compound text specification.