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

Mac OS & Linux : settings.json are not transmitted when using build command #122

Open
jcommaret opened this issue Oct 23, 2024 · 12 comments
Labels
question Further information is requested

Comments

@jcommaret
Copy link
Contributor

Problem :
Before the build, I am able to discuss with the void editor using scripts/code.sh
beforebuild

After running the build command, I am not able to do it. It seems package.json settings are not transmitted (void.command.toogleSettings), and settings.json neither.

after build
after build 2

Step to reproduce :

  • build the editor from scratch.

Expected :

  • I should be able to input settings, using the "icon" or the command palette.
@andrewpareles andrewpareles added the question Further information is requested label Oct 25, 2024
@AshDevFr
Copy link

I have the same issue, did you find a workaround to bundle with the settings on MacOS?

@jcommaret
Copy link
Contributor Author

jcommaret commented Oct 29, 2024

@AshDevFr : not yet, @andrewpareles told me that he was working on that.
I have a dirty fix in mind.

As the settings are stored in Library/void and @andrewpareles know the how this file should look like, maybe he can share us a settings file with options (except the api key) so we can be able to add it afterwards into the Library/void folder.

@jcommaret
Copy link
Contributor Author

@andrewpareles do you have any schedule on this ?

@jcommaret
Copy link
Contributor Author

jcommaret commented Nov 2, 2024

@andrewpareles i am still investigating this issue, so I am building a virtual MacOS to run in a VM to understand if the latests MacOS versions needs some tweaking, void (full ide) might not have access to the same system ressources than extensions.

@andrewpareles
Copy link
Contributor

Apologies for the late reply. I wonder if this has to do with #136? (If it does, it should be an easy fix inside extension.ts). Mac build worked for me the last time I tested it but I'll keep you posted.

@jcommaret
Copy link
Contributor Author

@andrewpareles what is your MacOS version ?
I had the same intuition, this 2 problems looks like they are very related to settings.json.

@jcommaret
Copy link
Contributor Author

@andrewpareles I think you could try to fix extension.ts

The same problem appears after building the extension on a MacOS Virtual machine running Sonoma. (I used gemini for activating the extension - thanks it's free and no credits are required, can be used worldwide... )

Capture d’écran 2024-11-03 à 12 46 01

So actually I am not able to run the full ide with extension.

@andrewpareles
Copy link
Contributor

Does #103 (rebasing) fix this?

@jcommaret
Copy link
Contributor Author

@andrewpareles I wasn't able to Check it right now.

@jcommaret
Copy link
Contributor Author

@andrewpareles :

  • I deleted the folder.
  • I recloned the project.
  • I cleaned node.js cache.
  • Installed the project. Nothing to do. this doesn't work.

I am not sure on how to update the visual code studio dependency inside this project.

However, running with script/code.sh is working.

@jcommaret jcommaret changed the title Mac OS : settings.json are not transmitted when using build command Mac OS & Linux : settings.json are not transmitted when using build command Nov 13, 2024
@jcommaret
Copy link
Contributor Author

Copie d'écran_20241113_161244

I am having the same problem on Fedora 40 / Asahi

@jcommaret
Copy link
Contributor Author

The extension now doesn't allow me the edit the settings at any place

@andrewpareles :

-> When full ide build :

Running scripts/code.sh :
Capture d’écran 2024-11-18 à 13 21 55

-> Same problems happens on extension build

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

No branches or pull requests

3 participants