2015-08-07 Phillip Lord <phillip.lord@newcastle.ac.uk>
- Improve error signalling for seq-subseq
+ Improve error signaling for seq-subseq
* lisp/emacs-lisp/seq.el (seq-subseq): The existing behavior is to error
when indexes are too large, but to silently ignore numbers which
are too negative for lists. String and vector handling errors in
On MS-Windows the @var{noactivate} argument has no effect. However, if
@var{frame} is a child frame (@pxref{Child Frames}), this function
-usualy does focus @var{frame} without raising it above other child
+usually focuses @var{frame} without raising it above other child
frames.
If there is no window system support, this function does nothing.
child and a parent frame. Also, the relative roles of child and parent
frame may be reversed at any time (though it's usually a good idea to
keep the size of child frames sufficiently smaller than that of their
-parent). An error will be signalled for the attempt to make a frame an
+parent). An error will be signaled for the attempt to make a frame an
ancestor of itself.
A child frame is clipped at the native edges (@pxref{Frame Geometry})
(erase-buffer)
(call-process-shell-command command nil t)
;; FIXME: What to do when the call fails?
- ;; "find: ‘zzgrep’: No such file or directory\n"
+ ;; "find: ‘foo’: No such file or directory\n"
;; The problem is, find-grep can exit with a nonzero code even
;; when there are some matches in the output.
(goto-char (point-min))
* value to be returned. In that latter case IGNORE is ignored.
*
* If `frame-windows-min-size' is called, it will make sure that the
- * return value accomodates all windows of FRAME respecting the values
+ * return value accommodates all windows of FRAME respecting the values
* of `window-min-height' (`window-min-width' if HORIZONTAL is non-nil).
* With IGNORE non-nil the values of these variables are ignored.
*
}
}
- /* Check these parameters for circular dependeny. This does not check
- for interdependencies between these properties. Hence you can
+ /* Check each parent-frame and delete-before parameter for a
+ circular dependency. Do not check between parameters, so you can
still create circular dependencies with different properties, for
example a chain of frames F1->F2->...Fn such that F1 is an ancestor
frame of Fn and thus cannot be deleted before Fn and a second chain
if (FRAME_GTK_WIDGET (f))
{
GtkWindow *gwin = GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f));
- gboolean gno_focus_on_map = NILP (no_focus_on_map) ? TRUE : FALSE;
+ gboolean g_no_focus_on_map = NILP (no_focus_on_map) ? TRUE : FALSE;
- gtk_window_set_focus_on_map (gwin, gno_focus_on_map);
+ gtk_window_set_focus_on_map (gwin, g_no_focus_on_map);
}
unblock_input ();
}
if (FRAME_GTK_WIDGET (f))
{
GtkWindow *gwin = GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f));
- gboolean gno_accept_focus = NILP (no_accept_focus) ? TRUE : FALSE;
+ gboolean g_no_accept_focus = NILP (no_accept_focus) ? TRUE : FALSE;
- gtk_window_set_accept_focus (gwin, gno_accept_focus);
+ gtk_window_set_accept_focus (gwin, g_no_accept_focus);
}
unblock_input ();
}
hints.decorations = NILP (new_value) ? MWM_DECOR_ALL : 0;
block_input ();
- /* For some reason the third and fourth argument in the following
- call must be identic: In the corresponding XGetWindowProperty
- call in getMotifHints, xfwm has the third and seventh arg both
+ /* For some reason the third and fourth arguments in the following
+ call must be identical: In the corresponding XGetWindowProperty
+ call in getMotifHints, xfwm has the third and seventh args both
display_info->atoms[MOTIF_WM_HINTS]. Obviously, YMMV. */
XChangeProperty (dpy, FRAME_OUTER_WINDOW (f), prop, prop, 32,
PropModeReplace, (unsigned char *) &hints,
hints.flags = MWM_HINTS_DECORATIONS;
hints.decorations = 0;
- /* For some reason the third and fourth argument in the following
- call must be identic: In the corresponding XGetWindowProperty
- call in getMotifHints, xfwm has the third and seventh arg both
+ /* For some reason the third and fourth arguments in the following
+ call must be identical: In the corresponding XGetWindowProperty
+ call in getMotifHints, xfwm has the third and seventh args both
display_info->atoms[MOTIF_WM_HINTS]. Obviously, YMMV. */
XChangeProperty (dpy, FRAME_OUTER_WINDOW (f), prop, prop, 32,
PropModeReplace, (unsigned char *) &hints,
hints.flags = MWM_HINTS_DECORATIONS;
hints.decorations = 0;
- /* For some reason the third and fourth argument in the following
- call must be identic: In the corresponding XGetWindowProperty
- call in getMotifHints, xfwm has the third and seventh arg both
+ /* For some reason the third and fourth arguments in the following
+ call must be identical: In the corresponding XGetWindowProperty
+ call in getMotifHints, xfwm has the third and seventh args both
display_info->atoms[MOTIF_WM_HINTS]. Obviously, YMMV. */
XChangeProperty (dpy, FRAME_OUTER_WINDOW (f), prop, prop, 32,
PropModeReplace, (unsigned char *) &hints,