[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master f9bbe3189b0: Merge from origin/emacs-29
|
From: |
Po Lu |
|
Subject: |
master f9bbe3189b0: Merge from origin/emacs-29 |
|
Date: |
Thu, 20 Jul 2023 07:51:34 -0400 (EDT) |
branch: master
commit f9bbe3189b0eee627c3d8bca3221882cf0c29b26
Merge: 7ff41bf8ed8 4bd8e8c6d2b
Author: Po Lu <luangruo@yahoo.com>
Commit: Po Lu <luangruo@yahoo.com>
Merge from origin/emacs-29
4bd8e8c6d2b ; * src/xdisp.c: Fix wording in commentary.
3af27a4b815 Improve commentary in nsfns.m
5de5e4b4d0a Fix typos and ommissions in cus-edit.el
9d93c6ba14a ; * src/xdisp.c: Fix typos in the commentary.
86f2d6d62fc ; * src/xdisp.c: Improve commentary. (Bug#64596)
ac075176bf0 ; * admin/notes/bugtracker: Fix punctuation.
81518534471 ; * admin/notes/bugtracker: Use 'e.g.' throughout the doc...
f063f79a493 Convert NUL-containing NSString objects to Lisp strings c...
d172cd59854 ; * doc/lispref/keymaps.texi (Modifying Menus): Add cross...
927e8b470fc ; * doc/lispref/keymaps.texi (Extended Menu Items): Add @...
77f489421ec ; * src/xdisp.c: Minor improvements of the commentary.
ce3f9fba1a3 ; Improve accuracy of out-out-order message insertion
17073af84d7 ; Improve robustness of package-report-bug
---
admin/notes/bugtracker | 27 ++++----
doc/lispref/keymaps.texi | 20 +++---
lisp/cus-edit.el | 6 +-
lisp/emacs-lisp/package.el | 15 ++---
lisp/net/rcirc.el | 2 +-
src/nsfns.m | 8 ++-
src/xdisp.c | 153 ++++++++++++++++++++++++++++-----------------
7 files changed, 140 insertions(+), 91 deletions(-)
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker
index deb06f552cc..b47061884d6 100644
--- a/admin/notes/bugtracker
+++ b/admin/notes/bugtracker
@@ -39,7 +39,7 @@ tags 123 moreinfo|unreproducible|wontfix|patch|notabug
For a list of all bugs, see https://debbugs.gnu.org/db/pa/lemacs.html
This is a static page, updated once a day. There is also a dynamic
-list, generated on request. This accepts various options, eg to see
+list, generated on request. This accepts various options, e.g., to see
the most recent bugs:
https://debbugs.gnu.org/cgi/pkgreport.cgi?newest=100
@@ -98,7 +98,7 @@ you might want to have a dialog with the owner address,
outside of
normal bug reporting.)
** When reporting a new bug, to send a Cc to another address
-(e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header.
+(e.g., bug-cc-mode@gnu.org), do NOT just use a Cc: header.
Instead, use "X-Debbugs-Cc:". This ensures the Cc address(es) will get a
mail with the bug report number in. If you do not do this, each reply
in the subsequent discussion might end up creating a new bug.
@@ -138,7 +138,8 @@ The "maintainer email address" is "bug-gnu-emacs@gnu.org"
in most cases.
** To not get acknowledgment mail from the tracker,
add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus,
-you can add an element to gnus-posting-styles to do this automatically, eg:
+you can add an element to gnus-posting-styles to do this automatically,
+e.g.:
("gnu-emacs\\(-pretest\\)?-bug"
("X-Debbugs-No-Ack" "yes"))
@@ -222,14 +223,14 @@ Mail-Followup-To: 123@debbugs.gnu.org, person-who-closed
** Setting bug parameters.
There are two ways to set the parameters of bugs in the database
(tags, severity level, etc). When you report a new bug, you can
-provide a "pseudo-header" at the start of the report, eg:
+provide a "pseudo-header" at the start of the report, e.g.:
Package: emacs
Version: 23.0.60
Severity: minor
This can also include tags, or any X-Debbugs- setting.
-Some things (e.g. submitter) don't seem to work here.
+Some things (e.g., submitter) don't seem to work here.
Otherwise, send mail to the control server, control@debbugs.gnu.org.
At the start of the message body, supply the desired commands, one per
@@ -258,12 +259,12 @@ where VERSION is XX.YY numerical version number, like
42.1.
*** To reopen a closed bug:
reopen 123
-*** Bugs can be tagged in various ways (eg wontfix, patch, etc).
+*** Bugs can be tagged in various ways (e.g., wontfix, patch, etc).
The available tags are:
patch wontfix moreinfo unreproducible fixed notabug help security confirmed
easy
See https://debbugs.gnu.org/Developer#tags
The list of tags can be prefixed with +, - or =, meaning to add (the
-default), remove, or reset the tags. E.g.:
+default), remove, or reset the tags. E.g.:
tags 123 + wontfix
@@ -310,7 +311,7 @@ This will add a usertag "any-tag-you-like" to bug#1234.
The tag will
be associated with the user "emacs". If you omit the first line,
the tag will be associated with your email address.
-The syntax of the usertags command is the same as that of tags (eg wrt
+The syntax of the usertags command is the same as that of tags (e.g., wrt
the optional [=+-] argument).
b) In an initial submission, in the pseudo-header:
@@ -340,15 +341,15 @@ than one email address, but it does not seem to work for
me.)
**** To find bugs tagged with a specific usertag:
This works just like a normal tags search, but with the addition of a
-"users" field. Eg:
+"users" field. E.g.:
https://debbugs.gnu.org/cgi/pkgreport.cgi?users=emacs;tag=calendar
*** To merge bugs:
-Eg when bad replies create a bunch of new bugs for the same report.
-Bugs must all be in the same state (e.g. same package(s) and severity
+e.g., when bad replies create a bunch of new bugs for the same report.
+Bugs must all be in the same state (e.g., same package(s) and severity
-- see 'reassign' and 'severity' below), but need not have the same
-tags (tags are merged). E.g.:
+tags (tags are merged). E.g.:
merge 123 124 125 ...
@@ -557,7 +558,7 @@ debbugs-submit. Approved mail is passed on to the tracker.
tracker, since mail from whitelisted senders goes straight through.)
NOTE: An alternative to this would be to use listhelper AT nongnu.org
-as a moderator address. Eg the emacs-bug-tracker list uses this.
+as a moderator address. E.g., the emacs-bug-tracker list uses this.
It does basic spam processing on the moderator requests and
automatically rejects the obviously bogus ones. Someone still has to
accept the good ones though. The advantage of this would not be having
diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi
index 9e36d6716b9..24b7738caff 100644
--- a/doc/lispref/keymaps.texi
+++ b/doc/lispref/keymaps.texi
@@ -2506,7 +2506,8 @@ get a non-selectable menu item. This is mostly useful
when creating
separator lines and the like.
The tail of the list, @var{item-property-list}, has the form of a
-property list which contains other information.
+property list (@pxref{Property Lists}) which contains other
+information.
Here is a table of the properties that are supported:
@@ -3171,14 +3172,15 @@ the menu. To put it elsewhere in the menu, use
@code{keymap-set-after}:
@defun keymap-set-after map key binding &optional after
Define a binding in @var{map} for @var{key}, with value @var{binding},
-just like @code{define-key}, but position the binding in @var{map} after
-the binding for the event @var{after}. The argument @var{key} should
-represent a single menu item or key, and @var{after} should be a
-single event type---a symbol or a character, not a sequence. The new
-binding goes after the binding for @var{after}. If @var{after} is
-@code{t} or is omitted, then the new binding goes last, at the end of
-the keymap. However, new bindings are added before any inherited
-keymap.
+just like @code{keymap-set} (@pxref{Changing Key Bindings}), but
+position the binding in @var{map} after the binding for the event
+@var{after}. The argument @var{key} should represent a single menu
+item or key, and should satisfy @code{key-valid-p} (@pxref{Key
+Sequences}). @var{after} should be a single event type---a symbol or
+a character, not a sequence. The new binding goes after the binding
+for @var{after}. If @var{after} is @code{t} or is omitted, then the
+new binding goes last, at the end of the keymap. However, new
+bindings are added before any inherited keymap.
Here is an example:
diff --git a/lisp/cus-edit.el b/lisp/cus-edit.el
index dbef5f47cd6..4fca5761c17 100644
--- a/lisp/cus-edit.el
+++ b/lisp/cus-edit.el
@@ -3533,7 +3533,11 @@ GNUstep or Macintosh OS Cocoa interface.")
(const :format "PGTK "
:sibling-args (:help-echo "\
Pure-GTK interface.")
- ns)
+ pgtk)
+ (const :format "Haiku "
+ :sibling-args (:help-echo "\
+Haiku interface.")
+ haiku)
(const :format "DOS "
:sibling-args (:help-echo "\
Plain MS-DOS.")
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index bbe5f00fde1..392f8fafa79 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -4641,13 +4641,14 @@ DESC must be a `package-desc' object."
vars)
(dolist-with-progress-reporter (group custom-current-group-alist)
"Scanning for modified user options..."
- (dolist (ent (get (cdr group) 'custom-group))
- (when (and (custom-variable-p (car ent))
- (boundp (car ent))
- (not (eq (custom--standard-value (car ent))
- (default-toplevel-value (car ent))))
- (file-in-directory-p (car group) (package-desc-dir desc)))
- (push (car ent) vars))))
+ (when (and (car group)
+ (file-in-directory-p (car group) (package-desc-dir desc)))
+ (dolist (ent (get (cdr group) 'custom-group))
+ (when (and (custom-variable-p (car ent))
+ (boundp (car ent))
+ (not (eq (custom--standard-value (car ent))
+ (default-toplevel-value (car ent)))))
+ (push (car ent) vars)))))
(dlet ((reporter-prompt-for-summary-p t))
(reporter-submit-bug-report maint name vars))))
diff --git a/lisp/net/rcirc.el b/lisp/net/rcirc.el
index 0ee52d8ef6c..a6dad4b640d 100644
--- a/lisp/net/rcirc.el
+++ b/lisp/net/rcirc.el
@@ -2059,7 +2059,7 @@ connection."
(point-min)))
(when (let ((then (get-text-property (point) 'rcirc-time)))
(and then (not (time-less-p time then))))
- (next-single-property-change (point) 'hard)
+ (goto-char (next-single-property-change (point) 'hard))
(forward-char 1)
(throw 'exit nil))))
(goto-char (line-beginning-position))
diff --git a/src/nsfns.m b/src/nsfns.m
index 90159533128..2519f1ebac8 100644
--- a/src/nsfns.m
+++ b/src/nsfns.m
@@ -3840,7 +3840,13 @@ all_nonzero_ascii (unsigned char *str, ptrdiff_t n)
/* Make a Lisp string from an NSString. */
- (Lisp_Object)lispString
{
- return build_string ([self UTF8String]);
+ /* `make_string' creates a string with a given length, instead of
+ searching for a trailing NULL byte to determine its end. This is
+ important because this function is called to convert NSString
+ objects containing clipboard data, which can contain NUL bytes,
+ into Lisp strings. (bug#64697) */
+ return make_string ([self UTF8String],
+ [self lengthOfBytesUsingEncoding: NSUTF8StringEncoding]);
}
@end
diff --git a/src/xdisp.c b/src/xdisp.c
index 3728228c6de..da6e0afa8e1 100644
--- a/src/xdisp.c
+++ b/src/xdisp.c
@@ -21,17 +21,17 @@ along with GNU Emacs. If not, see
<https://www.gnu.org/licenses/>. */
Redisplay.
- Emacs separates the task of updating the display from code
- modifying global state, e.g. buffer text. This way functions
- operating on buffers don't also have to be concerned with updating
- the display.
-
- Updating the display is triggered by the Lisp interpreter when it
- decides it's time to do it. This is done either automatically for
- you as part of the interpreter's command loop or as the result of
- calling Lisp functions like `sit-for'. The C function
- `redisplay_internal' in xdisp.c is the only entry into the inner
- redisplay code.
+ Emacs separates the task of updating the display -- which we call
+ "redisplay" -- from the code modifying global state, e.g. buffer
+ text. This way functions operating on buffers don't also have to
+ be concerned with updating the display as result of their
+ operations.
+
+ Redisplay is triggered by the Lisp interpreter when it decides it's
+ time to do it. This is done either automatically for you as part
+ of the interpreter's command loop, or as the result of calling Lisp
+ functions like `sit-for'. The C function `redisplay_internal' in
+ xdisp.c is the only entry into the inner redisplay code.
The following diagram shows how redisplay code is invoked. As you
can see, Lisp calls redisplay and vice versa.
@@ -75,63 +75,97 @@ along with GNU Emacs. If not, see
<https://www.gnu.org/licenses/>. */
and to make these changes visible. Preferably it would do that in
a moderately intelligent way, i.e. fast.
- Changes in buffer text can be deduced from window and buffer
+ At its highest level, redisplay can be divided into 3 distinct
+ steps, all of which are visible in `redisplay_internal':
+
+ . decide which frames need their windows to be considered for redisplay
+ . for each window whose display might need to be updated, compute
+ a structure, called "glyph matrix", which describes how it
+ should look on display
+ . actually update the display of windows on the glass where the
+ newly obtained glyph matrix differs from the one produced by the
+ previous redisplay cycle
+
+ The first of these steps is done by `redisplay_internal' itself, by
+ looping through all the frames and testing their various flags,
+ such as their visibility. The result of this could be that only
+ the selected window on the selected frame must be redisplayed, or
+ it could conclude that other windows need to be considered as well.
+
+ The second step considers each window that might need to be
+ redisplayed. This could be only the selected window, or the window
+ trees of one or more frames. The function which considers a window
+ and decides whether it actually needs redisplay is
+ `redisplay_window'. It does so by looking at the changes in
+ position of point, in buffer text, in text properties, overlays,
+ etc. These changes can be deduced from window and buffer
structures, and from some global variables like `beg_unchanged' and
- `end_unchanged'. The contents of the display are additionally
- recorded in a `glyph matrix', a two-dimensional matrix of glyph
- structures. Each row in such a matrix corresponds to a line on the
- display, and each glyph in a row corresponds to a column displaying
- a character, an image, or what else. This matrix is called the
- `current glyph matrix' or `current matrix' in redisplay
- terminology.
-
- For buffer parts that have been changed since the last update, a
- second glyph matrix is constructed, the so called `desired glyph
- matrix' or short `desired matrix'. Current and desired matrix are
- then compared to find a cheap way to update the display, e.g. by
- reusing part of the display by scrolling lines. The actual update
- of the display of each window by comparing the desired and the
- current matrix is done by `update_window', which calls functions
- which draw to the glass (those functions are specific to the type
- of the window's frame: X, w32, NS, etc.).
+ `end_unchanged'. The current contents of the display are recorded
+ in a `glyph matrix', a two-dimensional matrix of glyph structures.
+ Each row in such a matrix corresponds to a line on the display, and
+ each glyph in a row corresponds to a column displaying a character,
+ an image, or what else. This matrix is called the `current glyph
+ matrix', or `current matrix', in redisplay terminology.
+
+ For buffer parts that have been changed since the last redisplay,
+ `redisplay_window' constructs a second glyph matrix, the so called
+ `desired glyph matrix' or short `desired matrix'. It does so in
+ the most optimal way possible, avoiding the examination of text
+ that didn't change, reusing portions of the current matrix if
+ possible, etc. It could, in particular, decide that a window
+ doesn't need to be redisplayed at all.
+
+ This second step of redisplay also updates the parts of the desired
+ matrix that correspond to the mode lines, header lines, and
+ tab-lines of the windows which need that; see `display_mode_lines'.
+
+ In the third and last step, the current and desired matrix are then
+ compared to find a cheap way to update the display, e.g. by reusing
+ part of the display by scrolling lines. The actual update of the
+ display of each window, by comparing the desired and the current
+ matrix, is done by `update_window', which calls functions which
+ draw to the glass (those functions are specific to the type of the
+ window's frame: X, w32, NS, etc.).
Once the display of a window on the glass has been updated, its
desired matrix is used to update the corresponding rows of the
current matrix, and then the desired matrix is discarded.
You will find a lot of redisplay optimizations when you start
- looking at the innards of redisplay. The overall goal of all these
- optimizations is to make redisplay fast because it is done
- frequently. Some of these optimizations are implemented by the
- following functions:
+ looking at the innards of `redisplay_window'. The overall goal of
+ all these optimizations is to make redisplay fast because it is
+ done frequently. Some of these optimizations are implemented by
+ the following functions:
. try_cursor_movement
- This function tries to update the display if the text in the
- window did not change and did not scroll, only point moved, and
- it did not move off the displayed portion of the text.
+ This optimization is applicable if the text in the window did
+ not change and did not scroll, only point moved, and it did not
+ move off the displayed portion of the text. In that case, the
+ window's glyph matrix is still valid, and only the position of
+ the cursor might need to be updated.
. try_window_reusing_current_matrix
- This function reuses the current matrix of a window when text
- has not changed, but the window start changed (e.g., due to
+ This function reuses the current glyph matrix of a window when
+ text has not changed, but the window start changed (e.g., due to
scrolling).
. try_window_id
- This function attempts to redisplay a window by reusing parts of
- its existing display. It finds and reuses the part that was not
- changed, and redraws the rest. (The "id" part in the function's
- name stands for "insert/delete", not for "identification" or
- somesuch.)
+ This function attempts to update a window's glyph matrix by
+ reusing parts of its current glyph matrix. It finds and reuses
+ the part that was not changed, and regenerates the rest. (The
+ "id" part in the function's name stands for "insert/delete", not
+ for "identification" or somesuch.)
. try_window
- This function performs the full, unoptimized, redisplay of a
- single window assuming that its fonts were not changed and that
- the cursor will not end up in the scroll margins. (Loading
- fonts requires re-adjustment of dimensions of glyph matrices,
- which makes this method impossible to use.)
+ This function performs the full, unoptimized, generation of a
+ single window's glyph matrix, assuming that its fonts were not
+ changed and that the cursor will not end up in the scroll
+ margins. (Loading fonts requires re-adjustment of dimensions of
+ glyph matrices, which makes this method impossible to use.)
The optimizations are tried in sequence (some can be skipped if
it is known that they are not applicable). If none of the
@@ -140,16 +174,17 @@ along with GNU Emacs. If not, see
<https://www.gnu.org/licenses/>. */
Note that there's one more important optimization up Emacs's
sleeve, but it is related to actually redrawing the potentially
- changed portions of the window/frame, not to reproducing the
- desired matrices of those potentially changed portions. Namely,
- the function update_frame and its subroutines, which you will find
- in dispnew.c, compare the desired matrices with the current
- matrices, and only redraw the portions that changed. So it could
- happen that the functions in this file for some reason decide that
- the entire desired matrix needs to be regenerated from scratch, and
- still only parts of the Emacs display, or even nothing at all, will
- be actually delivered to the glass, because update_frame has found
- that the new and the old screen contents are similar or identical.
+ changed portions of the window/frame as part of the third step, not
+ to generating the desired matrices of those potentially changed
+ portions. Namely, the function `update_frame' and its subroutines,
+ which you will find in dispnew.c, compare the desired matrices with
+ the current matrices, and only redraw the portions that changed.
+ So it could happen that the functions in this file for some reason
+ decide that the entire desired matrix needs to be regenerated from
+ scratch, and still only parts of the Emacs display, or even nothing
+ at all, will be actually delivered to the glass, because
+ `update_frame' has found that the new and the old screen contents
+ are similar or identical.
Desired matrices.
@@ -159,7 +194,7 @@ along with GNU Emacs. If not, see
<https://www.gnu.org/licenses/>. */
redisplay tries to optimize its work, and thus only generates
glyphs for rows that need to be updated on the screen. Rows that
don't need to be updated are left "disabled", and their contents
- should be ignored.
+ in the desired matrix should be ignored.
The function `display_line' is the central function to look at if
you are interested in how the rows of the desired matrix are