view man/xemacs/mouse.texi @ 4885:6772ce4d982b

Fix hash tables, #'member*, #'assoc*, #'eql compiler macros if bignums lisp/ChangeLog addition: 2010-01-24 Aidan Kehoe <kehoea@parhasard.net> Correct the semantics of #'member*, #'eql, #'assoc* in the presence of bignums; change the integerp byte code to fixnump semantics. * bytecomp.el (fixnump, integerp, byte-compile-integerp): Change the integerp byte code to fixnump; add a byte-compile method to integerp using fixnump and numberp and avoiding a funcall most of the time, since in the non-core contexts where integerp is used, it's mostly distinguishing between fixnums and things that are not numbers at all. * byte-optimize.el (side-effect-free-fns, byte-after-unbind-ops) (byte-compile-side-effect-and-error-free-ops): Replace the integerp bytecode with fixnump; add fixnump to the side-effect-free-fns. Add the other extended number type predicates to the list in passing. * obsolete.el (floatp-safe): Mark this as obsolete. * cl.el (eql): Go into more detail in the docstring here. Don't bother checking whether both arguments are numbers; one is enough, #'equal will fail correctly if they have distinct types. (subst): Replace a call to #'integerp (deciding whether to use #'memq or not) with one to #'fixnump. Delete most-positive-fixnum, most-negative-fixnum from this file; they're now always in C, so they can't be modified from Lisp. * cl-seq.el (member*, assoc*, rassoc*): Correct these functions in the presence of bignums. * cl-macs.el (cl-make-type-test): The type test for a fixnum is now fixnump. Ditch floatp-safe, use floatp instead. (eql): Correct this compiler macro in the presence of bignums. (assoc*): Correct this compiler macro in the presence of bignums. * simple.el (undo): Change #'integerp to #'fixnump here, since we use #'delq with the same value as ELT a few lines down. src/ChangeLog addition: 2010-01-24 Aidan Kehoe <kehoea@parhasard.net> Fix problems with #'eql, extended number types, and the hash table implementation; change the Bintegerp bytecode to fixnump semantics even on bignum builds, since #'integerp can have a fast implementation in terms of #'fixnump for most of its extant uses, but not vice-versa. * lisp.h: Always #include number.h; we want the macros provided in it, even if the various number types are not available. * number.h (NON_FIXNUM_NUMBER_P): New macro, giving 1 when its argument is of non-immediate number type. Equivalent to FLOATP if WITH_NUMBER_TYPES is not defined. * elhash.c (lisp_object_eql_equal, lisp_object_eql_hash): Use NON_FIXNUM_NUMBER_P in these functions, instead of FLOATP, giving more correct behaviour in the presence of the extended number types. * bytecode.c (Bfixnump, execute_optimized_program): Rename Bintegerp to Bfixnump; change its semantics to reflect the new name on builds with bignum support. * data.c (Ffixnump, Fintegerp, syms_of_data, vars_of_data): Always make #'fixnump available, even on non-BIGNUM builds; always implement #'integerp in this file, even on BIGNUM builds. Move most-positive-fixnum, most-negative-fixnum here from number.c, so they are Lisp constants even on builds without number types, and attempts to change or bind them error. Use the NUMBERP and INTEGERP macros even on builds without extended number types. * data.c (fixnum_char_or_marker_to_int): Rename this function from integer_char_or_marker_to_int, to better reflect the arguments it accepts. * number.c (Fevenp, Foddp, syms_of_number): Never provide #'integerp in this file. Remove #'oddp, #'evenp; their implementations are overridden by those in cl.el. * number.c (vars_of_number): most-positive-fixnum, most-negative-fixnum are no longer here. man/ChangeLog addition: 2010-01-23 Aidan Kehoe <kehoea@parhasard.net> Generally: be careful to say fixnum, not integer, when talking about fixed-precision integral types. I'm sure I've missed instances, both here and in the docstrings, but this is a decent start. * lispref/text.texi (Columns): Document where only fixnums, not integers generally, are accepted. (Registers): Remove some ancient char-int confoundance here. * lispref/strings.texi (Creating Strings, Creating Strings): Be more exact in describing where fixnums but not integers in general are accepted. (Creating Strings): Use a more contemporary example to illustrate how concat deals with lists including integers about #xFF. Delete some obsolete documentation on same. (Char Table Types): Document that only fixnums are accepted as values in syntax tables. * lispref/searching.texi (String Search, Search and Replace): Be exact in describing where fixnums but not integers in general are accepted. * lispref/range-tables.texi (Range Tables): Be exact in describing them; only fixnums are accepted to describe ranges. * lispref/os.texi (Killing XEmacs, User Identification) (Time of Day, Time Conversion): Be more exact about using fixnum where only fixed-precision integers are accepted. * lispref/objects.texi (Integer Type): Be more exact (and up-to-date) about the possible values for integers. Cross-reference to documentation of the bignum extension. (Equality Predicates): (Range Table Type): (Array Type): Use fixnum, not integer, to describe a fixed-precision integer. (Syntax Table Type): Correct some English syntax here. * lispref/numbers.texi (Numbers): Change the phrasing here to use fixnum to mean the fixed-precision integers normal in emacs. Document that our terminology deviates from that of Common Lisp, and that we're working on it. (Compatibility Issues): Reiterate the Common Lisp versus Emacs Lisp compatibility issues. (Comparison of Numbers, Arithmetic Operations): * lispref/commands.texi (Command Loop Info, Working With Events): * lispref/buffers.texi (Modification Time): Be more exact in describing where fixnums but not integers in general are accepted.
author Aidan Kehoe <kehoea@parhasard.net>
date Sun, 24 Jan 2010 15:21:27 +0000
parents 376386a54a3c
children
line wrap: on
line source


@node Mouse Selection, Additional Mouse Operations, Mark, Top
@comment  node-name,  next,  previous,  up
@section Selecting Text with the Mouse
@cindex mouse selection

@cindex pointer shapes
  If you are using XEmacs under X, you can use the mouse pointer
to select text. (The normal mouse pointer is an I-beam, the same
pointer that @code{xterm} uses.)

@vindex modeline-pointer-glyph
@vindex nontext-pointer-glyph
@vindex text-pointer-glyph
The glyph variable @code{text-pointer-glyph} controls the shape of
the mouse pointer when over text.  You can also control the shape
of the mouse pointer when over nontext using @code{nontext-pointer-glyph},
and the shape of the mouse pointer when over the modeline using
@code{modeline-pointer-glyph}. (Remember, you should use
@code{set-glyph-image}, not @code{setq}, to set one of these
variables.)

@cindex pointer face
If you want to get fancy, you can set the foreground and background
colors of the mouse pointer by setting the @code{pointer} face.

There are two ways to select a region of text with the mouse:

  To select a word in text, double-click with the left mouse button
while the mouse cursor is over the word.  The word is highlighted when
selected. On monochrome monitors, a stippled background indicates that a
region of text has been highlighted. On color monitors, a color
background indicates highlighted text. You can triple-click to select
whole lines. 

To select an arbitrary region of text:

@enumerate
@item
Move the mouse cursor over the character at the beginning of the region of
text you want to select.
@item
Press and hold the left mouse button. 
@item
While holding the left mouse button down, drag the cursor to the
character at the end of the region of text you want to select.
@item
Release the left mouse button.
@end enumerate
The selected region of text is highlighted.

  Once a region of text is selected, it becomes the primary X selection
(@pxref{Using X Selections}) as well as the Emacs selected region. You
can paste it into other X applications and use the options from the
@b{Edit} pull-down menu on it.  Since it is also the Emacs region, you
can use Emacs region commands on it.

@node Additional Mouse Operations, Killing, Mouse Selection, Top
@section Additional Mouse Operations
@cindex mouse operations

XEmacs also provides the following mouse functions.  Most of these are
not bound to mouse gestures by default, but they are provided for your
customization pleasure.  For example, if you wanted @kbd{shift-left}
(that is, holding down the @key{Shift} key and clicking the left mouse
button) to delete the character at which you are pointing, then you
could do this:

@example
(global-set-key '(shift button1) 'mouse-del-char)
@end example

@findex mouse-del-char
@findex mouse-delete-window
@findex mouse-keep-one-window
@findex mouse-kill-line
@findex mouse-line-length
@findex mouse-scroll
@findex mouse-select
@findex mouse-select-and-split
@findex mouse-set-mark
@findex mouse-set-point
@findex mouse-track
@findex mouse-track-adjust
@findex mouse-track-and-copy-to-cutbuffer
@findex mouse-track-delete-and-insert

@table @kbd
@item mouse-del-char
Delete the character pointed to by the mouse.
@item mouse-delete-window
Delete the Emacs window that the mouse is on.
@item mouse-keep-one-window
Select the Emacs window that the mouse is on, then delete all other
windows on this frame.
@item mouse-kill-line
Kill the line pointed to by the mouse.
@item mouse-line-length
Print the length of the line indicated by the pointer.
@item mouse-scroll
Scroll point to the mouse position.
@item mouse-select
Select the Emacs window the mouse is on.
@item mouse-select-and-split
Select the Emacs window mouse is on, then split it vertically in half.
@item mouse-set-mark
Select the Emacs window the mouse is on and set the mark at the mouse 
position.  Display the cursor at that position for a second.
@item mouse-set-point
Select the Emacs window that the mouse is on and move point to the
mouse position.
@item mouse-track
Make a selection with the mouse.   This is the default binding of 
the left mouse button (@key{button1}).
@item mouse-track-adjust
Extend the existing selection.  This is the default binding of
@key{Shift-button1}.
@item mouse-track-and-copy-to-cutbuffer
Make a selection like @code{mouse-track}, but also copy it to the cut buffer.
@item mouse-track-delete-and-insert
Make a selection with the mouse and insert it at point.  This is the
default binding of @key{control-shift-button1}.
@item mouse-track-insert
Make a selection with the mouse and insert it at point.
This is the default binding of @key{control-button1}.
@item mouse-window-to-region
Narrow a window to the region between the cursor and the mouse pointer.
@end table

The @kbd{M-x mouse-track} command should be bound to a mouse button.  If
you click-and-drag, the selection is set to the region between the
point of the initial click and the point at which you release the
button.  These positions do not need to be ordered. 

If you click-and-release without moving the mouse, the point is moved,
and the selection is disowned (there will be no selection owner.)  The
mark will be set to the previous position of point.

If you double-click, the selection will extend by symbols instead of by
characters.  If you triple-click, the selection will extend by lines.

If you drag the mouse off the top or bottom of the window, you can
select pieces of text that are larger than the visible part of the
buffer; the buffer will scroll as necessary.

The selected text becomes the current X selection, and is also copied to
the top of the kill ring.  Point will be left at the position at
which you released the button and the mark will be left at the initial
click position.  Bind a mouse click to
@kbd{mouse-track-and-copy-to-cutbuffer} to copy selections to the cut buffer.
(See also the @code{mouse-track-adjust} command, on @kbd{Shift-button1}.)

The @kbd{M-x mouse-track-adjust} command should be bound to a mouse
button.  The selection will be enlarged or shrunk so that the point of
the mouse click is one of its endpoints.  This is only meaningful
after the @code{mouse-track} command (@key{button1}) has been executed.

The @kbd{M-x mouse-track-delete-and-insert} command is exactly the same
as the @code{mouse-track} command on @key{button1}, except that point is
not moved; the selected text is immediately inserted after being
selected; and the text of the selection is deleted.

The @kbd{M-x mouse-track-insert} command is exactly the same as the
@code{mouse-track} command on @key{button1}, except that point is not moved;
the selected text is immediately inserted after being selected; and the
selection is immediately disowned afterwards.