aboutsummaryrefslogtreecommitdiffstats
path: root/java
diff options
context:
space:
mode:
authorSpencer Baugh2025-06-19 17:20:12 -0400
committerEli Zaretskii2025-11-19 17:26:50 +0200
commit784d5b4954f7162c45ff7c265b11a30c1f260b8d (patch)
treefc3c69aeec738976af5fda100fbdbbd74f35374c /java
parent97d2ac4f95c02698e5d1145b4681b60b8bad6c78 (diff)
downloademacs-784d5b4954f7162c45ff7c265b11a30c1f260b8d.tar.gz
emacs-784d5b4954f7162c45ff7c265b11a30c1f260b8d.zip
Fix implicit usage of the current window-width in vtable.el
Previously, many functions in vtable.el called 'vtable--cache', which computed 'vtable--cache-key' based on the current selected window and frame; this could cause vtable functions to fail or misbehave if they were not called from the selected window and frame that 'vtable-insert' was last called in. Now, the vtable cache is stored with the text of the vtable, so that functions which need to interact with some vtable text can do so reliably without having to use the same selected window and frame. Also, 'vtable-update-object' has always required TABLE to be present at point in the current buffer; now its docstring states this. * lisp/emacs-lisp/vtable.el (vtable--current-cache) (vtable--cache-widths, vtable--cache-lines): Add. (vtable-insert): Save cache in 'vtable-cache. (vtable--ensure-cache, vtable--recompute-cache): Inline into 'vtable-insert'. (vtable--widths, vtable--cache): Delete. (vtable-update-object): Use 'vtable--current-cache' and update docstring. (Bug#69837) (vtable-remove-object, vtable-insert-object): Use 'vtable--current-cache' and save cache in 'vtable-cache'. (vtable--sort, vtable--alter-column-width) (vtable-previous-column, vtable-next-column): Use 'vtable--current-cache'.
Diffstat (limited to 'java')
0 files changed, 0 insertions, 0 deletions