From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Confusing doc string of list-or-string at point Date: Sat, 25 Sep 2021 22:03:48 +0300 Organization: LINKOV.NET Message-ID: <87o88ga357.fsf@mail.linkov.net> References: <83a6k3uspt.fsf@gnu.org> <87sfxv2p4e.fsf@mail.linkov.net> <835yururh3.fsf@gnu.org> <8335pvuqfh.fsf@gnu.org> <87tuibyxzd.fsf@mail.linkov.net> <83y27nt9ny.fsf@gnu.org> <87czoz3wm2.fsf@mail.linkov.net> <875yuqpjpp.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5088"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 25 21:17:07 2021 Return-path: Envelope-to: ged-emacs-devel@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 1mUDAZ-0001C5-1s for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Sep 2021 21:17:07 +0200 Original-Received: from localhost ([::1]:50598 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mUDAX-0000Fs-O5 for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Sep 2021 15:17:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51018) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mUD9C-0006po-JK for emacs-devel@gnu.org; Sat, 25 Sep 2021 15:15:43 -0400 Original-Received: from relay10.mail.gandi.net ([217.70.178.230]:41091) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mUD99-0001xn-PZ; Sat, 25 Sep 2021 15:15:42 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by relay10.mail.gandi.net (Postfix) with ESMTPSA id AFD82240008; Sat, 25 Sep 2021 19:15:35 +0000 (UTC) In-Reply-To: (Stefan Monnier's message of "Fri, 24 Sep 2021 13:41:34 -0400") Received-SPF: pass client-ip=217.70.178.230; envelope-from=juri@linkov.net; helo=relay10.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:275479 Archived-At: >> (defun thing-at-point--end-of-sexp () >> "Move point to the end of the current sexp." >> - (let ((char-syntax (syntax-after (point)))) >> + (let ((char-syntax (char-syntax (char-after)))) > > Splitting the work between `char-after` and `char-syntax` means that we > can't obey any `syntax-table` text properties placed on that char. > So I think the above change would be a regression in this sense (tho > I understand it fixes or circumvents a bug elsewhere). No bugs prompted this patch, just noticed the difference between this function and its counterpart thing-at-point--beginning-of-sexp that uses `(char-syntax (char-before))`.