Replies: 2 comments
-
|
Closing in favor of #822 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@theuserbl BTW, you're using Edit without ICU. I recommend not doing that due to the missing features. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am using Kubuntu 25.10.
On it I have run the Linux edit 1.2.0 binary from this github page, the snap package of edit in Kubuntu in version 1.2.1 and a for some days self compiled edit 2.0.0.
The official 1.2.0 binary opens without problems every directory and makes no problems.
The other two opens some directories without problem, but on other directories they abort. Important is not the directory itself. Important are the files in it. I haven't figure out which combination it need. But if some files are not there, they are also unproblemtical opened.
Here an problematical test-directory. I am using PowerShell as default on Linux.

With the official edit 1.2.0 binary it works correct

On Kubuntu the editor is called "msedit". It aborts, when I want to open that directory.

Same with my self compiled version 2.0.0

I have then tried in bash to set RUST_BACKTRACE=1

The result of the program is then

Then I tried it with RUST_BACKTRACE=full

The result was this one

After that I discovered the bnaries with ldd, if they are all loading the same libraries. The both programs which aborts links to an additional file: libgcc_s.so.1

I don't know why the edit on Kubuntu and my self compiled edit abort in that directory.
And I can also not open a bug report here, because the offical binary works without problems.
The situation is something strage.
Do you know the reason why the other binaries have problems to open that directory?
Beta Was this translation helpful? Give feedback.
All reactions