Joe Wicentowski

Not from me, alas. I'm stuck!

The PR linked to that announcement - https://github.com/eXist-db/eXide/pull/189 - was merged and released with that fix. But @wolfgangmm removed the emmet plugin in a later PR - https://github.com/eXist-db/eXide/pull/217. Perhaps some...

@galtm Thank you for the report! This sounds like a bug indeed. It is likely in the upstream project that @wolfgangmm drew on when he [contributed the feature](https://github.com/eXist-db/eXide/commit/3c1f9131dbbe2d8598c0b86ba7cd74e227581cf1). That project,...

Perhaps the results could be deposited in a text field, where we could select & copy ourselves. I find it difficult and fiddly to select results now for copy, as...

I've seen such a thing intermittently too. Have you been able to develop a set of specific steps to reproduce this with your file?

I've also seen this (and have not been able to find a reproducible test). It's definitely a bug. If we can find some way to induce eXide to open the...

Ah, I didn't realize this happens for you *always* and not just *sometimes*. That's quite promising! ;) Could you list detailed steps to reproduce? There are multiple ways to open...

Ah, ok, that makes sense. I wouldn't know how to go about fixing this. But it sounds like you have a possible javascript route in mind?

@nsincaglia The module in eXide that receives the requests from the "Edit > Find in files" command is https://github.com/eXist-db/eXide/blob/develop/modules/search.xq. This module doesn't examine files' **extensions**; rather, it checks the files'...

@nsincaglia Seeing it isn't nearly as useful as having steps I can reproduce on a stock eXist system running locally. Can you craft a set of steps to reproduce this...