From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: unpleasant flickering in terminal emacs Date: Sat, 28 Apr 2018 09:27:48 +0300 Message-ID: <83muxnu9p7.fsf@gnu.org> References: <87po2k7tdr.fsf@gmail.com> <831sf0vmms.fsf@gnu.org> <87tvrwu1ul.fsf@gmail.com> <83po2ktzox.fsf@gnu.org> <87sh7gtx7l.fsf@gmail.com> <864ljw5qri.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1524896792 4814 195.159.176.226 (28 Apr 2018 06:26:32 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 28 Apr 2018 06:26:32 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Apr 28 08:26:28 2018 Return-path: Envelope-to: geh-help-gnu-emacs@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 1fCJJT-00018f-N7 for geh-help-gnu-emacs@m.gmane.org; Sat, 28 Apr 2018 08:26:27 +0200 Original-Received: from localhost ([::1]:51067 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fCJLY-000469-Vg for geh-help-gnu-emacs@m.gmane.org; Sat, 28 Apr 2018 02:28:37 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38507) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fCJL8-00045r-NA for help-gnu-emacs@gnu.org; Sat, 28 Apr 2018 02:28:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fCJL5-00057a-Jk for help-gnu-emacs@gnu.org; Sat, 28 Apr 2018 02:28:10 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:49189) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fCJL5-00057V-Fp for help-gnu-emacs@gnu.org; Sat, 28 Apr 2018 02:28:07 -0400 Original-Received: from [176.228.60.248] (port=4529 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fCJL4-0004Ej-IL for help-gnu-emacs@gnu.org; Sat, 28 Apr 2018 02:28:07 -0400 In-reply-to: <864ljw5qri.fsf@zoho.com> (message from Emanuel Berg on Fri, 27 Apr 2018 22:38:25 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:116623 Archived-At: > From: Emanuel Berg > Date: Fri, 27 Apr 2018 22:38:25 +0200 > > 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? People who discover something important frequently want that to be the first issue described in . Of course, there's only one such issue that can ever be the first one in any document... Emacs does have a FAQ (two of them, actually), but our documentation principles are that such fundamental issues should be in the manual, not in the FAQ. The Emacs manual has a chapter on reporting bugs, which begins with explaining how to establish there's a bug and how to search the list of known problems. Then it describes how to report a bug, and as part of that tells about "emacs -Q". > 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! The "start with 'emacs -Q'" rule doesn't mean you cannot load additional packages, set variables to non-default values, etc. The idea is to present a full recipe starting from 'emacs -Q', so that others could reproduce that without knowing anything about the Emacs setup on the OP's system. > 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? Exactly. Except that if the problem doesn't need a Gnus init file at all, you don't even need such a minimal file as part of the recipe. You can just show which variables should be set to what values, manually.