Is there anyway to start cmd (from the run-dialog (windows+r)) with black background color and black font? I know that I can just change the colors when I'm inside of the cmd and then (e.g if I changed color 1 and 2 to black) just write "color 12", but that's not what I want, I want to start it somehow with black/black without any configuration in cmd.. Is this possible?
As you stated, doing this in batch might niot be possible,
but you might be able to call a c/c++ programm which sets the console color for you (the last time i checked cmd.exe was really bad in reverting any changes to its system settings when exiting a process).
So, look at How to change text color and console color in code::blocks? , copy it into a .cpp file, compile it (this is where i usually add a rant about how windows comes without installed compilers) and call it right after launching your cmd!
Sorry to lay it down but it is impossible in CMD to get black on black without altering the registry, using additional software, or additional code. Powershell would probably be the best way to go with it. I am not as experienced in that area but i did find a helpful webpage Here.
Related
While my search for a Python debugger on Emacs remains unfulfilled, I am giving PyCharm CE a test drive.
Already on my second day I'm encountering a trivial but frustrating point. Is it possible to set the background to be pitch black in just one place?
A program written by programmers for programmers should certainly have included a feature such as "change the background for Docstrings, Comments, Keywords, ... the whole shebang" to black, but I don't see it.
I understand of course that some parts of the UI will stubbornly refuse to change, and I'm OK with that, just so long as the Python code itself appears on a pure black background.
The Twilight and Mokokai themes come close, but their backgrounds still leave ample "contrast room" that could be used by darkening the background color.
(How do we get from left to right... err.. I mean.. how do we get darker than we are.. um, wait... Isn't the version on the right so much easier on the eye.. but anyway, how can we do it?)
Update
The exact same problem and solution apply to Android Studio.
In File > Settings:
Go to Editor > Colors & Fonts > General
Choose the theme you want to modify (will likely need to Save As... your own as you can't modify the default color schemes.
Go to the Text > Default Text colors and change the background to black. The only ones that won't be affected are the syntax highlighters that define their own background (usually select/highlight/errors/etc.)
I just recently installed Android Studio on my Windows 10 computer, and I am trying to resolve this dissonant background color issue in the built-in terminal. Screenshot here. I have not had this problem when I used Android Studio on Ubuntu 14.04.
The color of the text background is black, while the color of the console background is white. This issue is not related to my using Git Bash as my terminal as it also occurs when I use Windows Command Prompt.
I have checked through Settings --> Editor --> Colors and Fonts --> Console Colors and was unable to find anything that would allow me to resolve the background colors. I have also tried changing the color scheme to something different (e.g. Darcula). Screenshot here. Additionally, I also tried to change the overall UI theme and still got identical results.
The terminal is ugly, but I would love to take advantage of its built-in conveniences for using Git. The Android logcat output and Gradle messages look perfectly fine. How can I fix this so that the text and console background colors are the same? Thanks in advance.
I struggled with this issue for a while too.
From experience, the terminal takes the colors of the Windows console. Not that very well however that was the only way that I could do the required changes.
Open a cmd window in windows and on the main menu go to defaults.
Change the colors and save. Next terminal in Android Studio will change on next instance.
The colors won't follow exactly so one needs some experimenting. Best results I got with black text on white background.
I recently started using Lisp and Limp is the only available plugin for VIM. But, once I set it up and hit F12, the terminal like window that appears has a very small font size. I have a screen resolution of 1920x1080 and it's impractical to read such small fonts. I went through the man page of 'screen', but couldn't find any useful information on changing the font or font size. Is there a way to do this?
And how about using something like 'xterm' rather than 'screen'? I looked through the code of bridge.vim. I don't think it is too much of a task. Any ideas on this?
By screen, do you mean GNU screen?
GNU screen is a terminal emulator that runs in another terminal or emulator. It has no direct control over font sizes; it's purely text based. The window you're seeing must be some GUI terminal emulator; you haven't told us enough to guess which one (could be xterm, could be Gnome terminal, etc.).
For xterm, control-right-click should bring up the "VT Fonts" menu, which will let you select a different font. If none of the available fonts are to your liking, you can use X resources to reconfigure the options, including the choice for the default font.
xterm also supports a control sequence that sets the current font. You have to know the name of the font you want. xlsfonts will show you a very long list of font names (it just showed me 5594 of them). For example, if you run this from a shell running in xterm:
printf '\e]50;-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1\a'
it should give you the font I usually use. But screen generally intercepts escape sequences like that, so it probably won't work from screen under xterm.
Other terminal emulators should have similar mechanisms.
I've been trying to get colourschemes to work properly in VIM when using it over ssh with PuTTy as a client but unfortunately I haven't had much success. I can only get 8bit colours working with PuTTY even though I've enabled 256 colors in putty and set t_Co=256 in VIM. They don't turn out as they should. I've been trying to replicate this setup http://www.interworksinc.com/blogs/ckaukis/2009/06/03/vim-color-schemes-putty but as I say it's been in vain so far.
Has anyone here had success with colourschemes working with VIM in PuTTy? I'd appreciate any advice
Thanks,
Patrick
[EDIT] Turns out I've found the source of the problem. I was using vim in a screen which was breaking the colours. Updated question I guess is, is it possible to have working colors in a screen session? [/EDIT]
As well as compiled support, it may be necessary to add some config to screenrc (I needed to).
http://www.frexx.de/xterm-256-notes/ has a good guide. The relevant part to screen:
By default, screen is not aware that it is running in a 256 color capable xterm. To make programs in screen recognize this feature, you need to set three things in your ~/.screenrc:
# terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
# erase background with current bg color
defbce "on"
Yes, you can do 256 colours with screen, however, this option usually isn't compiled in. Simply compile screen yourself with:
--enable-colors256
Alternatively, you could get a tabbed PuTTy. It has the advantage of ctrl-a going to the beginning of the line, and saves you from many termcap headaches. However, if you like to reconnect to your screen sessions from multiple terminals, there really isn't anything better than screen for the job.
NB. This question probably belongs on Superuser.
I had same problem on Mac Os, tried some solutions but all tests show that 256 colors not displayed. After that I'm installed screen from brew and all works great. Maybe it's because Mac Os default screen from /usr/bin/ compiled without --enable-colors256 flag.
Solution for mac os: brew install screen
I had trouble with black background in Putty: blue characters on a black background with default colours are hard to read:
My solution for a better contrast was to enable "system colors" checkbox unter
"Settings / Window / Colours / Use system colors"
This displays the Putty screen with black characters on a white background. Not hip but readable :-)
I'd like to write a Linux screen magnifier that's customized to my liking. Ideally, the magnified window would be a square about 150 pixels wide that follows the mouse cursor wherever it goes.
Is it possible to do this in X11? Would it be easier to have an application window that follows the mouse around, or would it be better (or possible) to forget about the window altogether and just make the mouse pointer a 150x150 square that magnifies whatever's underneath?
Look at the source to xeyes?
This actually already exists, it's called Xmag (do a Google search for additional info). You might want to check out the source code for it if you want to know how it works.
EDIT: looks like I misread your question a little bit... if you want a magnified square to follow the mouse pointer around, I suppose it should be possible, but I don't know the technical details of how you'd do it. Regardless, the place to start is probably by looking at Xmag as a starting point.
I am unsure if this can run as its own app or would have to be integrated into your window manager. Either way, you would need libx11 (might have a different name from distro to distro). Also, I would suggest taking a look at swarp. I know this is not even close to what you are talking about, but the source code is only 35 lines and it shows what can be done with libx11.
I would personally make that a frameless window that always stays atop with a 1px hole in the middle. The events that the user makes (Mouse clicks, keypresses, whatever) is passed to the window below.
And when the user moves it's cursor it is ought to be visible to your window and you just move it over a bit. For the magnifying part, well - that is left as an exercise to the reader (Because I do not know how to do that as of yet ;-).
Texworks comes with such a feature to inspect the pdf resulting from typesetting a latex source. You can also choose between a square or a circular magnifier. See https://www.tug.org/texworks/ for access to the code which can serve a launchpad.