[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#9054: 24.0.50; show source in other window
From: |
martin rudalics |
Subject: |
bug#9054: 24.0.50; show source in other window |
Date: |
Tue, 5 Oct 2021 10:09:48 +0200 |
> It still needs to scan twice because for thing-at-point it should be
> implemented as two functions:
>
> (put 'comment 'beginning-op 'thing-at-point--beginning-of-comment)
> (put 'comment 'end-op 'thing-at-point--end-of-comment)
That should be redesigned in some way, possibly caching the syntax state
together with its 'buffer-modified-tick' when putting the 'beginning-op'.
And I would do the same for strings. If I'm not completely mistaken,
you have to run the 'foward-sexp' from their beginnings there as well.
>> BTW, I've recently seen this
>>
>> Debugger entered--Lisp error: (args-out-of-range #<buffer *Help*> 1 2461677)
>> parse-partial-sexp(1 2461677)
>> syntax-ppss(2461677)
>> context-menu-region((keymap #("Context Menu" 0 12 (hide t))
>> context-menu-map()
>> describe-buffer-bindings(#<buffer *info*> nil)
>> describe-bindings()
>> funcall-interactively(describe-bindings)
>> call-interactively(describe-bindings nil nil)
>> command-execute(describe-bindings)
>>
>> Any ideas as to what could have happened here? I must have been hitting
>> C-h b by accident - as a rule I never call 'describe-bindings' - but
>> 2461677 looks slightly preposterous ...
>
> It seems you still using old source code? Because recently this was fixed
> in event-end to use (window-point).
Maybe. Just that I can't remember working with a buffer that large ...
martin