> And maybe describe your use-case, what (not how) you want to do and why.

yes, i wanted to do that, but got lost in technicalities while filing the 
issue, that it got mingled in the long version, and got skipped in the TL;DR 
version 😅 . anyways, following is it:

* i have to take screenshot of the output, and embed those in a document
* for that, the output has to launch in a fixed window width, and in a fixed 
font size - both of which are compulsory, and have to be easily specifiable
* optionally, it would be nice if the output is in light theme - so that while 
taking the print out (i.e. hard print out on paper), it looks nice while 
consuming less ink

These above are requirements, and following is why the current situation is 
unable to achieve the last optional one:
* output of geany is shown on conhost

<details>
<summary>

* changing theme on conhost is not easy (click for details)
</summary>

* i tried doing that via colortool (see [above 
comment](https://github.com/geany/geany/discussions/3303#user-content-fnref-ct-f4953bd48a5c2cd01e758990f3d58600))
 which required using either of [4-bit 
terminal](http://ciembor.github.io/4bit/) or 
[terminal.sexy](https://terminal.sexy/)
* the 4-bit's presets were nice, only required two clicks : white/bright-white 
in background, and black in foreground
    + screenshot: 
![image](https://user-images.githubusercontent.com/19423063/192133055-62147d41-0efe-44b1-84f3-024f97841b09.png)
    + but i just couldn't get the generated .itermcolors (by copy pasting the 
data:url and decoding it from url-encoding) file to work with conhost. 
    + same with terminal.sexy

</details>

* that is, i don't have a functional light theme for conhost
* and don't know how to change geany to output in a terminal for which it is 
(easy to do all above)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3303#discussioncomment-3726327
You are receiving this because you are subscribed to this thread.

Message ID: <geany/geany/repo-discussions/3303/comments/[email protected]>

Reply via email to