mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-02-16 17:24:23 +00:00
; Rework documentation for diff-delete-other-hunks
This commit is contained in:
parent
c8ecd7fa0d
commit
11e7aa75ee
2 changed files with 11 additions and 6 deletions
|
|
@ -1705,8 +1705,11 @@ diffs were applied successfully, save the changed buffers.
|
|||
|
||||
@findex diff-delete-other-hunks
|
||||
@item C-c @key{RET} n
|
||||
Delete all hunks other than the current hunk. If the region is active,
|
||||
then delete all hunks that the region does not overlap.
|
||||
Delete hunks other than the current one. If the region is active, this
|
||||
command deletes the hunks the region overlaps; otherwise it deletes all
|
||||
hunks other than the current hunk. This command does not work in a
|
||||
narrowed buffer because deleting hunks safely requires access to the
|
||||
file headers.
|
||||
|
||||
@findex diff-refine-hunk
|
||||
@item C-c C-b
|
||||
|
|
|
|||
|
|
@ -822,10 +822,12 @@ If the prefix ARG is given, restrict the view to the current file instead."
|
|||
;; would be a patch with the same meaning. That is not implemented
|
||||
;; because it does not seem like it would be useful.
|
||||
(defun diff-delete-other-hunks (&optional beg end)
|
||||
"Delete all hunks other than the current hunk.
|
||||
Interactively, if the region is active, then delete all hunks that the
|
||||
region does not overlap. When called from Lisp, the optional arguments
|
||||
BEG and END specify the region of hunks not to delete."
|
||||
"Delete hunks other than the current one.
|
||||
Interactively, if the region is active, delete all hunks that the region
|
||||
overlaps; otherwise delete all hunks except the current one.
|
||||
When calling from Lisp, pass BEG and END as the bounds of the region in
|
||||
which to delete hunks; BEG and END omitted or nil means to delete all
|
||||
the hunks but the one which contains point."
|
||||
(interactive (list (use-region-beginning) (use-region-end)))
|
||||
(when (buffer-narrowed-p)
|
||||
(user-error "Command is not safe in a narrowed buffer"))
|
||||
|
|
|
|||
Loading…
Reference in a new issue