From: Achim Gratz <Stromeko@nexgo.de> To: firstname.lastname@example.org Subject: Re: org-plus-contrib: Invalid function: org-no-popups Date: Sat, 26 Jan 2013 13:48:30 +0100 [thread overview] Message-ID: <87sj5o155t.fsf@Rainer.invalid> (raw) In-Reply-To: <email@example.com> 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
next prev parent reply other threads:[~2013-01-26 12:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-23 17:42 Moritz Ulrich 2013-01-24 14:08 ` Bastien 2013-01-24 20:42 ` Achim Gratz 2013-01-24 21:59 ` Bastien 2013-01-25 6:48 ` Achim Gratz 2013-01-25 8:51 ` Bastien 2013-01-25 10:33 ` Bastien 2013-01-25 19:59 ` Achim Gratz 2013-01-26 10:45 ` Bastien 2013-01-26 12:48 ` Achim Gratz [this message] 2013-01-26 13:11 ` Bastien
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=87sj5o155t.fsf@Rainer.invalid \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: org-plus-contrib: Invalid function: org-no-popups' \ /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
Code repositories for project(s) associated with this 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).