On 2021-02-06 2:08 p.m., Bart Schaefer wrote:
You know, when one understands the logic of the thing, the problem isn't even a problem anymore. Still, hitting the up arrow is doing something is it not? Hitting it the second time updates fine. '$ history' is up to the second so why couldn't the up arrow check the same up to date history list before giving you a line rather than after? Ultimate small issue tho.The issue here is that when sitting at a prompt, zsh is (usually) doing literally nothing. It can't discover that the history file has changed until you unblock it by doing something, and it doesn't update the shared history until the current local history is ready to be written.