From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ryo Furue <furue@hawaii.edu>
Cc: 4709@emacsbugs.donarmstrong.com
Subject: bug#4709: 23.1; keyboard-translate not working with emacs daemon
Date: Fri, 16 Oct 2009 22:22:46 -0400 [thread overview]
Message-ID: <jwvr5t2223z.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <20091016.145549.159790690.furue@hawaii.edu> (Ryo Furue's message of "Fri, 16 Oct 2009 14:55:49 -1000 (HST)")
> | That doesn't sound right. Can you check that the relevant code from
> | your .emacs is indeed executed? E.g. add a (message "I'm here") and/or
> | a (setq my-test 'passed) right after the define-key.
> Thank you for debugging my problem and I'm sorry that that was
> purely my mistake. I was forgetting that I had a byte-compiled
> version of .emacs !
Good, thanks.
> I hadn't been interested in byte compilation before emacs23
> because the startup of emacs22 (and emacs21 if I remember
> correctly) was lightening quick. emacs23's startup,
> on the other hand, is crawlingly slow. That's why
> I tried byte-compilation (but that didn't help much)
> and then the emacs daemon (which is a nice solution).
Emacs-23 is known to be generally slower because of the new font-engine
which considers many more font options at startup, but it is not
expected to be as much slower as you seem to indicate. So maybe
a bug-report about it is in order.
> I understand there are two schools of thoughts:
> 1) The byte compiled version is a stable version
> and the source is a work in progress. Therefore,
> the byte compiled version should be used.
> 2) The byte compiled version is just a faster version
> of the source. Therefore, whichever is the newer
> should be used.
> My guess is that view 1 is generally taken by elisp
> developers and so that's the default behavior of emacs.
> I guess most "ordinary" users would take View 2; they
> don't have much elisp code in progress. I'm wondering
> if there is a simple way to switch between the two
> behaviors easily and quickly.
No there isn't. Please make it a separate M-x report-emacs-bug if you
want such a feature.
Stefan
next prev parent reply other threads:[~2009-10-17 2:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 20:37 bug#4709: 23.1; keyboard-translate not working with emacs daemon Ryo Furue
2009-10-14 13:25 ` Stefan Monnier
2009-10-14 21:07 ` Ryo Furue
2009-10-15 3:34 ` Stefan Monnier
2009-10-15 7:34 ` Ryo Furue
2009-10-15 15:22 ` Stefan Monnier
2009-10-15 18:26 ` Ryo Furue
2009-10-15 20:28 ` Stefan Monnier
2009-10-17 0:55 ` Ryo Furue
2009-10-17 2:22 ` Stefan Monnier [this message]
2009-10-17 3:19 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvr5t2223z.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=4709@emacsbugs.donarmstrong.com \
--cc=furue@hawaii.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.