> > I've solved 1 and 2.
> > You can force rebuild archive-tree by C-u tab.
>
> Good idea also. Perhaps more intuitive than my C-r binding.
You bind C-r to tla--name-read-refresh-cache.
Is the behavior of tla--name-read-refresh-cache different
from passing nil as USE-CACHE to tla--archive-tree-build-revisions?
BTW, tla--name-read-minibuf-map may be useful for the future extension.
> > To avoid confusion, I have not commit my modification to my tree.
>
> Ooops, I'm really sorry : I had read your message too quickly and
> didn't understand that you actually wrote some code.
No problem. One more request is that the indicator; during rebuilding
archive-tree, it should be reported to the user by using `message'.
This is an example.
(defun tla--name-read-refresh-cache ()
"Function to be called from the minibuffer while reading a name."
(interactive)
(message "rebuild cache for \"%s\"..." (minibuffer-contents))
(tla--archive-tree-build
(tla--name-construct
(butlast (delete nil (tla--name-split (minibuffer-contents))))))
(message "rebuild cache for \"%s\"...done" (minibuffer-contents))
(sit-for 0)
(message nil)
(setq tla--archive-tree nil))
Your code is good enough. I'd like you to move the code in xtla-read-moy.el to
xtla-core.el; and remove xtla-read.el and xtla-read-moy.el.
It is time to make tla--read-archive-*-name funcitons retire.
Masatake YAMATO
