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: Sat, 22 Jul 2023 13:21:11 +0000 Message-ID: <4DhjKANIbFgZWMXo6XhGnchGcbS3MrmPJZZKIJpQm1xbsUDq7jYnCIl7fNBXTQMpB8nN36XJPIdGhNLO9DvjvUC3a4UQEFZNiQsLdLRtnCU=@proton.me> References: <87edl7h2t6.fsf@dataswamp.org> <87wmywg1bx.fsf@dataswamp.org> <8ADlKavHDtxrJCESAqF033FMxAQWk1LFM6_dZHM59eCWdqWQBo_xoke12JrquaHDv90D9rAbLj-KQGJUEMiHaVUqv2ko6VDxPoj6UWV_5tE=@proton.me> <87tttwfptt.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="7887"; 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 Sat Jul 22 15:22:22 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 1qNCYv-0001l2-US for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 22 Jul 2023 15:22:22 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qNCYJ-0001hY-CU; Sat, 22 Jul 2023 09:21:43 -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 1qNCYH-0001hB-Ir for help-gnu-emacs@gnu.org; Sat, 22 Jul 2023 09:21:41 -0400 Original-Received: from mail-4318.protonmail.ch ([185.70.43.18]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qNCYD-0006yL-Au for help-gnu-emacs@gnu.org; Sat, 22 Jul 2023 09:21:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=ypo2gkbg5fbzbbtcqaadlq6ymi.protonmail; t=1690032087; x=1690291287; bh=dVTJjuwRmwc8UdA2tKyejg2R8QInTDWMeDTxWVN0994=; 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=AvW+jmD659dyf7FozaZjJ1BhSzM9uu1vrA4hBlLD8JPe7D9FaKSdjHoNo2Jqwo/1R btAbfj1V/ecC3MuvqYWhiQxLP+urY/rwYJyKmYqNULR9CCelr0cB1kAfzOskVvfipA JZWoHa4UIWmvYk9YFc6Ejl+zgYobQQSpYG1bFhJ0BKfwQnsxOEci0VJQiRIfpZEgvc 8f5C3hyzBOgv72gxJQF+BgS+aaZQzRIu+XDUmoY7zLBcnHH/9U4td9vkOJNNQXIdg+ PTEBv2SZ6p0AsrSCHk14VJXQCadewvpQg4TuzhAujlE7q/wltgL5a5XaDiDff81fKa YzJ04UvFOJoqw== In-Reply-To: <87tttwfptt.fsf@dataswamp.org> Feedback-ID: 52887082:user:proton Received-SPF: pass client-ip=185.70.43.18; envelope-from=uzibalqa@proton.me; helo=mail-4318.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:144382 Archived-At: ------- Original Message ------- On Saturday, July 22nd, 2023 at 6:00 PM, Emanuel Berg = wrote: > uzibalqa wrote: >=20 > > > But comments are already font locked into > > > `font-lock-comment-face' (there is also a` > > > font-lock-comment-delimiter-face', IMO it is overkill to > > > have that in another color than `font-lock-comment-face'). > >=20 > > I do not see the usefulness of coloring the comment > > delimiter separately (because that affects all comments in > > the same way, no distinguishing feature whatsoever ). >=20 >=20 > Indeed, I think all comments should be of the same color, > including the delimiters. >=20 > > We can keep highlighting with a back-quote for things that > > can be evaluated (e.g. `something') >=20 >=20 > Agreed, that is the exception that proves the rule. I could > also think of hyperlinking them to the help, as has been > suggested not that long ago. In ERC it is already like that > BTW, and here is some more work on that: >=20 > https://dataswamp.org/~incal/emacs-init/erc/erc-man.el >=20 > https://dataswamp.org/~incal/emacs-init/erc/erc-show-modes.el >=20 > But putting point at the beginning of `something' and doing` C-h f' isn't= that much of a deal, which is the reason I think > no one has cared about it enough to do it. >=20 > But I like all integration things, big and small, so why not. It is a very good strategy, and also of that school. > Here it should be noted that they already get > `font-lock-constant-face', if it sounds here like nothing at > all happens to the poor things. >=20 > > and use single-quote for more general case that allows > > spaces (e.g. 'this and that'). >=20 >=20 > But what do that express? What's the intended usage? Can you > provide a piece of Elisp, where you use that proposed syntax > for us to see? Besides using comment for descriptive purposes, I use it for FIX-THIS, IMPROVE-THIS, DEVELOP-THIS, PENDING. ;; PENDING ;; 'OMS GMBL' ;; 1st Fail Y Down ;; 2nd Fail P Down if P not -2.5 to +2.5=20 ;; 'FF MDM I/O Error' ;; I/O Reset =20 This is an example for elisp but my intention is to have this for any language (C, C++, Fortran). For these types of tasks, colouring will enhance the visibility of these phrases and make=20 them stand out, immediately close to the section of code of=20 relevanece. It is not the routine thing for everybody, but colouring within comments has benefits for things besides general description. > > We should not use multiple comment characters (e.g. ;;; > > Something) because those are for outlines - something of > > a completely different orthogonal purpose. >=20 >=20 > As long as it has a purpose, it can be font locked in > a distinguished way. If it should, in this case, is another > thing, but it could, and it wouldn't be wrong to do. But if it > should, I don't know, especially since comments in a uniform > color simply looks much better. Comments in uniform colour has the advantage that one can change the intensity of the text in some situations. =20 So perhaps use font lock on the comments as you say. One just need to be careful because some modes might reset whatever I try to do. > -- > underground experts united > https://dataswamp.org/~incal