From: Sam Halliday <sam.halliday@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36432@debbugs.gnu.org
Subject: bug#36432: 26.2; SMIE does not request forward tokens when point is at point-max
Date: Sat, 29 Jun 2019 14:01:52 +0100 [thread overview]
Message-ID: <CALR_T9A23zBOPn3NieGH4O51M8EBHnWkh5ABnjhWursfBxJvyQ@mail.gmail.com> (raw)
In-Reply-To: <83v9woftc4.fsf@gnu.org>
On 29/06/2019, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sat, 29 Jun 2019 15:42:27 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: 36432@debbugs.gnu.org
>>
>> How would Emacs know this is the case? Why don't you also override
>> point-max to make it consistent with those illusory characters?
>
> Or actually insert those characters at EOB, but make them invisible?
I think I'd like to avoid doing that unless I do it for all of the
virtual tokens. I don't know how to do that without it impacting the
underlying source code. Is there more documentation about doing it
that way? It'd be a drastic change in how the lexer is written.
BTW I had a look through smie.el and I can't see anywhere obvious
where (eobp) or (point-max) are called that would lead to the bug I'm
seeing. I'll most likely have to step debug at some point to get to
the bottom of this.
next prev parent reply other threads:[~2019-06-29 13:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 12:14 bug#36432: 26.2; SMIE does not request forward tokens when point is at point-max Sam Halliday
2019-06-29 12:23 ` Eli Zaretskii
2019-06-29 12:34 ` Sam Halliday
2019-06-29 12:42 ` Eli Zaretskii
2019-06-29 12:51 ` Eli Zaretskii
2019-06-29 13:01 ` Sam Halliday [this message]
2019-06-29 13:08 ` Eli Zaretskii
2019-06-29 12:51 ` Sam Halliday
2019-06-29 13:06 ` Eli Zaretskii
2019-06-29 13:13 ` Sam Halliday
2019-06-29 13:43 ` Eli Zaretskii
2019-06-29 21:39 ` Stefan Monnier
2019-06-30 8:50 ` Sam Halliday
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALR_T9A23zBOPn3NieGH4O51M8EBHnWkh5ABnjhWursfBxJvyQ@mail.gmail.com \
--to=sam.halliday@gmail.com \
--cc=36432@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.