From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: org-plus-contrib: Invalid function: org-no-popups Date: Sat, 26 Jan 2013 13:48:30 +0100 Message-ID: <87sj5o155t.fsf@Rainer.invalid> References: <87ham6wbwx.fsf@Rainer.invalid> <87622mkzti.fsf@bzg.ath.cx> <87pq0tzrk0.fsf@Rainer.invalid> <871ud9ir2e.fsf@bzg.ath.cx> <874ni5owxt.fsf@Rainer.invalid> <871ud88bp7.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57442) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tz5Bc-0000WH-Dv for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 07:48:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tz5Bb-0006Uv-7W for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 07:48:44 -0500 Received: from plane.gmane.org ([80.91.229.3]:51003) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tz5Bb-0006UP-0g for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 07:48:43 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Tz5Bp-0004Uy-Fi for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 13:48:57 +0100 Received: from pd9eb27a9.dip.t-dialin.net ([217.235.39.169]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Jan 2013 13:48:57 +0100 Received: from Stromeko by pd9eb27a9.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Jan 2013 13:48:57 +0100 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: emacs-orgmode@gnu.org Bastien writes: > I don't like it for at least these reasons: > > - it introduces an advice in the code -- we should work toward > removing them, not adding them. That's the mechanism Emacs provides for dealing with those situations. I could do it without an advice, but it would still do the same things, namely unload all features that have been shadowed by changing load-path so that they can be re-loaded from the correct place. It may have escaped your attention, but the advice is de-activated at the earliest possible moment and will not affect any later uses of require. > - it advices `require', which is a very core function in Emacs. Which has been discussed on Emacs devel and has been pronounced safe in this case. > This is completely hackish. Like a few hundred other places in Emacs and Org. Also, when some day Emacs will perhaps solve the problem, the solution will likely be something very similar: renaming the require primitive and creating a wrapper in Lisp that does what the advice is doing. > This is like telling Windows users to reboot their system so that it > can works correctly (remember the old days?). It feels wrong. And I > doubt we can educate the users -- there are many of them, and many > don't have the time to tell they have a problem. So why are you trying to educate users not to use ELPA when you think it's a waste of time? > I'm not sure what solution you suggest here. A problem produced by a certain piece of software should be fixed by that same software. For example, if starter-kit insists on loading Org before things are ready, it should also unload Org after it is finished using it and before the actual initialization commences. > In general, I think the benefit of having several ELPA distributions > of Org is not worth the trouble of dealing with installation issues. You're confusing me. Do you want to remove Org from ELPA or not? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds