Slawomir Grochowski <[email protected]> writes: >>> + (setq-local org-columns-global (not local)) >>> + (let* ((rows (save-excursion >>> + (org-columns--prepare-rows (not local) columns-format))) >>> + (has-item (assoc "ITEM" org-columns-current-fmt-compiled)) >>> + table) >>> + (goto-char org-columns-top-level-marker) > >> You moved goto-char *after* columns computation "(not local)". Not sure >> if this is right. > > The old code did not move to `org-columns-top-level-marker' before > computing columns either. It first called `org-columns', and > `org-columns' computed the scope and set `org-columns-top-level-marker'. > Only after that did `org-columns--capture-view' move to the marker.
Then, why is that goto-char necessary at all? org-map-entries will map over the narrowed portion of the buffer. It does not matter where the point position is. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
