From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Monnier Subject: bug#10125: RFE: require and load-path-shadowing Date: Fri, 11 Jan 2013 17:52:33 -0500 Message-ID: References: <87sj68eogm.fsf@Rainer.invalid> <87wqvjd7qa.fsf@Rainer.invalid> <87bocvcx9f.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41516) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TtnT8-0008TF-36 for emacs-orgmode@gnu.org; Fri, 11 Jan 2013 17:53:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TtnT3-0000fl-OV for emacs-orgmode@gnu.org; Fri, 11 Jan 2013 17:52:58 -0500 Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-Message-ID: In-Reply-To: <87bocvcx9f.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 11 Jan 2013 20:53:00 +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: Achim Gratz Cc: 10125@debbugs.gnu.org >>>> I guess we could fork Emacs early on and keep this second process >>>> around as a "process from which to generate new clean slates". >>> I've been thinking about something like this for a while=E2=80=A6 if it= worked >>> at least as well as starting a new Emacs instance on all platforms, I'd >>> favor this approach. >> IIUC "fork" is not really an option for w32. > For the intended application spawn should work as well? Could be: depends on the precise semantics of spawn, which I don't know. >> Along the same lines, we could try to use unload-feature. > I thought this was potentially dangerous, but reading the docstring > again maybe not. Let me try that as well. It's fundamentally tricky just in the same way as your proposed "namespace cleanup": if you undefine a function that's still registered on some hook, process filter, ... you may get subsequent errors, some of which may render Emacs completely unusable. So it's risky to call unload-feature on a random package, but it's not too hard for a package to make sure it survives unload-feature. Tho currently, there are some significant shortcomings (IIRC there are cases where the package's autoloads aren't re-instated, for example). Stefan