-
Notifications
You must be signed in to change notification settings - Fork 27
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
Line Numbers "Inherit" not working as expected #207
Comments
Hmmm, yes. Inherit used to do exactly what you expected it to, but it appears to be broken. I'll have to look into it. |
I've fixed this. It will appear in a future release, but the release will be delayed by the fact that I need another setting to control what happens when there isn't an editor corresponding to the print job, such as printing folders or selections of multiple files. When "inherit" was conceived folder and multi-selection printing didn't exist, and hardly anyone uses the file explorer to print just one file without opening it so I didn't notice the undefined case. |
I'm having the same issue with
Chrome:
|
I apologize if this is "operator error" on my part - but I do think I am using this extension as intended. And yes, I did read the manual.
If I set line number setting to No, then no line numbers print. Cool.
If I set line number setting to Yes, then line number print. They print if I print the whole file or print just a selection. Cool.
If I set line number setting to Inherit, then line numbers do NOT print, even when line numbers are visible in the editor.
Workaround for now is to use Yes and No explicitly, but I would much prefer to inherit from the editor. Ideas what I might be doing wrong?
Screenshot showing editor:
Screenshot showing print rendering with line number setting = Inherit
Screenshot showing print rendering with line number setting = Yes
I get the same result whether I print a selection or print the whole file. Using Edge browser (latest) on a Windows 10 platform. Using latest version of the Print extension at time of this writing (v0.11.1). And if it matters, the code is using SystemVerilog syntax highlighting as provided by the Verilog-HDL/SystemVerilog/Bluespec SystemVerilog v1.11.4 extension.
Here are the particulars regarding my VS Code:
The text was updated successfully, but these errors were encountered: