From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: reloading causes visibility bug requiring restart Date: Wed, 8 Apr 2009 08:45:25 +0200 Message-ID: <92AF42A6-AB05-41C3-832B-6FD9B44F12EE@gmail.com> References: <20524da70904051118n5a304526sb364130170aab58e@mail.gmail.com> <030733CA-9EE1-4D83-AC8E-913DC3E33109@gmail.com> <20524da70904071337n6a02cf6qa520f88f769a7baf@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LrRXR-0006PH-RL for emacs-orgmode@gnu.org; Wed, 08 Apr 2009 02:45:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LrRXO-0006JS-0Y for emacs-orgmode@gnu.org; Wed, 08 Apr 2009 02:45:33 -0400 Received: from [199.232.76.173] (port=36194 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LrRXN-0006J8-JK for emacs-orgmode@gnu.org; Wed, 08 Apr 2009 02:45:29 -0400 Received: from mx20.gnu.org ([199.232.41.8]:52579) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LrRXM-0000KO-Vp for emacs-orgmode@gnu.org; Wed, 08 Apr 2009 02:45:29 -0400 Received: from mail-gx0-f160.google.com ([209.85.217.160]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LrRXM-0002k0-2Z for emacs-orgmode@gnu.org; Wed, 08 Apr 2009 02:45:28 -0400 Received: by gxk4 with SMTP id 4so7218215gxk.18 for ; Tue, 07 Apr 2009 23:45:27 -0700 (PDT) In-Reply-To: <20524da70904071337n6a02cf6qa520f88f769a7baf@mail.gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Samuel Wales Cc: emacs-orgmode@gnu.org, Carsten Dominik On Apr 7, 2009, at 10:37 PM, Samuel Wales wrote: > Thanks, Carsten. That sounds like exactly the right solution. > > One question. Are there any org .elc files that perform actions upon > loading? e..g. defining a key that the user might have redefined in a > hook or setting a variable that the user might have reset? If so, > reloading might cause unexpected behavior. Or is this all taken care > of if the user is careful? My guess is that you've already considered > this, but thought it worth asking just in case. I am not sure myself. - Carsten