Re: emacs coding modes need 'Suspend Disbelief' button

[Jason Vas Dias <jason.vas.dias@gmail.com>]

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 '#<file name>#'
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 <eliz@gnu.org> wrote:
>> From: Jason Vas Dias <jason.vas.dias@gmail.com>
>> 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.
>