From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Jason Vas Dias Newsgroups: gmane.emacs.devel Subject: Re: emacs coding modes need 'Suspend Disbelief' button Date: Fri, 19 May 2017 11:43:53 +0000 Message-ID: References: <83shk12is5.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1495194248 19512 195.159.176.226 (19 May 2017 11:44:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 19 May 2017 11:44:08 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 19 13:44:05 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dBgKC-0004y2-KV for ged-emacs-devel@m.gmane.org; Fri, 19 May 2017 13:44:04 +0200 Original-Received: from localhost ([::1]:58062 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dBgKI-0007Gl-9I for ged-emacs-devel@m.gmane.org; Fri, 19 May 2017 07:44:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57685) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dBgK5-0007CI-QD for emacs-devel@gnu.org; Fri, 19 May 2017 07:43:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dBgK5-0000Ol-0m for emacs-devel@gnu.org; Fri, 19 May 2017 07:43:57 -0400 Original-Received: from mail-ua0-x233.google.com ([2607:f8b0:400c:c08::233]:35904) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dBgK3-0000OV-NP; Fri, 19 May 2017 07:43:55 -0400 Original-Received: by mail-ua0-x233.google.com with SMTP id j17so24132544uag.3; Fri, 19 May 2017 04:43:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2e+xd36r1CyjsOe2ipbQS6VtrmF0JQejnXdouuQwi1s=; b=iMwJaUxx8O7fl4OmyozVC9gDKyP88dcRxeCLL4abEiaeEedvVZ8m9m6qBPVSX+CDzG 0dNg7GJN49vqyUlSuWaKl1qwAIYMNYAf51pQcwmBKDlG5AwmUdBwskjN7JMBVcGnnmRQ 5Koqhc6k/Wnu+a3dWlM59Azcjh7NhDeUANmiukQCFrvRVGyFNzv38EyQuoI6qqvyw+2h Fqh8D2W+qWBzZu1lppeY7FR4b46HlOHgM0v+KxMmNrVXXuPay/k9I2GBb0JSHAgKnAcg LHtgeUS6euxxsV/UwURKWQeT7+nncl0SOA2Yj65VSsfNNubCvI0rHIC5T6niTqPiPfRF aQtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2e+xd36r1CyjsOe2ipbQS6VtrmF0JQejnXdouuQwi1s=; b=rgEviTxOSfjOn0b5T/WTC8uFuUjKU0e0SHXJEZ68QwZuH3yL/eXQw5/nSMCI2upIVa Idabh7lw3GJi51C16xJ/2kC5rBcMT26CKG+oIULPl4vJLexky3tsDif0TD+ONFhdr5WI jGc3p7INx7YwKqKC4dUtO/K6kTKIdpMcR686tX0riynGX0A9ZEZre/42m0ySzlVtAhdf yzF4GjBuo/DFVQvwMK+W/PmTuX98+tM/FkkFyScyipxepd1D9J/3d99rzuSAcREEssI9 MMJ5Fjd63IHUHfzWrcyaj4U7FeUdWOSBw4MRq2lCEjbyTBvdvHPa2aW21Xzb/jsIH1r5 q9iQ== X-Gm-Message-State: AODbwcBbhEnKWcsl05xrThSrg4w0Aa1mTpw8W14XTkEjuRp+CvtBMqby xdo5BVox6IxCMtJcHmtuvZfbq03oUw== X-Received: by 10.176.77.158 with SMTP id s30mr4497759uag.29.1495194234475; Fri, 19 May 2017 04:43:54 -0700 (PDT) Original-Received: by 10.103.37.134 with HTTP; Fri, 19 May 2017 04:43:53 -0700 (PDT) In-Reply-To: <83shk12is5.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400c:c08::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:214991 Archived-At: The problem is, it is a transient and timing related bug - I cannot reproduce it at will . But it has happened several times over the last month . Fortunately, emacs has always saved a '##' crash file and I've been able to recover what I was typing. The last exact difference that caused a core dump was : $ diff -U0 sets.sh \#sets.sh# --- sets.sh 2017-05-19 09:40:20.150752587 +0000 +++ #sets.sh# 2017-05-19 09:48:20.160120576 +0000 @@ -9,0 +10 @@ +_r=''; @@ -36,0 +38,3 @@ + function needle_cmp() + { + @@ -65,3 +68,0 @@ - if ! IN $x $needle; then - return 1; - fi Now, that's not much to go on, and I can't reproduce it by typing: function f() { function fsub() { } if ! f $x; then return 1; fi } Nor can I reproduce it by making same edits in clean emacs . But leaving the core dumps aside, continuous syntax checking and document re-coloring is just plain annoying, when typing, but is nice when reading - I wish I could turn it off & on quickly & easily . On 19/05/2017, Eli Zaretskii wrote: >> From: Jason Vas Dias >> Date: Fri, 19 May 2017 10:54:28 +0000 >> >> I just thought I should let you know, >> being an emacs user of over 20 years, >> that I think the fact that it is possible >> to core-dump emacs by simply adding >> some text to a shell script is bad > > I agree, and I urge you to report this as bugs, with all the details > required to reproduce the problem. >