Skip to Content
Bloggit log ate the stack trace

git log ate the stack. The history is still there

You copied the traceback. Your fingers were faster than the thought, and git log ran again.

The system clipboard keeps one payload. The stack still flashed on screen. It is no longer what paste will insert. You do not need a new abbreviation. You need the copy you already made.

CodeExpander’s clipboard history is its own window, and it is Pro. It stores a configurable recent list — a hundred items by default — across text, HTML, RTF, images, and file paths. Filter by type, search the body, star what you cannot afford to lose, click a row to paste into whatever still has focus. Capture, annotate, and OCR are a different path; that article is Capture, annotate, OCR. This one is only retrieval.

Search clipboard…
*AllTextImage
  • CE-xxxx-xxxx-xxxx
    Text · license
    just now
  • https://codeexpander.com
    Text · URL
    2 min ago
  • error.png
    Image · 1280×800
    10 min ago

Clipboard history: filter, search, click to paste. Does not steal focus from the app you are typing in.

Open the window, then click the row

If the main window is running, history is already being recorded. You do not have to open the panel first. Open it from the tray, from Settings → Clipboard, or from the global shortcut you assigned.

  1. Copy the stack, the token, the reply you will need twice.
  2. Do the next thing. Let the system clipboard move on.
  3. Open history, search a few characters if the list is long, click the row. It pastes into the field that still has focus.

On Windows the panel can stay on top, and the arrow keys still move the list without clicking into the search box first. Showing the window does not steal the editor you were typing in.

Paste without formatting strips a rich payload down to characters. Oversized items can be skipped with a size cap. Old rows can age out on a day limit. Starred rows stay when later copies would have pushed them off. A note on a row helps next week, when a string of digits no longer explains itself. All of that is Settings → Clipboard.

The system clipboard is still one layer. The history window is a list beside it, not infinite undo for paste. Clicking a row is what makes that payload current again.

This is not system-wide expand

Expansion is the signature loop: abbreviation in any focused field, trigger key, body replaces the short text. The history window does not do that. It does not read abbreviations, it does not edit the snippet library, and it does not turn a copy into a snippet by itself.

If this stack should become a template you can expand later, that is a separate “create from clipboard” step. Do not merge retrieve and replace. History finds. Expand substitutes.

The list stays on this computer. It is not uploaded to CE Cloud or Gist. A key or an internal URL you copied does not leave the machine because the window is open. Sync is still the switch you turn on elsewhere, on purpose.

Do not

  • Do not treat history as a second expander. If you forgot the abbreviation, type // or open the search window. Do not scroll copies hoping one of them is the template.
  • Do not treat it as a cloud clipboard. Power this machine off and the list is not on the next one.
  • Free tier does not include the window. Copy less over yourself, or see Pricing.

Related: Clipboard, Capture, annotate, OCR.

Last updated