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

Opening an integrated terminal also opens a new terminal window #43

Open
kaletellier opened this issue Nov 7, 2024 · 6 comments
Open
Labels
bug Something isn't working question Further information is requested

Comments

@kaletellier
Copy link

Hi,

as the descriptions says, whenever I want to open an integrated terminal, it also opens a completely new window (not obsidian window but a Windows window) with that terminal. They are bound somehow so that when I close that new window, the integrated terminal window does not work anymore.
Obsidian gives me a few messages at the side
image

Do you have a clue? Thanks a lot and really thanks for that great plugin!

@polyipseity polyipseity added bug Something isn't working question Further information is requested labels Dec 1, 2024
@polyipseity
Copy link
Owner

Have you installed Python and these packages using pip?

pip3 install psutil==5.9.5 pywinctl==0.0.50 typing_extensions==4.7.1

installation instructions

@kaletellier
Copy link
Author

kaletellier commented Dec 2, 2024

Yes, just checked it and the exact versions are installed.
That's the console output of obsidian:
image

Sorry for the german output. I were not able to change it but I translated it myself:
"Python could not be found. Run the shortcut without arguments to install it via the Microsoft Store or disable this shortcut under ..."

@polyipseity
Copy link
Owner

Yes, just checked it and the exact versions are installed

If you open the developer console in Obsidian, it should show more detailed error messages. Could you show it to me? Thanks.

@kaletellier
Copy link
Author

The above mentioned output is the only message I get there

@polyipseity
Copy link
Owner

polyipseity commented Dec 5, 2024

(Ignore the content collapsed below, you are on Windows so this could not have been applied to you.)

I think this is probably caused by Obsidian being installed using Snap or Flatpak, because they sandbox access to the system and filesystem. If so, you probably need to give Obsidian access to Python (I am not quite familiar with this).

I have been thinking to add a notice about this if you install Obsidian using Snap or Flatpak, but I haven't gotten around to do so.

Maybe your Python is called python instead of python3? If so, change the below setting to python. You can also try to enter the full path to Python 3 instead. Then click the "Check" button to see if it works.

image

(By the way, it would be best to add a reply instead of editing an old message so that I know there's a new message.)

@kaletellier
Copy link
Author

I updated the post one or two minutes after I created it, but it seems that you answered right away, faster than I edited 😅

But man, you're a genius, it worked! I just changed my python executable to "python" instead of "python3". Works like a charm, thank you so much!

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

No branches or pull requests

2 participants