[Danthewaann]

Fixes #11

The ordinal value should be the same as the display value to support fuzzy search.

I also added some extra info (mark character and line number) to each entry to make them more unique incase you have multiple marks set in a single file e.g. A:/Users/me/Workspace/notes.md:1.

[fnune]

Looks good to me, but would appreciate the legibility change if it does work. You can merge once that's done or you find it doesn't work the way I suggested.

[fnune]

Looks like I added tests for this 👀 unexpected.

            Passed in:
            (string) 'A'
            Expected:
            (string) 'A:/tmp/nvim-recall-test-47775321633.txt:1'

[fnune]

@Danthewaann before we merge (and sorry about backtracking): isn't this an absolute path? Should we default to a path relative to Neovim's content root path?

[Danthewaann]

@Danthewaann before we merge (and sorry about backtracking): isn't this an absolute path? Should we default to a path relative to Neovim's content root path?

Do you mean instead of creating test files under /var we should create them in a tmp folder in the current working directory instead?

[fnune]

I'm suggesting a change in the actual functionality: instead of showing A:/Users/me/Workspace/notes.md:1 we should show a relative path to the content root, e.g. if Neovim was launched in /Users/me/Workspace we would show A:notes.md:1.

[Danthewaann]

Would doing this break global marks for files that are outside of the directory where neovim was launched? We could check if each file is relative to the current directory before converting it to a relative path. If a file isn't relative to the current directory we still render it as an absolute path so nothing breaks?

[Danthewaann]

@fnune I've pushed up commit 296cacc which include the changes to support rendering relative and absolute filenames for marks in telescope. Let me know if it looks reasonable.

[fnune]

Lints are failing, but once that's good let's merge?

[fnune]

Thanks @Danthewaann !