(emacs)Antinews

What is the meaning of the following paragraph in
`(emacs)Antinews'?
In as far as I know, Emacs does still not (by default)
respond to the
described clicks in an xterm.  Was this paragraph added in
the short
period that xterm-mouse-mode was enabled by default?  I
propose to
remove the paragraph.

   * On an xterm, Emacs provides a more convincing
simulation of a
     text terminal by not responding to mouse-clicks on the
mode-line,
     header-line, or display margin.

Sincerely,

Luc.


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

 > What is the meaning of the following paragraph in
`(emacs)Antinews'?
 > In as far as I know, Emacs does still not (by default)
respond to the
 > described clicks in an xterm.  Was this paragraph
added in the short
 > period that xterm-mouse-mode was enabled by default?

Yes, I think so.

 >                                                     I
propose to
 > remove the paragraph.
 > 
 >    * On an xterm, Emacs provides a more convincing
simulation of a
 >      text terminal by not responding to mouse-clicks
on the mode-line,
 >      header-line, or display margin.

You pushed to disable this feature, now you're trying to
remove references to
it.  There seems little point in adding features if its hard
for users to find
out about them.  How about:

    * On an xterm, Emacs provides a more convincing
simulation of a text
      terminal by being unable to respond to mouse-clicks on
the mode-line,
      header-line, or display margin.

Nick


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

Nick Roberts wrote:

   You pushed to disable this feature, now you're trying to
remove
   references to it.

There was no reference to Xterm Mouse mode in anti.texi;
anti.texi
just gave the impression to describe the default behavior.

       * On an xterm, Emacs provides a more convincing
simulation of a text
	 terminal by being unable to respond to mouse-clicks on the
mode-line,
	 header-line, or display margin.

Still same problems: no reference to Xterm Mouse mode and
still seems
to describe default behavior.

Some other stuff in anti.texi seems out of date too.  I
propose the
following changes to anti.texi and I can install them, if
desired.

===File ~/anti.texi-diff====================================
*** anti.texi	30 Oct 2005 08:25:39 -0600	1.32
--- anti.texi	24 Jan 2006 20:14:51 -0600	
***************
*** 34,42 ****
  onto an Emacs window, nothing will happen.
  
  item
! On an xterm, Emacs provides a more convincing simulation
of a text
! terminal by not responding to mouse-clicks on the
mode-line,
! header-line, or display margin.
  
  item
  For simplicity, windows always have fringes.  We wouldn't
want to
--- 34,40 ----
  onto an Emacs window, nothing will happen.
  
  item
! The minor mode Xterm Mouse mode is no longer available.
  
  item
  For simplicity, windows always have fringes.  We wouldn't
want to
***************
*** 88,95 ****
  the code command does not expand samp{$}
at all.
  
  item
! Emacs will not query you if a command accumulates too much
undo
! information.  If Emacs runs out of memory as a result, it
will handle
  this by crashing.
  
  item
--- 86,93 ----
  the code command does not expand samp{$}
at all.
  
  item
! If a single command accumulates too much undo information,
Emacs never
! discards it.  If Emacs runs out of memory as a result, it
will handle
  this by crashing.
  
  item
***************
*** 131,139 ****
  equivalent to typing them once.  kbd ignores numeric
arguments.
  
  item
! If you want to repeat a jump to a previous mark, you
should supply the
! prefix argument explicitly.  So, instead of typing kbd{C-u
C-SPC
! C-SPC C-SPC}, type kbd{C-u C-SPC C-u C-SPC C-u C-SPC}.
  
  item
  kbd{C-key C-key} has no special
meaning--it just sets the
--- 129,135 ----
  equivalent to typing them once.  kbd ignores numeric
arguments.
  
  item
! The user option code has been
removed.
  
  item
  kbd{C-key C-key} has no special
meaning--it just sets the
***************
*** 261,267 ****
  The Kmacro package has been replaced with a simple and
elegant
  keyboard macro system.  Use kbd{C-x (} to start a new
keyboard macro,
  kbd{C-x )} to end the macro, and kbd{C-x
e} to execute the last
! macro.
  
  item
  The Calc, CUA, GDB-UI, Ibuffer, Ido, Password, Printing,
Reveal,
--- 257,264 ----
  The Kmacro package has been replaced with a simple and
elegant
  keyboard macro system.  Use kbd{C-x (} to start a new
keyboard macro,
  kbd{C-x )} to end the macro, and kbd{C-x
e} to execute the last
! macro.  Use kbd{M-x name-last-kbd-macro} to name the
most recently
! defined macro.
  
  item
  The Calc, CUA, GDB-UI, Ibuffer, Ido, Password, Printing,
Reveal,
============================================================


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

The info in NEWS is also outdated.  I propose the following
patch,
which I can install if desired.

===File ~/NEWS-diff=========================================
*** NEWS	22 Jan 2006 17:20:24 -0600	1.1307
--- NEWS	24 Jan 2006 20:27:07 -0600	
***************
*** 1460,1468 ****
  
  ** Xterm support:
  
! ---
! *** Emacs now responds to mouse-clicks on the mode-line,
header-line and
! display margin, when run in an xterm.
  
  ---
  *** Improved key bindings support when running in an
xterm.
--- 1460,1469 ----
  
  ** Xterm support:
  
! +++
! *** If you enable the new minor mode Xterm Mouse mode,
Emacs will
! respond to mouse-clicks on the mode-line, header-line and
display
! margin, when run in an xterm.
  
  ---
  *** Improved key bindings support when running in an
xterm.
============================================================


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

 >        * On an xterm, Emacs provides a more convincing
simulation of a text
 > 	 terminal by being unable to respond to mouse-clicks
on the mode-line,
 > 	 header-line, or display margin.
 > 
 > Still same problems: no reference to Xterm Mouse mode
and still seems
 > to describe default behavior.

I disagree, to me "unable" suggests "cannot
be configured".

 > Some other stuff in anti.texi seems out of date too. 
I propose the
 > following changes to anti.texi and I can install them,
if desired.
 ...
 > ! The minor mode Xterm Mouse mode is no longer
available.

xterm-mouse-mode is not new to Emacs 22, its just that when
enabled, mouse
clicks didn't used to work in the mode-line, header-line, or
display margin.

Nick


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

 > ! +++
 > ! *** If you enable the new minor mode Xterm Mouse
mode, Emacs will
 > ! respond to mouse-clicks on the mode-line,
header-line and display
 > ! margin, when run in an xterm.

 ! +++
 ! *** If you enable Xterm Mouse mode, Emacs will respond to
mouse-clicks
 ! on the mode-line, header-line and display margin, when
run in an xterm.

Nick


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

Nick Roberts wrote:

   xterm-mouse-mode is not new to Emacs 22, its just that
when enabled, mouse
   clicks didn't used to work in the mode-line, header-line,
or display margin.

OK, so what about:

item
Enabling Xterm Mouse mode no longer makes Emacs respond to
mouse
clicks on the mode line, header line or display margin, when
run in an
xterm.


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

> Date: Tue, 24 Jan 2006 20:19:50 -0600 (CST)
> From: Luc Teirlinck <teirllmdms.auburn.edu>
> Cc: emacs-develgnu.org
> 
>   item
> ! On an xterm, Emacs provides a more convincing
simulation of a text
> ! terminal by not responding to mouse-clicks on the
mode-line,
> ! header-line, or display margin.
>   
>   item
>   For simplicity, windows always have fringes.  We
wouldn't want to
> --- 34,40 ----
>   onto an Emacs window, nothing will happen.
>   
>   item
> ! The minor mode Xterm Mouse mode is no longer
available.

Antinews is supposed to be funny and humorous, not dead
serious like
NEWS and other documentation.  This and other changes you
suggest
remove almost every trace of humor from the original
entries.


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

Eli Zaretskii <elizgnu.org> writes:

>>   item
>> ! On an xterm, Emacs provides a more convincing
simulation of a text
>> ! terminal by not responding to mouse-clicks on the
mode-line,
>> ! header-line, or display margin.

> Antinews is supposed to be funny and humorous, not dead
serious like
> NEWS and other documentation.  This and other changes
you suggest
> remove almost every trace of humor from the original
entries.

How about:

On an xterm, even if you enable XTerm Mouse Mode, Emacs
provides a
more convincing simulation of a text terminal by not
responding to
mouse-clicks on the mode-line, header-line, or display
margin.

-- 
Kim F. Storm <stormcua.dk> http://www.cua.dk



_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

These changes are good, apart from the Xterm one, which may
not be
entirely correct.


_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel