From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: bug#10125: RFE: require and load-path-shadowing Date: Fri, 11 Jan 2013 08:15:38 +0530 Message-ID: <87wqvk5tf1.fsf__48571.0906134502$1357872456$gmane$org@gmail.com> References: <87sj68eogm.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36248) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TtUe3-0004Ij-QR for emacs-orgmode@gnu.org; Thu, 10 Jan 2013 21:47:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TtUe2-0008WG-58 for emacs-orgmode@gnu.org; Thu, 10 Jan 2013 21:46:59 -0500 Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-Message-ID: In-Reply-To: (Stefan Monnier's message of "Thu, 10 Jan 2013 20:57:41 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Stefan Monnier Cc: Glenn Morris , Achim Gratz , 10125@debbugs.gnu.org Stefan Monnier writes: > - outdated .elc file taking precedence over the new .el file can do > the same. I find this warning quite useful. Consider this, all happening because of what is in .emacs. 1. Something in .emacs causes org-x to be loaded from Vanilla Emacs. 2. Load path changed to point to a git checkout. 3. User does something which loads org-y. org-y comes from (2). The chain of events ends up with requiring an org-x. org-x WASN'T RE-LOADED because the symbol is provided. Ofcourse, it is provided from the wrong place. In case of (3), a warning that says "I refuse to have mutiple personality disorder". A warning during Emacs initing could be missed. So if there is a command line option to trigger an abrupt-end, we could advise the user to enable it and say "You have got a problem in your init file. Not the Org-mode that is distributed." This will serve to remove endless amount of confusion. What I am saying, even if we couldn't solve the problem cleanly, a simple warning that says "Something fishy" will greatly reduce the user complaints in the Org list. I am not sure how much of what I typed makes sense. But I type nevertheless, people read it or ignore it. --