On Sat, Dec 30, 2023 at 7:16 PM João Távora wrote:
> > On the face of things, remember.el does not comprise a huge amount of
> > code, and I don't see why the above two features couldn't be retrofitted
> > into it.
>
> Seems like the first one could be done with narrowin
On Sat, Dec 30, 2023 at 5:21 PM Stefan Kangas wrote:
>
> Ihor Radchenko writes:
>
> > The refactoring de-coupled what used to be org-remember.el into
> > completely rewritten org-capture.el that added important features that
> > could not be implemented within remember.el framework:
> >
> > 1.
On Mon, Dec 11, 2023 at 11:54 PM Dmitry Gutov wrote:
>
> On 12/12/2023 01:48, João Távora wrote:
> > On Mon, Dec 11, 2023 at 11:41 PM Dmitry Gutov wrote:
> >> On 12/12/2023 01:35, João Távora wrote:
> >>> Or maybe say what the ruby-mode imenu backend
> &g
On Mon, Dec 11, 2023 at 11:41 PM Dmitry Gutov wrote:
>
> On 12/12/2023 01:35, João Távora wrote:
> > Or maybe say what the ruby-mode imenu backend
> > does?
>
> Juri just posted a long example of what ruby-mode does (and ruby-ts-mode
> too) in his last message in th
On Mon, Dec 11, 2023 at 11:23 PM Dmitry Gutov wrote:
> >> But if the LS will produce distinct strings, good.
> > All imenu backends, at least all the ones I've seen, produce
> > trees, not strings.
>
> There are exceptions, like the previously mentioned one.
What is the imenu backend that
On Mon, Dec 11, 2023 at 7:24 PM Dmitry Gutov wrote:
>
> It's no invention, it's docstring syntax for reference to a method.
In Ruby right?
> But if the LS will produce distinct strings, good.
All imenu backends, at least all the ones I've seen, produce
trees, not strings. If you collect all
On Mon, Dec 11, 2023 at 7:27 PM Ihor Radchenko wrote:
> > Indeed, it's unfortunate that imenu--make-index-alist and imenu--index-alist
> > are named as internal.
>
> Should they be renamed to `imenu-make-index-alist' and `imenu-index-alist'
> then?
Maybe, but it's much more urgent IMO to
On Mon, Dec 11, 2023 at 5:43 PM Dmitry Gutov wrote:
> > is still usable even without special characters like "#".
>
> Until a class contains both an instance and a class method with the same
> name, I suppose.
If that happens, the LS will have to provide to distinct paths
to these two distinct
On Mon, Dec 11, 2023 at 5:21 PM Juri Linkov wrote:
> > By the way, this seems to be exactly what the breadcrumb-jump command
> > in my breadcrumb.el package does. Goes reasonably well with a flex/fuzzy
> > completion style.
>
> It would be great to have some form of breadcrumb-jump in imenu.el
On Sat, Dec 9, 2023 at 5:39 PM Juri Linkov wrote:
> menu1
> sub-item1
> sub-item2
>
> could be flattened to
>
> menu1 -> sub-item1
> menu1 -> sub-item2
By the way, this seems to be exactly what the breadcrumb-jump command
in my breadcrumb.el package does. Goes reasonably well
41329af259273fe604dc4f8669fbd8a
> git bisect bad bd95d66ae97f3dcfe73b972de935e27e434e49be
> git bisect bad 5b45c269cda09fe46e110adb6f6767040f4ade59
> git bisect good 0e774d4f355b4f12a625da5ca9602d1ba876bcc1
> 5b45c269cda09fe46e110adb6f6767040f4ade59 is the first bad commit
> ```
>
>
>
--
João Távora
gt;
> I appreciate if the problem would be fixed.
Are you familiar with `git bisect`? It's a bit of work, but it usually points
to the culprit commit. Emacs history is very good. I don't have
time for this right now, but maybe you have? It's a question
of compiling Emacs methodically and then testing your recipe
each time.
João Távora
> I apologize that the file I posted is NG. Please try the following file
> as shown below.
Thanks, now I did reproduce... something. I get the "Marker does not
point anywhere" error you describe, but also mentions to other broken
functionality, not only the "antiblink":
Error in
João Távora writes:
> I'll keep investigating: I still don't know which marker the message
> is referring to. It could be antiblink's marker, but it could be
> anything else.
>
> João
I've now reproduced after setting
(setq jit-lock-antiblink-grace nil)
Which turns of
14 matches
Mail list logo
