Buffer created but why movement command of function ignored?

Buffer created but why movement command of function ignored?

[Chris Seberino]

When I run this function the ansi-term is created but the point
does NOT move to beginning of buffer.  Why?

(global-set-key (kbd "M-l")       (lambda () (interactive)
                                          (ansi-term "ls")
                                          (beginning-of-buffer)))

Re: Buffer created but why movement command of function ignored?

[Michael Heerdegen]

Chris Seberino <cseberino@gmail.com> writes:

> When I run this function the ansi-term is created but the point
> does NOT move to beginning of buffer.  Why?
>
> (global-set-key (kbd "M-l")       (lambda () (interactive)
>                                           (ansi-term "ls")
>                                           (beginning-of-buffer)))

That's expected.  It's because the output comes from an asynchronous
process and arrives after your function has long given back control to
the command loop.  When your (beginning-of-buffer) is evaluated, the
buffer is there but still empty.

That's why such things are typically done in a process sentinel.


Michael.