From: Alan Mackenzie <acm@muc.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: acm@muc.de, Eli Zaretskii <eliz@gnu.org>, 69684@debbugs.gnu.org
Subject: bug#69684: Functionality of Fbare_symbol has been lost.
Date: Mon, 11 Mar 2024 20:01:06 +0000 [thread overview]
Message-ID: <Ze9jAo8vrfjsiihX@ACM> (raw)
In-Reply-To: <36c94f0a-3a1a-407d-9cef-40a5e8cc35af@cs.ucla.edu>
Hello Paul.
On Mon, Mar 11, 2024 at 00:38:39 -0700, Paul Eggert wrote:
> On 2024-03-10 03:39, Eli Zaretskii wrote:
> > OK, so let's wait for Paul to chime in.
> The problem was that I mistakenly believed the documentation when it
> said that a symbol with position behaves like its bare symbol when
> symbols-with-position-enabled is t. Unfortunately it appears that this
> part of the doc wasn't intended to apply to bare-symbol, so when I fixed
> something else involving bare-symbol I got the semantics wrong.
I think the doc and doc strings were somewhat unclear when it came to
the less obvious cases.
> As penance I installed the attached, which makes a simple code change
> along the lines that you suggested and adds a regression test to help
> prevent this bug from happening again.
Thanks!
> The hardest part of writing this patch was adjusting the documentation
> to match what I think was the intent of the behavior. Alan, if you find
> mistakes in that please let me know.
That might take a little tine. I've broken my right arm, which makes
doing Emacs strenuous work. But I'm sure the patch will work.
It's also worth pointing out that the uses of SWPs are expanding (see
bug #67455), something I've got mixed feelings about, even though I'm
doing the implementation.
> A couple of other things.
> Currently (position-symbol 'x -1) creates a symbol with position where
> the position is negative; is that intended? The documentation says
> positions are nonnegative.
Yes. I think that back when it was being done, there was no convenient
way to exclude -ve numbers.
> Also, more test cases of the symbols with position primitives would not
> go amiss. I'm not a good person to write them, though, as I easily get
> confused by symbols with position.
Yes, I agree here, too.
[ .... ]
--
Alan Mackenzie (Nuremberg, Germany)
prev parent reply other threads:[~2024-03-11 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 23:23 bug#69684: Functionality of Fbare_symbol has been lost Alan Mackenzie
2024-03-10 5:57 ` Eli Zaretskii
2024-03-10 9:21 ` Alan Mackenzie
2024-03-10 10:39 ` Eli Zaretskii
2024-03-11 7:38 ` Paul Eggert
2024-03-11 20:01 ` Alan Mackenzie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Ze9jAo8vrfjsiihX@ACM \
--to=acm@muc.de \
--cc=69684@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).