From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: uzibalqa Newsgroups: gmane.emacs.help Subject: Re: Words with spaces highlighted in elisp-mode comments Date: Thu, 20 Jul 2023 11:47:40 +0000 Message-ID: <8ADlKavHDtxrJCESAqF033FMxAQWk1LFM6_dZHM59eCWdqWQBo_xoke12JrquaHDv90D9rAbLj-KQGJUEMiHaVUqv2ko6VDxPoj6UWV_5tE=@proton.me> References: <87edl7h2t6.fsf@dataswamp.org> <87wmywg1bx.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1746"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: Emanuel Berg Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jul 20 13:48:40 2023 Return-path: Envelope-to: geh-help-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 1qMS99-0000Dk-VP for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 20 Jul 2023 13:48:40 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qMS8a-0004WA-A7; Thu, 20 Jul 2023 07:48:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qMS8X-0004UR-K0 for help-gnu-emacs@gnu.org; Thu, 20 Jul 2023 07:48:02 -0400 Original-Received: from mail-4324.protonmail.ch ([185.70.43.24]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qMS8S-0008Jd-GE for help-gnu-emacs@gnu.org; Thu, 20 Jul 2023 07:48:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1689853673; x=1690112873; bh=2i+h+3Myfz0liF211sy3J+OOCv6oat2rsWaZx94UMkU=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=DMBpR1QhKx7oeL8mfWjb8uLcB6n82liVTSJbNC7NLkE22OmMJNa6NlQYtYvfFogSl Jdl11qNdK9jVjtrVSQbgdI3ZFVWFPy6euVTLwWm7LFA88DGukFUvWlw8Hsu2L5tUSd m1axGTCCWaR+VtZU9DHgsvKox2+Kx0ub6+p3hTIRFNPhmCB9W0xIlxzTUExn3nuRt5 zufJ7RXTrCn3UN7sJXgz1UMPIGWSE4MB3qF2rSr99/91D0TrqjwfMPbW2iaOHpht1n GLneONqlIRZ+aC8UtD76vEURmchsYjLmYy6okvFBGV9PHXVlzkjvLTMehJGUJdn8R5 zkE/Bw11mPaWw== In-Reply-To: <87wmywg1bx.fsf@dataswamp.org> Feedback-ID: 52887082:user:proton Received-SPF: pass client-ip=185.70.43.24; envelope-from=uzibalqa@proton.me; helo=mail-4324.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:144350 Archived-At: ------- Original Message ------- On Wednesday, July 19th, 2023 at 1:02 PM, Emanuel Berg wrote: > uzibalqa wrote: >=20 > > > > comments, words within single quotes get highlighted. > > > > It would be beneficial if arbitrary text is also > > > > highlighted within single quotes (e.g. text with spaces). > > >=20 > > > I don't understand what 'ooh' and 'ooh aah' means in Elisp, > > > do you? > > >=20 > > > But it is clear the oohs and the aahs are treated > > > differently by Emacs as 'ooh' gets the > > > `font-lock-constant-face' and with the whitespace, as you > > > say, it doesn't. > > >=20 > > > You can evaluate 'ooh' (into ooh) but not use it in code, > > > 'ooh aah' cannot be evaluated. > >=20 > > Highlighting some text in comments would be beneficial. >=20 >=20 > But comments are already font locked into > `font-lock-comment-face' (there is also a` font-lock-comment-delimiter-fa= ce', IMO it is overkill to > have that in another color than `font-lock-comment-face'). I do not see the usefulness of colouring the comment delimiter separately = (because that affects all comments in the same way, no distinguishing feature whatsoever = ). We can keep highlighting with a back-quote for things that can be evaluated (e.g. `some= thing') and=20 use single-quote for more general case that allows spaces (e.g. 'this and t= hat'). We should not use multiple comment characters (e.g. ;;; Something) because = those are for outlines - something of a completely different orthogonal purpose. =20 > I don't see why 'ooh' within a comment should be colorized any > other way than the comment, since that syntax don't denote > anything in Elisp. If you intend to use it as labels, and to > put them aside as a special color, I'd say there are better > ways to do that, namely stack semi-colons in different numbers > denoting different things, so that, for example >=20 > ;; this is a general comment <-- one face >=20 > (setq one 1) ; don't do that <-- comment that refers to one line >=20 > ;;; this is a LABEL, as seen in Lisp packages <-- one face for that > (code (code ...) > (code (code ...) >=20 > This would also be safe to implement because if someone didn't > like it, it could be default be set so that all those Lisp > levels of comments initially were set to the same color. >=20 > -- > underground experts united > https://dataswamp.org/~incal