From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: Algorithm in electric-pair--unbalanced-strings-p unsuitable for CC Mode Date: Wed, 3 Jul 2019 14:31:58 +0100 Message-ID: References: <20190702131632.GA30597@ACM> <20190702160410.GB30597@ACM> <20190702182811.GC30597@ACM> <20190703105804.GA11238@ACM> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000060a4fb058cc6e3ee" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="212683"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 03 15:44:09 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hifYO-000spI-Bu for ged-emacs-devel@m.gmane.org; Wed, 03 Jul 2019 15:44:08 +0200 Original-Received: from localhost ([::1]:36054 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hifMw-0003MG-OV for ged-emacs-devel@m.gmane.org; Wed, 03 Jul 2019 09:32:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41662) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hifMq-0003Lk-Er for emacs-devel@gnu.org; Wed, 03 Jul 2019 09:32:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hifMo-0006oJ-SU for emacs-devel@gnu.org; Wed, 03 Jul 2019 09:32:12 -0400 Original-Received: from mail-io1-xd30.google.com ([2607:f8b0:4864:20::d30]:36627) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hifMo-0006nx-N3 for emacs-devel@gnu.org; Wed, 03 Jul 2019 09:32:10 -0400 Original-Received: by mail-io1-xd30.google.com with SMTP id h6so4802164ioh.3 for ; Wed, 03 Jul 2019 06:32:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mb0JeLusP5wPOqNSPn4fjy9Fnu/+Ra7p1mRJb5etdC8=; b=D9LcxdrNBCBqYSZfBNJmGrkxRWjtIK9DpO37DLHm+e3elNfvRwfgKSME92zH1s3I9M xq4mFzgCksuXtGdSIHQluJvCnEYX6qSy+iTyJjWEldrsW+miX6hzyrpJ9rQLUVJOqx5x VU95rdcDKJZKfvwCMbnvdU7TCO06chqAiA1/jyUzAVNMIYJ7M/HKoUKrHkjV/mIRkCul SHdGOen3Jf6isGTviMlSWRVlYZJlOh342L1R9hCr4Bs4SZw7XZ280ltZuFkrnlC+AkCf XW+TQn3f+QuXMstpJYY72nnGpNLP6DdtxUaBXoYzgYWe0re4Eygx90z9KaGcDeMYxnGW wrdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mb0JeLusP5wPOqNSPn4fjy9Fnu/+Ra7p1mRJb5etdC8=; b=uI1jhyC7KFsjcVmOoB/zX4kdweODkpym1/iplt9eDoUgJ+UvZJOs1vIcRGsiyxVMks KQEwP3VCszct/F/j0OnQ7EGthanNWN+Cr0YCCMX6PoYmk58Pw6p6wmEgfx3MhXHNnBPi W/s8t/h3gSgD5oOtQshTRIy3WzFkcVhbucEez90fRVm7zzKcv1qgM89NsPbx8wg+fCN4 labXUdOi8oyyvpRnfDUnQh27X6OXjKKQqFY8N+AvQjJ75a2L9IEYXy1bQ1Iux6j3d1vs bsjyXzhRTxV8LV/uUqckdhK/YzkvxD4Wk00SuiConYoImg07FNfURiXqb67dZC6UQ1kp LO6A== X-Gm-Message-State: APjAAAWrDbHa1k8pGLzjMGcqPDl88gv8KLb8cXbmTBb5hTPKln73vN8P e8NPdYyySR/qeVkLnQVGIduOu7Cinhr9KkkK3XGOqjlrkAI= X-Google-Smtp-Source: APXvYqylpEsdlEO8hOX6R4bm0xDzvVHitY3xDwMvxoXb65+8o+na/AavNv+BcVxgC4xkfZsIcxfARrYMc+jhn7SY89Y= X-Received: by 2002:a05:6638:3d6:: with SMTP id r22mr3756608jaq.71.1562160729726; Wed, 03 Jul 2019 06:32:09 -0700 (PDT) In-Reply-To: <20190703105804.GA11238@ACM> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::d30 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:238328 Archived-At: --00000000000060a4fb058cc6e3ee Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jul 3, 2019 at 11:58 AM Alan Mackenzie wrote: > I'm fully aware it's a git commit hash. Funnily enough, I don't > memorise such hashes, so if you wish to draw my attention to some > commit, please have the decency to give me its date, Look I'm not being indecent, Alan. Stop this. just `git show fe06f64b`, and move on. > You're complaining that a dubious trick borne of incorrectness no longer > works. Why are you dictating what I can and can't use that to select the region between the two quotes? I write my text, fill the pargaph, select it with C-M-u C-M-SPC (nicely chained "u" and SPC) and then I C-S-% to put in the backslahes. You may well consider it a "trick" and "dubious" and "stupid", but it's the way I work. Anyway, tell me, out of curiosity, how do you do it? How do you create "this \ text, \ for \ example" ? > I think, perhaps, you encounter such broken strings extremely rarely, > and you're making a big song and dance over a relatively minor matter. No, it's pretty routine, really. Help blurbs in c++ and multi-line shell commands in Makefiles, from the top of my head. C-M-stuff is so second nature in Emacs I don't even think when I'm using it, I just expect it to work. I have user commands that use the underlying functions, too. By the way C-M-u is backward-up-list, not up-list as I stated earlier (but both are broken, I think). > can you suggest some other mechanism by > which CC Mode can create the required font-locking? If you can, and > it's workable, we all win. No, I can't, but I've asked others to chime in. I would personally do it (in fact I already do do it) via flymake-mode. If you don't like that, sorry. > C-M-u and C-M-f aren't broken. You just have unreasonable expectations > of them. If you call unreasonable expectations gained from many years of using Emacs in a variety of modes, including, up to very recently, cc-mode, then clearly there's little point in proceeding this argument. > > > No, you'd be cleaning up your code, to conform with the reality that in > > > 2019 major modes use syntax-table text properties. Features from CC > > > Mode have a habit of migrating to the Emacs core. > > It's not "my" code and I won't be bullied into making changes I don't > > agree with. > If anybody's the bully around here, it's not me. I found a minor bug in > electric-pair-mode, diagnosed it, and reported it. You believe this is a bug in e-p-m. It's certainly your right to believe that. I believe it's a bug in cc-mode. Do I have that right, too? Good. Shall I open a bug report to joust with it, or is saying so enough? I'd much rather the conflicting feature be disabled or made optional in cc-mode, so that not only e-p-m starts working but also C-M-u, C-M-f, etc. If don't agree, find a small enough solution that fixes e-p-m, propose it here, then find a consensus that overrides my opinion, it happens all the time, won't hold it against you or anyone else, good luck. -- Jo=C3=A3o T=C3=A1vora --00000000000060a4fb058cc6e3ee Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jul 3, 2019 at 11:58 AM Alan Mackenzie <acm@muc.de> wrote:

> I'm fully = aware it's a git commit hash.=C2=A0 Funnily enough, I don't
>= memorise such hashes, so if you wish to draw my attention to some
> = commit, please have the decency to give me its date,

Look I'm no= t being indecent, Alan. Stop this. just `git show fe06f64b`,
and move on= .

> You're complaining that a dubious trick borne of incorrec= tness no longer
> works. =C2=A0

Why are you dictating what I c= an and can't use that to select
the region between the two quotes? I= write my text, fill the pargaph,
select it with C-M-u C-M-SPC (nicely c= hained "u" and SPC) and then
I C-S-% to put in the backslahes.= You may well consider it a "trick"
and "dubious" an= d "stupid", but it's the way I work.

Anyway, tell me, = out of curiosity, how do you do it? How do you create

"this \text, \
for \
example"

?

> I think, perhaps, = you encounter such broken strings extremely rarely,
> and you're = making a big song and dance over a relatively minor matter.

No, it&#= 39;s pretty routine, really.=C2=A0 Help blurbs in c++ and multi-line shell<= br>commands in Makefiles, from the top of my head.=C2=A0 C-M-stuff is sosecond nature in Emacs I don't even think when I'm using it, I jus= t
expect it to work. I have user commands that use the underlying
fun= ctions, too.=C2=A0 By the way C-M-u is backward-up-list, not up-list
as = I stated earlier (but both are broken, I think).

> can you sugges= t some other mechanism by
> which CC Mode can create the required fon= t-locking?=C2=A0 If you can, and
> it's workable, we all win.
=
No, I can't, but I've asked others to chime in. I would persona= lly do it
(in fact I already do do it) via flymake-mode. If you don'= t like that, sorry.

> C-M-u and C-M-f aren't broken.=C2=A0 Yo= u just have unreasonable expectations
> of them.

If you call u= nreasonable expectations gained from many years of using
Emacs in a vari= ety of modes, including, up to very recently, cc-mode,
then clearly ther= e's little point in proceeding this argument.

> > > No,= you'd be cleaning up your code, to conform with the reality that in> > > 2019 major modes use syntax-table text properties.=C2=A0 Fe= atures from CC
> > > Mode have a habit of migrating to the Emac= s core.
> > It's not "my" code and I won't be bu= llied into making changes I don't
> > agree with.
> If a= nybody's the bully around here, it's not me.=C2=A0 I found a minor = bug in
> electric-pair-mode, diagnosed it, and reported it.

Y= ou believe this is a bug in e-p-m. It's certainly your right to believe=
that. I believe it's a bug in cc-mode. Do I have that right, too? G= ood.
Shall I open a bug report to joust with it, or is saying so enough?=
I'd much rather the conflicting feature be disabled or made optiona= l
in cc-mode, so that not only e-p-m starts working but also C-M-u,
C= -M-f, etc. If don't agree, find a small enough solution that fixes
e= -p-m, propose it here, =C2=A0then find a consensus that overrides my
opi= nion, it happens all the time, won't hold it against you or
anyone e= lse, good luck.

--
Jo=C3=A3o T=C3=A1vora
--00000000000060a4fb058cc6e3ee--