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

Pygments not loading #33

Open
tig opened this issue Jul 13, 2020 · 4 comments · May be fixed by #41
Open

Pygments not loading #33

tig opened this issue Jul 13, 2020 · 4 comments · May be fixed by #41
Assignees
Labels
bug Something isn't working

Comments

@tig
Copy link
Owner

tig commented Jul 13, 2020

Describe the bug
Via "Paul":

I found winprint 2.0 and am having trouble getting it to work.
I ran the installer and was told it was successful.
If I start it from the start menu and add a file I get.

Screenshots
If applicable, add screenshots to help explain your problem.
image

image

@tig tig self-assigned this Jul 13, 2020
@wasspaul
Copy link

I did get the GUI to work. What I did was try the pygmentize.exe executable alone in a cmd window and it failed. It was trying to run c:\python38\python.exe which I did not have. I do have a win python installation and I did not want a second python installation so I made a linked DIR that mimic-ed c:\python38 and all with the gui is well. I went back and read all the documentation I could find. Best I can tell there is no documentation of needing a python env installled on the machine for winprint to function

On the other hand I tried every thing I could think of to get the powershell command line version to install and was not successful.

@tig
Copy link
Owner Author

tig commented Jul 13, 2020

Yea, i was just debugging this and discovered I never implemented showing errors if python & pygments weren't installed! Duh.

I will fix this asap. What version of python DO you have installed if not 3.8?

Can you share your logs with me so I can diagnose the powershell issue?

@wasspaul
Copy link

C:\WPy64-3771\python-3.7.7.amd64 which is a WinPython distribution.

I might be a little confused about your log request. I cant get the import-module to work in powershell - either from the command line or in a profile. Therefore I cant get winprint to run from the powershell I did not think a log file would be created in that case. Am I missing something?

@tig
Copy link
Owner Author

tig commented May 31, 2022

Wow, I'm sorry I missed this last comment (two years ago!).

 ls "$env:appdata/Kindel Systems/WinPrint/logs"

    Directory: C:\Users\charlie\AppData\Roaming\Kindel Systems\winprint\logs

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---            2/7/2022  1:43 PM          12609 out-winprint.log
-a---            2/7/2022  1:41 PM          14924 winprintgui.log

@tig tig added the bug Something isn't working label May 31, 2022
@tig tig linked a pull request Sep 20, 2022 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants