[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#45085: Have so-long mode fire-sprinkler system always ready for M-x
From: |
積丹尼 Dan Jacobson |
Subject: |
bug#45085: Have so-long mode fire-sprinkler system always ready for M-x compile, M-x shell |
Date: |
Wed, 09 Dec 2020 20:51:34 +0800 |
>>>>> "PS" == Phil Sainty <psainty@orcon.net.nz> writes:
PS> One immediate issue with the scenario you're considering
PS> is that buffers handling process output are commonly
PS> auto-scrolling to the end of the output, which means that
Got an idea: Guilty until proven innocent!
E.g., when a *compilation* buffer is born, it should / could be in
so-long mode at birth.
And only when it is finished filling up, (compilation status: "exit") an
(automatic) inspection could be made. And only if there were no crazy
long lines in it, would so-long mode be lifted.
Yes, there are long (many minutes) compilation jobs. Ones where the
user is sure nothing will go wrong too. For them the user could set a
variable...