# The Basis 108 was a Apple II clone, manufactured by the "Basis
# Mikrocomputer GmbH" in Munster, Germany (the company still exists today,
# about 1,5 km from where I live, but doesn't build own computers any
-# more). A Basis 108 featured a really heavy (cast aluminium?) case, was
+# more). A Basis 108 featured a really heavy (cast aluminum?) case, was
# equipped with one or two 5.25" disk drives, had a monochrome and colour
# video output for a TV set or a dedicated monitor and several slots for
# Apple II cards. Basis 108 were quite popular at german schools before
;; You might make extra input sequences on the basis of the X
;; locale/*/Compose files (which have both prefix and postfix
;; sequences), but bear in mind that sequences which are logical in
-;; that context may not be sensible when they're not signalled with
+;; that context may not be sensible when they're not signaled with
;; the Compose key. An example is a double space for NBSP.
;;; Code:
(gud-watch, gdb-var-create-handler): Display function::var format
but don't use to create variable object.
(gdb-var-create-handler): Use message-box in place of message.
- (gdb-stopped): Call gdb-exited if signalled.
+ (gdb-stopped): Call gdb-exited if signaled.
2006-02-22 Carsten Dominik <dominik@science.uva.nl>
* doc-view.el (doc-view-scroll-up-or-next-page)
(doc-view-scroll-down-or-previous-page): Use image-scroll-up and
image-scroll-down instead of the non-image equivalents.
- Don't rely on a signalled condition but switch pages when scrolling
+ Don't rely on a signaled condition but switch pages when scrolling
doesn't change the vertical position anymore.
(doc-view-mode-map): Remap scroll-{up,down} to
image-scroll-{up,down}.
branch and removes any locks that might remain after check-in.
(vc-cancel-version): Abort with error message in the CVS case.
- (The error used to be signalled in vc-backend-uncheck, which is
+ (The error used to be signaled in vc-backend-uncheck, which is
a little too late.)
(vc-minor-revision): Function removed.
2000-10-19 Jason Rumney <jasonr@gnu.org>
- * dired.el (dired-insert-directory): Do not let errors signalled by
+ * dired.el (dired-insert-directory): Do not let errors signaled by
attempt to run dired-free-space-program prevent dired from working.
2000-10-19 Stefan Monnier <monnier@cs.yale.edu>
;; you can give a numeric prefix argument specifying the number of
;; times to repeat the macro. Macro execution automatically
;; terminates when point reaches the end of the buffer or if an error
-;; is signalled by ringing the bell.
+;; is signaled by ringing the bell.
;; When you define a macro with F3/F4, it is automatically added to
;; the head of the "keyboard macro ring", and F4 actually executes the
;; If the first scroll succeeded, then some scrolling
;; is possible: keep scrolling til the beginning but
;; do not signal an error. For some reason, we have
- ;; to do it even if the first scroll signalled an
+ ;; to do it even if the first scroll signaled an
;; error, because otherwise the window is recentered
;; for a reason that escapes me. This problem seems
;; to only affect scroll-down. --Stef
;; We handle here all file primitives. Most of them have the file
;; name as first parameter; nevertheless we check for them explicitly
-;; in order to be signalled if a new primitive appears. This
+;; in order to be signaled if a new primitive appears. This
;; scenario is needed because there isn't a way to decide by
;; syntactical means whether a foreign method must be called. It would
;; ease the life if `file-name-handler-alist' would support a decision
(let ((rng-dt-namespace-context-getter '(nxml-ns-get-context)))
(nxml-with-unmodifying-text-property-changes
(rng-do-some-validation-1 continue-p-function))))
- ;; errors signalled from a function run by an idle timer
+ ;; errors signaled from a function run by an idle timer
;; are ignored; if we don't catch them, validation
;; will get mysteriously stuck at a single place
(rng-compile-error
"Run BODY and demote any errors to simple messages.
If `debug-on-error' is non-nil, run BODY without catching its errors.
This is to be used around code which is not expected to signal an error
-but which should be robust in the unexpected case that an error is signalled."
+but which should be robust in the unexpected case that an error is signaled."
(declare (debug t) (indent 0))
(let ((err (make-symbol "err")))
`(condition-case-no-debug ,err
;;; url-gw.el --- Gateway munging for URL loading
-;; Copyright (C) 1997, 1998, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
+;; Copyright (C) 1997, 1998, 2004, 2005, 2006, 2007, 2008
+;; Free Software Foundation, Inc.
;; Author: Bill Perry <wmperry@gnu.org>
;; Keywords: comm, data, processes
(error "Bad setting of url-gateway-method: %s"
url-gateway-method)))))
;; Ignoring errors here seems wrong. E.g. it'll throw away the
- ;; error signalled two lines above. It was also found inconvenient
+ ;; error signaled two lines above. It was also found inconvenient
;; during debugging.
;; (error
;; (setq conn nil))
is non-nil it is silently bashed; else if the function was
called interactively the user is queried as to whether s/he
wants to bash the file; otherwise (ok-if-exists nil, non-interactive)
- a file-already-exists error is signalled.
+ a file-already-exists error is signaled.
* window.c: Made get-window-buffer return nil if get-buffer of
its arg returns nil, rather than erring.
* editfns.c (Fchar_after, Fchar_before): Doc fix.
* bytecode.c (Fbyte_code): Use {BEFORE,AFTER}_POTENTIAL_GC where
- an error may be signalled.
+ an error may be signaled.
2000-01-26 Gerd Moellmann <gerd@gnu.org>
else
/* An unknown pseudovector may contain non-Lisp fields, so we
can't just blindly traverse all its fields. We used to call
- `Flength' which signalled `sequencep', so I just preserved this
+ `Flength' which signaled `sequencep', so I just preserved this
behavior. */
wrong_type_argument (Qsequencep, subtree);
/* Parse network options in the arg list.
We simply ignore anything which isn't a known option (including other keywords).
- An error is signalled if setting a known option fails. */
+ An error is signaled if setting a known option fails. */
for (optn = optbits = 0; optn < nargs-1; optn += 2)
optbits |= set_socket_option (s, args[optn], args[optn+1]);
/* Thread proc for child process and socket reader threads. Each thread
is normally blocked until woken by select() to check for input by
- reading one char. When the read completes, char_avail is signalled
+ reading one char. When the read completes, char_avail is signaled
to wake up the select emulator and the thread blocks itself again. */
DWORD WINAPI
reader_thread (void *arg)
To reduce the number of places in which Emacs can be hung such that
C-g is not able to interrupt it, we always wait on interrupt_handle
- (which is signalled by the input thread when C-g is detected). If we
+ (which is signaled by the input thread when C-g is detected). If we
detect that we were woken up by C-g, we return -1 with errno set to
EINTR as on Unix. */
current_status = cp->status;
if (WaitForSingleObject (cp->char_avail, 0) == WAIT_OBJECT_0)
{
- /* char_avail has been signalled, so status (which may
+ /* char_avail has been signaled, so status (which may
have changed) should indicate read has completed
but has not been acknowledged. */
current_status = cp->status;
}
else
{
- /* char_avail has not been signalled, so status should
+ /* char_avail has not been signaled, so status should
indicate that read is in progress; small possibility
- that read has completed but event wasn't yet signalled
+ that read has completed but event wasn't yet signaled
when we tested it (because a context switch occurred
or if running on separate CPUs). */
if (current_status != STATUS_READ_READY
start_time = GetTickCount ();
- /* Wait for input or child death to be signalled. If user input is
+ /* Wait for input or child death to be signaled. If user input is
allowed, then also accept window messages. */
if (FD_ISSET (0, &orfds))
active = MsgWaitForMultipleObjects (nh + nc, wait_hnd, FALSE, timeout_ms,
abort ();
/* Loop over all handles after active (now officially documented as
- being the first signalled handle in the array). We do this to
+ being the first signaled handle in the array). We do this to
ensure fairness, so that all channels with data available will be
processed - otherwise higher numbered channels could be starved. */
do
when the input queue is empty, so make it a manual reset event. */
keyboard_handle = input_available = CreateEvent (NULL, TRUE, FALSE, NULL);
- /* interrupt_handle is signalled when quit (C-g) is detected, so that
+ /* interrupt_handle is signaled when quit (C-g) is detected, so that
blocking system calls can be interrupted. We make it a manual
reset event, so that if we should ever have multiple threads
performing system calls, they will all be interrupted (I'm guessing
that would the right response). Note that we use PulseEvent to
- signal this event, so that it never remains signalled. */
+ signal this event, so that it never remains signaled. */
interrupt_handle = CreateEvent (NULL, TRUE, FALSE, NULL);
}
void
signal_quit ()
{
- /* Make sure this event never remains signalled; if the main thread
+ /* Make sure this event never remains signaled; if the main thread
isn't in a blocking call, then this should do nothing. */
PulseEvent (interrupt_handle);
}
The number of children n equals the number of resizable
children of this window + 1 because we know window itself
- is resizable (otherwise we would have signalled an error).
+ is resizable (otherwise we would have signaled an error).
This reasoning is not correct when other windows become too
small and shrink_windows refuses to delete them. Below we
projects / emacs.git / commitdiff