You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.The text was updated successfully, but these errors were encountered: