From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Robert Thorpe <rt@robertthorpeconsulting.com> Newsgroups: gmane.emacs.help Subject: Re: Fatal error 11: Segmentation Fault Date: Wed, 03 Apr 2019 22:07:55 +0100 Message-ID: <87imvupzkk.fsf@robertthorpeconsulting.com> References: <86r2airec0.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="185043"; mail-complaints-to="usenet@blaine.gmane.org" Cc: help-gnu-emacs@gnu.org To: Emanuel Berg <moasenwood@zoho.eu> Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Apr 03 23:08:27 2019 Return-path: <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org> 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 <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org>) id 1hBn7S-000m0O-G7 for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Apr 2019 23:08:26 +0200 Original-Received: from localhost ([127.0.0.1]:48822 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org>) id 1hBn7R-0008Bx-B3 for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Apr 2019 17:08:25 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:40016) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <rt@robertthorpeconsulting.com>) id 1hBn77-00089q-BI for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 17:08:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <rt@robertthorpeconsulting.com>) id 1hBn74-0000NG-8x for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 17:08:03 -0400 Original-Received: from outbound-smtp12.blacknight.com ([46.22.139.17]:53456) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from <rt@robertthorpeconsulting.com>) id 1hBn71-0000C2-75 for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 17:07:59 -0400 Original-Received: from mail.blacknight.com (pemlinmail04.blacknight.ie [81.17.254.17]) by outbound-smtp12.blacknight.com (Postfix) with ESMTPS id DD0151C1DD7 for <help-gnu-emacs@gnu.org>; Wed, 3 Apr 2019 22:07:55 +0100 (IST) Original-Received: (qmail 8184 invoked from network); 3 Apr 2019 21:07:55 -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 21:07:55 -0000 In-Reply-To: <86r2airec0.fsf@zoho.eu> (message from Emanuel Berg on Wed, 03 Apr 2019 23:03:43 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 46.22.139.17 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 <help-gnu-emacs.gnu.org> List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-gnu-emacs>, <mailto:help-gnu-emacs-request@gnu.org?subject=unsubscribe> List-Archive: <http://lists.gnu.org/archive/html/help-gnu-emacs/> List-Post: <mailto:help-gnu-emacs@gnu.org> List-Help: <mailto:help-gnu-emacs-request@gnu.org?subject=help> List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-gnu-emacs>, <mailto:help-gnu-emacs-request@gnu.org?subject=subscribe> Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org> Xref: news.gmane.org gmane.emacs.help:119891 Archived-At: <http://permalink.gmane.org/gmane.emacs.help/119891> Emanuel Berg <moasenwood@zoho.eu> writes: > Robert Thorpe wrote: > >> 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. > > It is a module at first alright, but what if > you have a second module later on, and that > second module uses stuff that the first module > already has? Do you kill/yank it into module-2 > verbatim? > > If so, they are not modules anymore IMO - more > like the opposite of modularity, I'm afraid - > "dinosaurs", perhaps... If the copying is only a few lines then I'd copy them. If not, I would put the common parts into a third file. Then I'd require that third file from both of the two original modules. BR, Robert Thorpe