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

JavaScript error on run #5

Open
PrismaWeaver opened this issue Aug 27, 2020 · 12 comments
Open

JavaScript error on run #5

PrismaWeaver opened this issue Aug 27, 2020 · 12 comments
Labels
bug Something isn't working

Comments

@PrismaWeaver
Copy link

error reads:

Uncaught Exception:
TypeError: Cannot read property 'toString' of undefined
at ReadFileContext.callback (...\wind-unpacked\resources\app.asar\build\electron.js:47:47)
at FSReqCallback.readFileAfterOpen [as oncomplete] (fs:js:247:13)

results in Terminal Tweaker running successfully, but there are no available options under each tab.

@issue-label-bot issue-label-bot bot added the bug Something isn't working label Aug 27, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.94. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@KrunchMuffin
Copy link

confirmed

@creizlein
Copy link

Confirmed x2, same here.

@dominic-ks
Copy link

Also confirmed, no idea on a workaround.

@umernalla
Copy link

Same here
Uncaught Exception:
TypeError: Cannot read property 'toString' of undefined
at ReadFileContext.callback (C:\Downloads\Terminal.Tweaker.Portable\win-unpacked\resources\app.asar\build\electron.js:47:47)
at FSReqCallback.readFileAfterOpen [as oncomplete] (fs.js:247:13)

@jhilker98
Copy link

Confirmed here as well.

@nateshmbhat
Copy link
Owner

mostly the issue here is that microsoft have changed the location to their terminal configuration file and that's why its not able to find that file in the location which was there before.

i am having issues in booting up my windows machine currently. so it will take some time to set all this up. i plan to do it when i get some time.

Meanwhile , if anyone wants to open a PR, that would be very helpful. It will be a small change i think in this particular function :

const findConfigFilePathForFirstTime = () => {

@nateshmbhat nateshmbhat pinned this issue Mar 18, 2021
@enxg
Copy link

enxg commented Apr 19, 2021

mostly the issue here is that microsoft have changed the location to their terminal configuration file and that's why its not able to find that file in the location which was there before.

i am having issues in booting up my windows machine currently. so it will take some time to set all this up. i plan to do it when i get some time.

Meanwhile , if anyone wants to open a PR, that would be very helpful. It will be a small change i think in this particular function :

const findConfigFilePathForFirstTime = () => {

I ran the code on my machine and it found a match, path seems correct, I think you only need to publish a new release.

@nateshmbhat
Copy link
Owner

Unfortunately Microsoft has changed the format of the file now in latest versions.

I will have to do quite some changes to this to work. I will see if I can tweak this up some places to fix it.

@andyrz
Copy link

andyrz commented Dec 8, 2021

Any plans on resolving this issue? The tool is essentially useless....

@binbard
Copy link

binbard commented Jan 16, 2022

Not yet fixed, still reproduced that error, on windows 11.
2022-01-16 17_35_56-Error

@manusoftar
Copy link

Bump

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

No branches or pull requests