From: Jason Vas Dias <jason.vas.dias@gmail.com>
To: emacs-devel@gnu.org, help-gnu-emacs@gnu.org
Subject: emacs coding modes need 'Suspend Disbelief' button
Date: Fri, 19 May 2017 10:54:28 +0000 [thread overview]
Message-ID: <CALyZvKzyfer+sqHGuUEyz05pi_Q4aQnJk0=F6-06KvVaw2=_9g@mail.gmail.com> (raw)
Hi Emacs wizards -
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 , and
that I think modern emacs is going too
far in continuously syntax-checking
and parsing code.
In general, when using programming modes
such as c-mode / cc-mode / shell-script-mode ,
I wish, when typing, I could just turn all syntax
checking off by clicking on a 'Suspend Disbelief'
or 'Syntax Check Off' button / checkbox -
then, when I enter '"' or "'", the rest of the text
would not be colored - this is really annoying and greatly
slows down editing of large files - I don't want
the cursor to jump to the previous open bracket,
and I want the current indent to be preserved, until
I un-check 'Syntax Check' or press 'Syntax Check On' .
The insistence of modern emacs on always unconditionally
syntax checking everything greatly slows down typing and
is a major inhibition to quick editing of large source files .
And in some modes, such as shell script mode, and also
cc-mode, it is still possible to core-dump Emacs (latest 25.2 version)
simply by entering partial source code too slow or too fast , because of this
continuous syntax-checking .
I have core-dumped emacs several times recently by doing this -
one example that works pretty reliably is to start defining a
function within a function in shell-script - there is a timing
related bug , if you don't enter the opening '{' fast enough,
emacs will core-dump .
Emacs is regressing back towards 1990s levels of reliability
because of its insistence on continuous syntax checking .
Is there any way to globally turn off continuous syntax checking
for all modes ?
If not, I'm going to develop one.
Thanks & Regards,
Jason
next reply other threads:[~2017-05-19 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 10:54 Jason Vas Dias [this message]
2017-05-19 11:22 ` emacs coding modes need 'Suspend Disbelief' button Eli Zaretskii
2017-05-19 11:43 ` Jason Vas Dias
2017-05-26 13:32 ` Thien-Thi Nguyen
2017-06-21 18:38 ` Jason Vas Dias
2017-06-23 21:11 ` Stefan Monnier
[not found] ` <20170519112004.GA31732@tuxteam.de>
[not found] ` <CALyZvKzvUBe1-+yTnpK97MA=Dh5q89RmTugG3CJ0bcrbqnd2Eg@mail.gmail.com>
2017-05-19 11:37 ` Fwd: " Jason Vas Dias
2017-05-20 7:47 ` Robert Thorpe
2017-05-19 11:42 ` Óscar Fuentes
2017-05-19 13:35 ` Drew Adams
2017-05-19 16:23 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALyZvKzyfer+sqHGuUEyz05pi_Q4aQnJk0=F6-06KvVaw2=_9g@mail.gmail.com' \
--to=jason.vas.dias@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).