From: Bastien <email@example.com>
Subject: Re: Regression in `org-todo'
Date: Tue, 03 Apr 2012 00:40:39 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <7135.1333402849@alphaville> (Nick Dokos's message of "Mon, 02 Apr 2012 17:40:49 -0400")
Nick Dokos <email@example.com> writes:
> Michael Strey <firstname.lastname@example.org> wrote:
>> Hi Bastien,
>> On Mon, Apr 02, 2012 at 05:03:04PM +0200, Bastien wrote:
>> > ...
>> > Please test against latest HEAD and tell me if your problem is still
>> > here, it shouldn't.
>> I confirm that the problem is solved. Thank you!
>> It's interesting to see how a bug in a module from the contrib path can
>> cause strange behaviour of org-mode's core functions.
> There is no distinction between contrib and core. Once a module is
> loaded (wherever it comes from), it is part of emacs and can cause all
> kinds of damage: not just to org, but to the whole running emacs. It's
> the price one pays for the convenience of dynamically loading code. You
> can avoid the danger by not loading modules, but then emacs becomes much
> less interesting: after all, the "e" stands for "extensible".
If the features provided by org-checklist.el are useful to many people,
including them in core seems quite natural. I don't use it myself, I'm
just wondering how people do. But I agree with you here that we should
not move things into core inconsiderately.
next prev parent reply other threads:[~2012-04-02 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 15:01 Regression in `org-todo' Moritz Ulrich
2012-04-01 18:35 ` [URGENT] " Moritz Ulrich
2012-04-01 20:29 ` Bastien
2012-04-01 20:37 ` Bastien
2012-04-02 14:54 ` Michael Strey
2012-04-02 15:03 ` Bastien
2012-04-02 20:44 ` Michael Strey
2012-04-02 21:07 ` Bastien
2012-04-02 21:43 ` Nick Dokos
[not found] ` <email@example.com>
2012-04-02 21:40 ` Nick Dokos
2012-04-02 22:40 ` Bastien [this message]
2012-04-02 23:18 ` Bernt Hansen
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).