Skip to content
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

embark-export of consult-global-mark fails #107

Closed
hmelman opened this issue Dec 31, 2020 · 2 comments
Closed

embark-export of consult-global-mark fails #107

hmelman opened this issue Dec 31, 2020 · 2 comments

Comments

@hmelman
Copy link

hmelman commented Dec 31, 2020

I ran consult-global-mark and then used embark-export. Because of the use the xref-location category, I got a buffer in grep mode of my global marks, great. The lines began with FILE:NUM: as you'd expect; note the FILE was just the last component of the name, no directory path info. I then selected a line and hit RET expecting to go there. I got a prompt "Find this grep hit in: " and I had to select a directory. (1) I found this clunky and wish there was a way that the grep buffer knew the full path of the hit. (2) I entered the proper directory where the file could be found but got an error "No `􀒦hrm-keys.el' in directory ~/elisp/". There seems to be a unicode 0x1004a6 character before the filename which I can't explain. Note a different hit in the same file has a different character 0x10061F in front. I am not sure if this is a consult or embark error but I started here.

@minad
Copy link
Owner

minad commented Dec 31, 2020

Sorry, this is my fault. I will change this back.

@oantolin
Copy link
Contributor

Just so people that land here don't have to go over to oantolin/embark#98: consult-global-mark nor reports category consult-location, and the Embark exporter for that produces a buffer in occur-mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants