From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.help Subject: RE: Fatal error 11: Segmentation Fault Date: Wed, 3 Apr 2019 10:06:41 -0700 (PDT) Message-ID: <76a8206d-702c-484d-867c-912aa860d34a@default> References: <86imvx5gyz.fsf@zoho.eu> <86ef6l5dwk.fsf@zoho.eu> <86a7h85ru5.fsf@zoho.eu> <865zrw55gm.fsf@zoho.eu> <5e7fb661-c090-4893-bcab-24ee4d96bea3@default> <86ftqzhd04.fsf@zoho.eu> <20190403081845.GA6609@tuxteam.de> <86k1gbximf.fsf@zoho.eu> <20190403162903.GA22109@tuxteam.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="106173"; mail-complaints-to="usenet@blaine.gmane.org" To: tomas@tuxteam.de, help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Apr 03 19:07:19 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 1hBjM6-000RXE-VH for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Apr 2019 19:07:19 +0200 Original-Received: from localhost ([127.0.0.1]:35081 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hBjM5-0002cy-VJ for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Apr 2019 13:07:17 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:40589) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hBjLu-0002ah-Nm for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 13:07:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hBjLs-0001u4-RC for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 13:07:06 -0400 Original-Received: from userp2120.oracle.com ([156.151.31.85]:59554) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hBjLo-0001Po-W5 for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 13:07:03 -0400 Original-Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x33H3rOi158245; Wed, 3 Apr 2019 17:06:55 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=UB1bW6YwZU37Ku/OQ95tZEBub2Zrch6u/xAJ6kbXBZs=; b=CovlFR+6Aggrv9mmVjGErzgKgneSs4TgwCRBMXJ3XVfyR/KwaHUSBKR3VseAg8jbbBP4 sL2pf/EHsbePBRxzxbNBJM/NMvViTseBUEhxkQiTskfNcEDruy82mAuQvaqX1CX5sKMA zP/IeMNYHmjo1iAV9zY7fw1Folpz9Ym0tkXxSj300OHeMYKsZ6q2Cr4nyCwfafGgQVZF ORhIOdQbbZTs+lScBOZ0v5nQ7Xf59gz10K003bWbX36V7rG4LpRoxjveXE6qm8tVeIt7 +G7RypGNxaLj/ckVQWa2kbvGCvvvw+kJTL9TQdT5u/sE8SIxTcYtc6Ck17rHGyCsj++E kw== Original-Received: from aserp3020.oracle.com (aserp3020.oracle.com [141.146.126.70]) by userp2120.oracle.com with ESMTP id 2rj13qa9hk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 03 Apr 2019 17:06:54 +0000 Original-Received: from pps.filterd (aserp3020.oracle.com [127.0.0.1]) by aserp3020.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x33H5LpO076288; Wed, 3 Apr 2019 17:06:53 GMT Original-Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserp3020.oracle.com with ESMTP id 2rm9mj6276-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 03 Apr 2019 17:06:53 +0000 Original-Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id x33H6gF9027790; Wed, 3 Apr 2019 17:06:45 GMT In-Reply-To: <20190403162903.GA22109@tuxteam.de> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4822.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9216 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904030116 X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9216 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904030116 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] X-Received-From: 156.151.31.85 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:119880 Archived-At: > > > And here you see the price you pay for your > > > above decision [...] >=20 > > ... what approaches are there, again? >=20 > 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 I tried suggesting the same thing. Imagine... You're going on vacation. You make a list of what you need to bring. For each thing you think of you decide to list not only that thing but also each of its parts. For your car you list not only "car" but also tires, engine, transmission, radio... Why? Because you think it's easier somehow. Because you can loop over your checklist... Your car already requires its tires (at least it should!). Leaving your car home should automatically leave your tires home. But if you list each bit separately then sure, if you try to bring your car _without_ the tires there'll be a problem because it thinks it needs them (and it does). This is why we have things like `require' - they keep track of dependencies for us. List only the things _you_ need to bring. Make sure that things that require other things know that they require them, so _they_ take care of bringing whatever _they_ need, saving you the bother. Then if you leave something home none of the things you bring with you will holler.