-
Notifications
You must be signed in to change notification settings - Fork 7
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
custom ebuku-database-path issue on Windows #31
Comments
Hmm. The error
So we need to check your locale settings, and in particular, the value of the LC_COLLATE environment variable. How are you running Emacs - natively, or via WSL? i'm not a Windows user myself, but if you're running Emacs natively, you could perhaps try either starting PowerShell and running If you're running Emacs via WSL, please run At any rate, please share all the output here. |
Hi, thank you for your timely reply.
I am using Chinese as my primary language. |
Yes, i cloned the Git repo: https://savannah.gnu.org/projects/emacs
Okay. Usually LC_ALL includes LC_COLLATE, but i don't know whether this is true on Windows. As a test, what happens if you instead set LC_ALL to zh_CN.UTF-8? Does that make any difference? |
I made the change but the error message persists. |
Thanks for checking that. Hm. Could you please enable (i don't know if the problem is an incorrect assumption in my code, or in Emacs' code, as you suggested might be the case.) |
The full trace is here
So the path utility is functional and works well. |
Thanks for that. However, i'm a bit confused. In your original comment, you wrote that the error message was "invalid string for collation: Invalid argument"; here, however, the trace shows the error message to be "(args-out-of-range "1884. Welcome to Comprehensive Rust 🦀 - Comprehens..." 15862 15893)" Are you now unable to reproduce the circumstances that resulted in the "Invalid string for collation" message? i can certainly work on the issue with emojis, and that issue might actually be related to the "Invalid string for collation" issue, but it would help me to know whether the latter issue still exists, or if it was actually fixed by setting LC_ALL to If you can no longer reproduce the "Invalid string for collation" issue with your system, can you please let me know if it returns if you change LC_ALL back to |
Thank you for your efforts. |
Ah, okay - no worries, i sometimes forget to that myself, so i understand. :-) Okay, i'll work on the emoji problem; i'll open a new issue for it, and then close this one. |
Opened new issue as #32, closing this one. |
Hi, I am trying ebuku on Windows.
I put the absolute path for my database file in the ebuku-database-path variable with
(setq ebuku-database-path "C:/Users/uname/.local/share/buku/bookmarks.db")
But then I get the error message "invalid string for collation: Invalid argument".
The path is valid, and when I call the
buku --db C:/Users/uname/.local/share/buku/bookmarks.db --print
, it works fine.Also, when I try some address alternatives like
(setq ebuku-database-path "~/.local/share/buku/bookmarks.db")
There will be new directory created under the working directory, like
D:\pwd\~\.local\share\buku\bookmarks.db
I guess that's because buku will create a new db if you provide some valid path.
And my suspicion is that the
substitute-in-file-name
function is the cause, maybe this function don't handle the Windows path properly.The text was updated successfully, but these errors were encountered: