Seiji Zenitani
zenit****@tkg*****
Wed Aug 17 00:31:59 JST 2005
Hi, On 2005/08/15, at 1:34, Kasi wrote: > > (add-hook 'after-init-hook 'server-start) > > to be responsible. The problem is, the after-init-hook is only > evaluated, after emacs has started. That's the reason for the > different behavior between using .emacs and evaluating the file after > initialization. Whenever I start the server, it starts using CPU > time. This behavior is different on Unix. For example, the > emacsserver does not use CPU time in Linux. So is this a MacOS/Darwin > specific thing? Are there differences in the source between the > emacsserver on Mac and on Linux? Another choice: how about using a shell command: 'open -a Emacs.app'? At my hand, emacsserver constantly consumes 0.6%-0.7% of the CPU time. > Another bug, which I hope that someone else can confirm. > > - Open a console (or iterm) > - type 'open /Applications/Emacs.app' > - press return and keep repetitively hitting return > - Emacs will open up and immediately die > > This also happens, if you press other keys, however, it's easy to > show with the return key. Why is this bug annoying: if you click to > open emacs and continue to write, for instance, an email, you will > encounter this problem. Yes, emacs seems to be unstable to keyboard input events in its startup time. This problem is well-known one, but it remains unsolved. -- Seiji
