-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hightlight on wrong location #60
Comments
Hi!,
thank you! |
Of course, I should have included those in first place - I got the same results just now, trying to find from results of 'ls' right after opening Hyper. The copy of .hyper.js below. // Future versions of Hyper may add additional config options, module.exports = {
}; |
@kangho99 thanks for the quick response, i'll be trying to reproduce the bug using your config in the following days. |
the issue is in containers.js file inside the function getLine.
when white space is encountered (eg. 'Download Document') the function would the string without the whitespace I'DownloadDocument'). I looked up the xterm.js documentation, there is a function called translateToString() for BufferLine. By directly returning the result from translateToString() the correct location is highlighted. I have opened a PR to fix the issue #70 |
#70 has been merged and published to npm (hyper-search@0.3.1). @kangho99 please let us know if u still have issues. Thank you @samuelyeungkc !!! 🍺 |
I don't see the issue after update. Thank you both for nice plugin and quick fix! @jaanauati @samuelyeungkc |
Like the image suggests, the issue is very straightforward.
Search result highlights wrong location on some cases.
It was a clean, first hyper install, and hyper-search was the first plugin installed.
The text was updated successfully, but these errors were encountered: