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 13:34:06 +0100 [thread overview]
Message-ID: <CALR_T9CVNkFR9tH28Yowx1afEbitrWR8jyYp8icEBampxgDyBw@mail.gmail.com> (raw)
In-Reply-To: <83y31kfumo.fsf@gnu.org>
On 29/06/2019, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Sam Halliday <sam.halliday@gmail.com>
>> Date: Sat, 29 Jun 2019 13:14:01 +0100
>>
>> SMIE (via a `indent-for-tab-command') does not request forward tokens
>> from the lexer when point is at `point-max'.
>>
>> This might sound like a strange bug report: why should smie expect
>> there to be any tokens when it is already at point-max? The answer is:
>> virtual tokens. For example, Haskell may have many closing curly
>> brackets that live at the end of the buffer.
>
> ??? There can be noting at point-max, as that position is beyond the
> last buffer position. Did you mean the position just before that? Or
> am I missing something here?
>
I mean at point-max.
Consider this layout algorithm
https://gitlab.com/tseenshe/haskell-tng.el/blob/tng/haskell-tng-layout.el
and this lexer
https://gitlab.com/tseenshe/haskell-tng.el/blob/tng/haskell-tng-lexer.el
that can continue to produce tokens even when the point is at the very
end of the buffer.
e.g.
input https://gitlab.com/tseenshe/haskell-tng.el/blob/tng/test/src/layout.hs
with layout https://gitlab.com/tseenshe/haskell-tng.el/blob/tng/test/src/layout.hs.layout
just tokens https://gitlab.com/tseenshe/haskell-tng.el/blob/tng/test/src/layout.hs.lexer
note the trailing } that exists at the very end of the file. SMIE
always misses this.
next prev parent reply other threads:[~2019-06-29 12:34 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 [this message]
2019-06-29 12:42 ` Eli Zaretskii
2019-06-29 12:51 ` Eli Zaretskii
2019-06-29 13:01 ` Sam Halliday
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_T9CVNkFR9tH28Yowx1afEbitrWR8jyYp8icEBampxgDyBw@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.