From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: RDS Newsgroups: gmane.emacs.bugs Subject: bug#50462: 27.2; emacsclient syntax highlight failure Date: Wed, 8 Sep 2021 13:32:46 -0700 Message-ID: References: <83sfygnsgv.fsf@gnu.org> <83o893obwy.fsf@gnu.org> <87r1dz7e24.fsf@gnus.org> <838s07o67b.fsf@gnu.org> <83wnnrknk9.fsf@gnu.org> <83r1dylvi6.fsf@gnu.org> <83mtomlt4j.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000272aa005cb81cb3e" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1686"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, 50462@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 08 22:34:14 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mO4Gs-00009n-6z for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 08 Sep 2021 22:34:14 +0200 Original-Received: from localhost ([::1]:50330 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mO4Gq-0002E9-G2 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 08 Sep 2021 16:34:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38822) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mO4Gg-0002Du-7I for bug-gnu-emacs@gnu.org; Wed, 08 Sep 2021 16:34:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50337) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mO4Gf-0000z1-WD for bug-gnu-emacs@gnu.org; Wed, 08 Sep 2021 16:34:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mO4Gf-0000vj-Oc for bug-gnu-emacs@gnu.org; Wed, 08 Sep 2021 16:34:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: RDS Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 08 Sep 2021 20:34:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50462 X-GNU-PR-Package: emacs Original-Received: via spool by 50462-submit@debbugs.gnu.org id=B50462.16311332113532 (code B ref 50462); Wed, 08 Sep 2021 20:34:01 +0000 Original-Received: (at 50462) by debbugs.gnu.org; 8 Sep 2021 20:33:31 +0000 Original-Received: from localhost ([127.0.0.1]:33650 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mO4GA-0000ut-TS for submit@debbugs.gnu.org; Wed, 08 Sep 2021 16:33:31 -0400 Original-Received: from mail-wm1-f42.google.com ([209.85.128.42]:37793) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mO4G9-0000uf-Er for 50462@debbugs.gnu.org; Wed, 08 Sep 2021 16:33:29 -0400 Original-Received: by mail-wm1-f42.google.com with SMTP id c8-20020a7bc008000000b002e6e462e95fso2562391wmb.2 for <50462@debbugs.gnu.org>; Wed, 08 Sep 2021 13:33:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Y6CWJ6S3b61LHiVxEp7rx3Jv02mq/3g20kv4TZs211Y=; b=UtMX/94LvZMmorHVLbrRJfbuB3j9SqbCm0fDGQ3yu0bllZgVMSNLqb2vyIKc0oll5m 4ELSNpJAdOTS8/QwJzUHjTCpnFrJpZuO+upTBg8q1DwdfJD0Pw85PA19atAuXuUar64t qoNc5GeKWXav8j8lTqdJKgK8OygEdlMOuYX8k+GhS3cXMLkjIZ0kOGvPSz4r1/KC54to Q9NWzZBdin0KfZkQtrAYWhgIGA3TqBFmt9C3rNY9QiepR+mo4VnUZ87ZH9ZytehNH6VJ lQGUrtsRkreGiRmpestO1Mx3dGooOTWbGjFtOVdb6f5HTWWfzXdk1sVYTJdVis2dYTRX QHJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Y6CWJ6S3b61LHiVxEp7rx3Jv02mq/3g20kv4TZs211Y=; b=tQNcGwYPbjtDxbZ8V4z+rVs8yeY2LMeTipGHzvvth7z4UL6XyD+S/5b4JEwDP6VzN+ XOlaplKtd9QyagQlDDPFdQ1SiCT3HcIhbdMk2fe7dwe73yJK4gxtdeC9q6yYSNcrW9wZ xdwwuferI35/92FSFQjt9oLV8dXA6fd7AudXjO6+NsWt2pQIhyMgZNWjo/5cafOEMDaf EH4dFJPno3OsLVI2zSNw/yJLHDMS+4CBkCnNwpBhW1+Zq2UfiNFbKEeLGWF7Mz7La7vO tx+v0NKZyGSlHNH09kMk2eR1IBuLOxtpS/BENUjHBzJpnM/CXFN4PS9wM/4JqrCdR5A8 v4xg== X-Gm-Message-State: AOAM532Fu9KzTWxdpRSHxtcYuqCgUPhXOSs2/Gv3sgHxf1Uy3CD58hF/ l/+x0BEm0xMNv/LY7M2thXX0Wl4aXey8u70LlXs= X-Google-Smtp-Source: ABdhPJyrkhh70WHd5FJfv5k6mMLvmabcnzpLC6mRLOzDhIDYiLr1km/i49/VjoAI9unkjItsbZUT/mmXJyK21lXsD/0= X-Received: by 2002:a05:600c:21cd:: with SMTP id x13mr5383946wmj.20.1631133203113; Wed, 08 Sep 2021 13:33:23 -0700 (PDT) In-Reply-To: <83mtomlt4j.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:213863 Archived-At: --000000000000272aa005cb81cb3e Content-Type: text/plain; charset="UTF-8" >So two frames from two separate emacsclients are always involved? And >you need to switch from one client to another and back? Two tty's & emacsclients or more are used: (In X org, I open 2 workspaces. Each has an xterm.) tty1> emacsclient -t /home/rds (showing dired) visit .bashrc (it has lots of strings from aliases) switch to tty2 tty2> mc (run Midnight Commander) edit .Xesources ($EDITOR=emacsclient -t) It looks fine. switch to tty1. .bashrc looks OK. switch to tty2 edit more files in my tree randomly with emacsclient. switch to tty1. All OK? yes. back to tty2. keep repeating this cycle. Eventually, tty1 will lose its string display. On Wed, Sep 8, 2021 at 1:17 PM Eli Zaretskii wrote: > > From: RDS > > Date: Wed, 8 Sep 2021 13:05:59 -0700 > > Cc: larsi@gnus.org, 50462@debbugs.gnu.org > > > > >OK, so please describe again, in as much detail as you can, what do > > >you do with Emacs between correct display and incorrect display. You > > >said you switch to another buffer and return, but could you tell more? > > >Just switching to another buffer and back immediately triggers that? > > >Or something else is needed? > > That is indeed the tough part. I have yet to find a definite repeatable > pattern that induces the bug. But, I now > > usually arrive there in a few minutes of activity with two emacsclients > -t in use. > > > > Switching back & forth immediately will not do it. At least one client > is loading / unloading various files before > > switching back to other client. Take a look again at the original post > for more of these general actions I use. > > So two frames from two separate emacsclients are always involved? And > you need to switch from one client to another and back? > --000000000000272aa005cb81cb3e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
>= ;So two frames from two separate emacsclients are always involved?=C2=A0 An= d
>you need to switch from one client to another and back?
<= div class=3D"gmail_default" style=3D"font-size:large">Two tty's & e= macsclients or more are used:
(In X org, I open 2 workspaces. Each has an xterm.)
tty1> emacsclient -t= /home/rds (showing dired)
visit .bashrc (it has lots of strings from aliases)
switch to tty2
tty2> mc (run Midnight = Commander)
edit= .Xesources ($EDITOR=3Demacsclient -t)
It looks fine.
switch to tty1.
.bashrc looks OK.
switch to tty2
edit more files in my tree randomly with emacsc= lient.
switch t= o tty1. All OK? yes. back to tty2.
keep repeating this cycle. Eventually, tty1 will lose = its string display.


<= /div>








On Wed, Sep 8, 2021 at 1:17 PM Eli Zaretskii <eliz@gnu.org> wrote:
> From: RDS <rds1944@gmail.com>
> Date: Wed, 8 Sep 2021 13:05:59 -0700
> Cc: larsi@gnus.org= , 50462@debb= ugs.gnu.org
>
> >OK, so please describe again, in as much detail as you can, what d= o
> >you do with Emacs between correct display and incorrect display.= =C2=A0 You
> >said you switch to another buffer and return, but could you tell m= ore?
> >Just switching to another buffer and back immediately triggers tha= t?
> >Or something else is needed?
> That is indeed the tough part. I have yet to find a definite repeatabl= e pattern that induces the bug. But, I now
> usually arrive there in a few minutes of activity with two emacsclient= s -t in use.
>
> Switching back & forth immediately will not do it. At least one cl= ient is loading / unloading various files before
> switching back to other client. Take a look again at the original post= for more of these general actions I use.

So two frames from two separate emacsclients are always involved?=C2=A0 And=
you need to switch from one client to another and back?
--000000000000272aa005cb81cb3e--