From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Robert Thorpe Newsgroups: gmane.emacs.help Subject: Re: Fatal error 11: Segmentation Fault Date: Wed, 03 Apr 2019 18:41:35 +0100 Message-ID: <87o95nouk0.fsf@robertthorpeconsulting.com> References: <20190403162903.GA22109@tuxteam.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="269249"; mail-complaints-to="usenet@blaine.gmane.org" Cc: help-gnu-emacs@gnu.org To: Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Apr 03 19:41:57 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBjtc-0017sO-GA for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Apr 2019 19:41:56 +0200 Original-Received: from localhost ([127.0.0.1]:45473 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hBjtb-0002gd-Dk for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Apr 2019 13:41:55 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:46778) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hBjtP-0002gJ-Rq for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 13:41:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hBjtO-0004by-UA for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 13:41:43 -0400 Original-Received: from outbound-smtp09.blacknight.com ([46.22.139.14]:45607) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hBjtO-0004Vy-MI for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 13:41:42 -0400 Original-Received: from mail.blacknight.com (pemlinmail03.blacknight.ie [81.17.254.16]) by outbound-smtp09.blacknight.com (Postfix) with ESMTPS id 64D2D1C26C7 for ; Wed, 3 Apr 2019 18:41:36 +0100 (IST) Original-Received: (qmail 12503 invoked from network); 3 Apr 2019 17:41:36 -0000 Original-Received: from unknown (HELO RTLaptop) (rt@robertthorpeconsulting.com@[51.37.88.142]) by 81.17.254.9 with ESMTPSA (AES128-SHA encrypted, authenticated); 3 Apr 2019 17:41:36 -0000 In-Reply-To: <20190403162903.GA22109@tuxteam.de> (tomas@tuxteam.de) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 46.22.139.14 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:119884 Archived-At: writes: > On Wed, Apr 03, 2019 at 04:34:32PM +0200, Emanuel Berg wrote: >> tomas wrote: >> >> > And here you see the price you pay for your >> > above decision [...] > >> ... what approaches are there, again? > > I was talking about every piece of code (conditionally) pulling > in its dependencies (with require, e.g.). This makes it much > easier to skip parts without the whole construction breaking > down. But hey -- it's just an offer. You are not forced to do > it this way :-D > > Cheers > -- t For what it's worth, this is the approach I use. If I have a lot of related elisp then I put it into a file by itself. I treat it as a self-contained module. All of the dependencies it needs are required there. So, I could hand the file to someone else using stock Emacs and it would just work. This method is useful for debugging. BR, Robert Thorpe