emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Remove the build-in orgmode
Date: Sat, 07 Jun 2014 07:57:06 +0200	[thread overview]
Message-ID: <87a99pntxp.fsf@gmail.com> (raw)
In-Reply-To: 87egz1vrf0.fsf@Rainer.invalid

Achim Gratz <Stromeko@nexgo.de> writes:

> Nick Dokos writes:
>> I did that in the past (presumably for reasons similar to Thorsten's)
>> and I don't bother any longer (overriding is simple enough as you point
>> out), but the question  still bugs me: what's so bad about it?
>
> The reason it is bad is that parts of the code have already leaked out
> from the org/ directory via custom-load and autoloads and that's going
> to break things in the least convenient moment – for instance when you
> try to hunt down bugs via "-Q".  There simply is no way to remove the
> builtin Org from Emacs other than at build time and it's best not to
> pretend otherwise.  Some day Emacs might actually treat its built-in
> packages as actual packages so that you can de-activate or replace them,
> but I wouldn't hold my breath.

That sounds reasonable enough, but somehow that least convenient moment
never happens, while I remember *many* such moments when I still had more
than one Org on my machine ... but maybe I just don't huntdown bugs via
-Q often enough.

-- 
cheers,
Thorsten

  reply	other threads:[~2014-06-07  5:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 22:22 Remove the build-in orgmode Shiyuan
2014-06-02  6:46 ` Brady Trainor
2014-06-02  7:18   ` Rainer M Krug
2014-06-02  7:26 ` Thorsten Jolitz
2014-06-06 14:09   ` Bastien
2014-06-06 16:01     ` Nick Dokos
2014-06-06 18:12       ` Achim Gratz
2014-06-07  5:57         ` Thorsten Jolitz [this message]
2014-06-11  6:05           ` Shiyuan

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=87a99pntxp.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=emacs-orgmode@gnu.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).