From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: unpleasant flickering in terminal emacs
Date: Fri, 27 Apr 2018 22:38:25 +0200 [thread overview]
Message-ID: <864ljw5qri.fsf@zoho.com> (raw)
In-Reply-To: mailman.13046.1524853658.27995.help-gnu-emacs@gnu.org
Eli Zaretskii wrote:
> Then I take it as meaning that "emacs -Q"
> doesn't show the problem, even if you load
> the theme you are normally using? If so,
> I suggest to bisect your customizations to
> find out which one(s) cause this flickering,
> then come back here and tell what you found.
Is there an Emacs FAQ? (Of course there is.
Somewhere in Emacs!) The first question should
be,
Q: I have a problem when I [insert the rest
of your question here]
A: run Emacs like this
$ emacs -Q
does the problem remain?
I guess this is an inherent problem with all
software that is based on customization and
extension, and where that happens in text files
that contain code. (Now it sounds like I have
tons of such software. And maybe I do...)
In practice, I have not experienced this as
a problem. I can find the bug in all my init
files because they are loaded by theme. So to
do binary search does not mean commenting out
half the code in a single enormous file (that
itself contains comments/"sections as
comments").
But that's the mere technical side to searching
of course. With time, one gets better at
finding the problem by thinking at the same
time as one does a brute-force attempt.
That's why the fighters that can punch AND
think are the best. Or carpenters for
that matter!
The only exception to the rule "isolating the
problem isn't difficult" that I have
encountered is with Gnus. Because leave out the
configuration, and you can't get to your
e-mail, or to any newsgroups, so you can't
reproduce the error w/o the Gnus your
init files!
Perhaps one should do like the LaTeX people
with their hangup on "minimal working
examples", namely, write a "minimal Gnus init
file" that does that and only that, namely
connects to ONE mailbox, and a single NNTP
newsgroup, and one Gmane/NNTP ditto, and why
not the .test ones while at it?
Then one could say, OK, so Gnus works. But not
my Gnus!
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2018-04-27 20:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 11:58 unpleasant flickering in terminal emacs Amos Bird
2018-04-27 12:04 ` Tim Visher
2018-04-27 12:23 ` Amos Bird
2018-04-27 12:51 ` Eli Zaretskii
2018-04-27 12:50 ` Eli Zaretskii
2018-04-27 15:05 ` Amos Bird
2018-04-27 15:51 ` Eli Zaretskii
2018-04-27 16:45 ` Amos Bird
2018-04-27 18:27 ` Eli Zaretskii
2018-04-28 3:36 ` Amos Bird
2018-04-28 6:40 ` Eli Zaretskii
[not found] ` <mailman.13046.1524853658.27995.help-gnu-emacs@gnu.org>
2018-04-27 20:38 ` Emanuel Berg [this message]
2018-04-28 6:27 ` Eli Zaretskii
[not found] ` <mailman.13064.1524896893.27995.help-gnu-emacs@gnu.org>
2018-04-28 11:05 ` Emanuel Berg
[not found] <mailman.13019.1524830349.27995.help-gnu-emacs@gnu.org>
2018-04-27 15:14 ` Emanuel Berg
2018-04-27 16:47 ` Amos Bird
[not found] ` <mailman.13042.1524847634.27995.help-gnu-emacs@gnu.org>
2018-04-27 16:58 ` Emanuel Berg
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=864ljw5qri.fsf@zoho.com \
--to=moasen@zoho.com \
--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.
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).