From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Problem after updating org: C-c a a broken
Date: Fri, 28 Oct 2011 23:11:44 +0200 [thread overview]
Message-ID: <80wrbog6sv.fsf@somewhere.org> (raw)
In-Reply-To: 10252.1319830069@alphaville.americas.hpqcorp.net
Hi Nick and Markus,
Nick Dokos wrote:
> Nick Dokos <nicholas.dokos-VXdhtT5mjnY@public.gmane.org> wrote:
>> Markus Heller <hellerm2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>> > Hm, so ok, restarting emacs actually solved it.
>> >
>> > Kinda weird, because I never had to do this when updating org (I don't
>> > compile the sources, I just do C-c C-x !).
>> >
>> > Seems a bit odd to me but it's working again so I'm happy :)
>> >
>> > I apologize for the noise.
>>
>> Did you try M-x org-reload RET? That should work but sometimes it misses
>> something (but if it does, that would be a bug of course, so report it).
>
> nm - I missed the C-c C-x !
I don't think org-reload is fully bullet-proof. I think it misses changes in
defvars, deffaces, and the like: once set, if the default is changed, it's not
updated by reloading the files.
Now, in 99.999% of the cases, that should not be a problem. But to be really
safe...
Last thing, how is this problem solved by a restart of Emacs and not by a
reload, not sure we can easily understand.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-10-28 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 18:36 Problem after updating org: C-c a a broken Markus Heller
2011-10-28 19:09 ` Nick Dokos
2011-10-28 19:16 ` Markus Heller
2011-10-28 19:19 ` Markus Heller
2011-10-28 19:25 ` Nick Dokos
2011-10-28 19:27 ` Nick Dokos
2011-10-28 21:11 ` Sebastien Vauban [this message]
2012-04-13 0:45 ` Jinli
2011-10-28 19:19 ` Nick Dokos
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=80wrbog6sv.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).