Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Undo buffer limit exceeded #26

Open
DonyorM opened this issue Mar 15, 2017 · 4 comments
Open

Undo buffer limit exceeded #26

DonyorM opened this issue Mar 15, 2017 · 4 comments
Labels
Emacs Emacs client related issue

Comments

@DonyorM
Copy link

DonyorM commented Mar 15, 2017

I have been doing an inner trace on a recursive function, and thus generating a very large workspace buffer. I've been getting this error basically whenever I did something.

Warning (undo): Buffer `*sayid*' undo info was 21192348 bytes long.
The undo info was discarded because it exceeded `undo-outer-limit'.

This is normal if you executed a command that made a huge change
to the buffer.  In that case, to prevent similar problems in the
future, set `undo-outer-limit' to a value that is large enough to
cover the maximum size of normal changes you expect a single
command to make, but not so large that it might exceed the
maximum memory allotted to Emacs.

If you did not execute any such command, the situation is
probably due to a bug and you should report it.

You can disable the popping up of this buffer by adding the entry
(undo discard-info) to the user option `warning-suppress-types',
which is defined in the `warnings' library.

I don't know if sayid needs the undo buffer, so if it doesn't, we could consider removing it to avoid the issue. Otherwise, users need to set their limit higher.

@bpiel
Copy link
Collaborator

bpiel commented Mar 15, 2017

Sayid shouldn't need any undo info. I'll fix that. thanks

@bpiel
Copy link
Collaborator

bpiel commented May 1, 2017

Should be fixed in next release
c452b09

@bpiel
Copy link
Collaborator

bpiel commented May 3, 2017

v0.0.15 is out with a fix for this. I didn't actually get around to testing though. If this is still happening, I'd really appreciate a note here.

@bpiel
Copy link
Collaborator

bpiel commented May 3, 2017

Nope, that didn't work. This is still a bug.

@bbatsov bbatsov added the Emacs Emacs client related issue label Aug 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Emacs Emacs client related issue
Projects
None yet
Development

No branches or pull requests

3 participants