emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <dominik@science.uva.nl>
Subject: Re: reloading causes visibility bug requiring restart
Date: Wed, 8 Apr 2009 08:45:25 +0200	[thread overview]
Message-ID: <92AF42A6-AB05-41C3-832B-6FD9B44F12EE@gmail.com> (raw)
In-Reply-To: <20524da70904071337n6a02cf6qa520f88f769a7baf@mail.gmail.com>


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

  reply	other threads:[~2009-04-08  6:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05 18:18 reloading causes visibility bug requiring restart Samuel Wales
2009-04-05 19:27 ` Carsten Dominik
2009-04-06  5:56   ` Manish
2009-04-06  6:08     ` Carsten Dominik
2009-04-06 10:57     ` Carsten Dominik
2009-04-06 12:05       ` Sebastian Rose
2009-04-06 15:47         ` Manish
2009-04-07 20:10       ` Carsten Dominik
2009-04-07 20:37         ` Samuel Wales
2009-04-08  6:45           ` Carsten Dominik [this message]
2009-04-07  5:21   ` Samuel Wales
2009-04-05 19:33 ` Bernt Hansen
2009-05-07 14:48   ` Peter Westlake
2009-05-07 16:07     ` Bernt Hansen
2009-05-08  4:24     ` Carsten Dominik
2009-05-08 10:20       ` Peter Westlake
2009-05-08 10:53         ` Carsten Dominik
2009-05-08 11:06     ` Carsten Dominik
2009-05-08 17:56       ` Peter Westlake

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=92AF42A6-AB05-41C3-832B-6FD9B44F12EE@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).