1. 29 Sep, 1992 11 commits
    • Jim Blandy's avatar
      *** empty log message *** · 960fa1fa
      Jim Blandy authored
      960fa1fa
    • Jim Blandy's avatar
      * xterm.h (ROOT_WINDOW): Use the DefaultScreen macro, not the · bbe42033
      Jim Blandy authored
      	XDefaultScreen function.
      bbe42033
    • Jim Blandy's avatar
      *** empty log message *** · 11270fa7
      Jim Blandy authored
      11270fa7
    • Jim Blandy's avatar
      * gud.el: When we send a command to the debugger via gud-call, · 53eb3a97
      Jim Blandy authored
      	it's annoying to see the command and the new prompt in the
      	debugger interaction buffer; nuke the command and the old prompt.
      	(gud-delete-prompt-marker): New variable, with extensive documentation.
      	(gud-mode): Make gud-delete-prompt-marker buffer-local, and
      	initialize it.
      	(gud-filter-insert): If gud-delete-prompt-marker is set, delete
      	the prompt, and clear gud-delete-prompt-marker.
      	(gud-call): Arrange for the last prompt printed to get deleted, by
      	setting gud-delete-prompt-char.
      53eb3a97
    • Jim Blandy's avatar
      * gud.el (gud-def): Doc fix. · 6bde8427
      Jim Blandy authored
      	(gud-gdb-marker-filter, gud-sdb-marker-filter,
      	gud-dbx-marker-filter): Rename the argument `s' or `str' to
      	`string', and change all uses; these definitions were referring to
      	`string', which is unbound in the lexical context, but which
      	happens to end up being bound to the right thing by the caller,
      	gud-filter.
      	(sdb): Set comint-prompt-regexp, not comint-prompt-pattern; the
      	latter doesn't exist.
      	(gud-dbx-debugger-setup): Use the argument `f', not the variable
      	`file', which happens to be bound in the caller.
      	(gud-filter-insert): The variable `start' is never used.  The
      	variable `moving' is unnecessary.  The variable `old-buffer' and
      	the unwind-protect form are unneeded, since save-excursion can do
      	their work.  The binding of output-after-point should be done after
      	switching to the process's buffer, not in whatever random buffer
      	happens to be current when the process filter is called.  There's
      	no need to set the process mark if we've just inserted at its
      	location using insert-before-markers.
      	(gud-read-address): Don't bother setting the variable `result'; it
      	is never used.
      
      	* gud.el (gud-mode-map): Bind gud-refresh to C-c C-l, not C-c l;
      	the latter is reserved for the user's purposes.
      
      	* gud.el (gdb, sdb, dbx): Use C-c C-r ("resume") for continuing,
      	instead of C-c C-c.  C-c C-c should be comint-interrupt-subjob;
      	it's important to have that available, and the C-c C-c binding is
      	consistent with all the other comint-derived modes.
      6bde8427
    • Jim Blandy's avatar
      * editfns.c (save_excursion_save, save_excursion_restore): · 0e2c9c70
      Jim Blandy authored
      	Formatting tweaked for readability.
      0e2c9c70
    • Jim Blandy's avatar
      * data.c (Frem): Use the `fmod' function under SunOS, Ultrix, and · a080486e
      Jim Blandy authored
      	HP/UX, not just under USG systems.
      a080486e
    • Jim Blandy's avatar
      * buffer.c (Fbury_buffer): This used to undisplay the buffer being · b271272a
      Jim Blandy authored
      	buried only if the BUFFER argument was nil.  Instead, undisplay the
      	buffer whenever it's displayed in the selected window, no matter
      	how it was specified by BUFFER.  This is how it behaves in 18.58,
      	and I can't find any ChangeLog entry in 18.58 or 19.0 saying why
      	they differ.  Fix the doc string accordingly.
      b271272a
    • Jim Blandy's avatar
      * frame.c (Fselect_frame, Fframe_root_window, · 8693ca83
      Jim Blandy authored
      	Fframe_selected_window, Fnext_frame, Fmake_frame_visible,
      	Fmake_frame_invisible, Ficonify_frame): Doc fixes.
      8693ca83
    • Jim Blandy's avatar
      entered into RCS · 30e4c427
      Jim Blandy authored
      30e4c427
    • Jim Blandy's avatar
      * ralloc.c: Since the users of the relocating allocation code · 98b7fe02
      Jim Blandy authored
      	handle memory exhaustion, it's better to return an error code to
      	them than to call abort.
      	(obtain): If we cannot allocate more memory, don't call
      	abort.  Instead, return non-zero iff the allocation is successful.
      	(get_more_space): If obtain fails, return zero.
      	(get_bloc): Return zero if we can't allocate the new bloc.
      	(r_alloc_sbrk): Return zero if we can't allocate more memory.
      	(r_alloc): If we can't allocate more memory, set *PTR to zero and
      	return zero.
      	(r_re_alloc): If we can't allocate more memory, leave *PTR
      	unchanged, and return zero.
      
      	* ralloc.c (warnfunction): Renamed to warn_function; users changed.
      98b7fe02
  2. 28 Sep, 1992 14 commits
  3. 27 Sep, 1992 11 commits
  4. 26 Sep, 1992 4 commits