Permalink
Commits on May 18, 2015
  1. Merge branch 'remove-no-dups' of https://github.com/T-J-Teru/browse-k…

    T-J-Teru committed May 18, 2015
    …ill-ring into T-J-Teru-remove-no-dups
Commits on May 5, 2015
  1. Merge pull request #51 from T-J-Teru/bkr-error

    T-J-Teru committed May 5, 2015
    Reorder `browse-kill-ring` and use error not message.
Commits on Apr 29, 2015
  1. Reorder `browse-kill-ring` and use error not message.

    T-J-Teru committed Apr 22, 2015
    Using `browse-kill-ring` when already in the kill ring buffer now gives
    and error.
    Unnest code within `browse-kill-ring` now that `error` will raise an
    exception.
  2. Remove browse-kill-ring-no-duplicates.

    T-J-Teru committed Apr 27, 2015
    The browse-kill-ring-no-duplicates functionality is not related to
    browsing the kill-ring, but is instead about controlling what is placed
    in to the kill-ring.
    
    This functionality, if it is wanted at all, should be moved into a new
    package, the browse-kill-ring package should focus on its core task.
Commits on Jan 4, 2015
  1. Merge pull request #48 from T-J-Teru/after-edit-handling

    T-J-Teru committed Jan 4, 2015
    Unify common code after `browse-kill-ring-edit'.
Commits on Jan 2, 2015
  1. Unify common code after `browse-kill-ring-edit'.

    T-J-Teru committed Jan 2, 2015
    This patch unifies common code from `browse-kill-ring-finish' and
    `browse-kill-ring-abort', and adds protection so that we only kill the
    edit buffer if it's in the correct mode (so we can be reasonably sure
    that it really is the edit buffer).
    
    I've made the `browse-kill-ring-edit-target' variable track when the
    user is editing an entry in the `kill-ring', resetting it's value to nil
    after the edit is complete.  The variable can then now be used to tell
    if calling `browse-kill-ring-edit-finish' is correct or not.
Commits on Nov 4, 2014
  1. Bump to version 2.0

    To1ne committed Nov 4, 2014
Commits on Oct 3, 2014
  1. Merge pull request #47 from T-J-Teru/linum-fix

    T-J-Teru committed Oct 3, 2014
    Support non browse-kill-ring overlays in the *Kill Ring* buffer.
Commits on Sep 26, 2014
  1. Update -search-forward to use -target-overlay-at.

    T-J-Teru committed Sep 26, 2014
    Update browse-kill-ring-search-forward to use
    browse-kill-ring-target-overlay-at rather than overlays-at so that we
    can support non browse-kill-ring overlays existing in the *Kill Ring*
    buffer.
  2. Handle non browse-kill-ring overlays during item highlight.

    T-J-Teru committed Sep 26, 2014
    Use browse-kill-ring-target-overlay-at rather than overlays-at to allow
    for non browse-kill-ring overlays that might exist in the *Kill Ring*
    buffer.
  3. Update -edit to use -target-overlay-at not overlays-at.

    T-J-Teru committed Sep 26, 2014
    This enables browse-kill-ring to handle the situation where there are
    overlays active in the *Kill Ring* buffer that are not from
    browse-kill-ring.
  4. Update -forward to use -target-overlay-at not overlays-at.

    T-J-Teru committed Sep 26, 2014
    This enables the code to handle the case where there are other, non
    browse-kill-ring, overlays active in the *Kill Ring* buffer.
  5. Change -current-index to use -target-overlay-at.

    T-J-Teru committed Sep 26, 2014
    Should better handle the case where there are other overlays active in
    the browse-kill-ring buffer.
  6. Use -target-overlay-at for -current-string.

    T-J-Teru committed Sep 26, 2014
    Code reuse, there's now a common piece of code that looks for suitable
    overlays at a position, lets use it where we can.
  7. Make error optional in browse-kill-ring-target-overlay-at.

    T-J-Teru committed Sep 26, 2014
    Allow this function to return nil in the case where there's no suitable
    overlay at POSITION.
Commits on Sep 15, 2014
  1. Merge branch 'edit-delete-empty-v4' of github.com:T-J-Teru/browse-kil…

    T-J-Teru committed Sep 15, 2014
    …l-ring into T-J-Teru-edit-delete-empty-v4
Commits on Sep 14, 2014
  1. Merge pull request #43 from T-J-Teru/inhibit-read-ony

    glasserc committed Sep 14, 2014
    Inhibit read only before deleting Kill Ring entries.
Commits on Sep 12, 2014
  1. Delete items that are edited to the empty string.

    T-J-Teru committed Sep 12, 2014
    When using the edit feature of browse-kill-ring, if an item is edited to
    the empty string then it is deleted from the `kill-ring'.  Care is taken
    to ensure that the correct entry is reselected after the delete in order
    to give the same user experience as if the user had just chosen to
    delete the item from the kill-ring with browse-kill-ring-delete.
Commits on Sep 11, 2014
  1. Inhibit read only before deleting Kill Ring entries.

    T-J-Teru committed Sep 11, 2014
    This fix is from http://bugs.debian.org/224751.  Disable all read only
    properties before trying to delete an entry from the *Kill Ring*
    buffer.
Commits on Sep 7, 2014
  1. Fix bug in browse-kill-ring-occur.

    T-J-Teru committed Sep 7, 2014
    The parameters to browse-kill-ring-setup have changed at some point in
    the past, and browse-kill-ring-occur had not been update to the new
    usage, with the result that browse-kill-ring-occur no longer worked.
    Fixed in this commit, brings use of browse-kill-ring-setup up to date.
    
    ChangeLog:
    
    	Fix bug in `browse-kill-ring-occur' due to change in parameters of
    	`browse-kill-ring-setup'.
  2. Merge branch 'early-quit-v2' of github.com:T-J-Teru/browse-kill-ring …

    T-J-Teru committed Sep 7, 2014
    …into T-J-Teru-early-quit-v2
Commits on Sep 6, 2014
  1. Merge branch 'cleanup-on-kill' of github.com:T-J-Teru/browse-kill-rin…

    T-J-Teru committed Sep 6, 2014
    …g into T-J-Teru-cleanup-on-kill
Commits on Sep 3, 2014
  1. Perform the quit action earlier.

    T-J-Teru committed Aug 25, 2014
    Previously the `*Kill-Ring*' buffer is only closed after the item has
    been inserted and the highlighting has finished (if highlighting of the
    inserted item is turned on), this takes 0.5 seconds, and gives a user
    experience that appears unresponsive.
    
    After this patch when the user asks for insert and exit, we first
    establish what will be inserted, then we close the `*Kill Ring*' buffer,
    and then we insert and highlight the item.  This gives a much more
    responsive user experience.
  2. Merge branch 'hide-preview-v2' of github.com:T-J-Teru/browse-kill-rin…

    T-J-Teru committed Sep 3, 2014
    …g into T-J-Teru-hide-preview-v2
  3. Use a kill-buffer-hook to ensure that the preview is removed.

    T-J-Teru committed Sep 3, 2014
    Previously, if the `*Kill Ring*' buffer is killed in by calling
    `kill-buffer' directly, rather than `browse-kill-ring-quit' then the
    preview is left active.  After this patch the preview will be removed
    even in this case.
  4. Merge branch 'edit-with-preview-v2' of github.com:T-J-Teru/browse-kil…

    T-J-Teru committed Sep 3, 2014
    …l-ring into T-J-Teru-edit-with-preview-v2
  5. Merge branch 'delete-last' of github.com:T-J-Teru/browse-kill-ring in…

    T-J-Teru committed Sep 3, 2014
    …to T-J-Teru-delete-last
  6. Merge pull request #38 from T-J-Teru/select-after-edit-v2

    T-J-Teru committed Sep 3, 2014
    Reselect `kill-ring` item after editing.