When I change the font in WinDbg, the text disappears. I have to restart WinDbg to see text again, but then, the font setting is gone.
Before:
After changing the Font to Lucida Console 14:
Version at the time of writing: WinDbg 10.0.10586.567
There seem to be 2 questions:
How can I get the color back without restarting
How do I save the font in the workspace
Get the color back
This only happens in customized workspaces like yours. The text is not really gone but its color seems to be reset to black. The text is still there and can be selected:
To partially fix this, you can go to the View/Options menu, select the text color entry (no need to change) and click Ok.
Doing so might be needed twice:
when the focus is in the output window
when the focus is in the command prompt
Doing that will not affect the readability of existing text but the output of any new commands will be displayed in green color again.
Store the font in the Workspace
WinDbg knows several workspaces and when you chose "Save Workspace" it probably saved into a very specific one (specific to an executable or a crash dump).
To have the font settings always, it needs to be saved in the "base" Workspace. To do that:
open WinDbg without running a program and without opening a dump file
change the font
set the color again
save the Workspace (File / Save Workspace)
In some versions of WinDbg, e.g. 6.3.9600, this does not seem to be enough. In that case,
open WinDbg without running a program and without opening a dump file
change the font
set the color again
set the window to restored size (i.e. not maximized)
move the window to a different position
save the Workspace (File / Save Workspace)
maximize the window (if you want it maximized)
save the Workspace again (if you want it maximized)
Related
For some time now, I can't change FileMerge's font. Then it suddenly started using a Helvetica-like font (sans serif, variable width) for files it doesn't recognize (like typescript source files). That could be changed temporarily to monaco by changing the font to ... Helvetica. Yes, it's very weird.
But now, it shows all text white on white, and only the changed section is visible because of the different background and I cannot change it. I've tried to locate all the pref files, and reinstalled Xcode, but the text remains white on white.
Does anyone know how to change that, or where which (pref) file to change?
It could be a write permission issue, since I'm running it from a non-admin account.
Thanks.
This feature is completely broken, so you have to edit the theme file manually. It's located here:
~/Library/Developer/FileMerge/UserData/FontAndColorThemes/Default.xccolortheme
The file itself is plaintext XML. Even though it's pretty straightforward, I recommend backing it up first.
For example, if you want to increase the font size from "11.0" to "14.0", just do a find and replace.
You might be tempted to copy in a theme from Xcode. Don't bother. The font sizes don't appear to take effect, and FileMerge expects a white background, so darker themes won't work correctly.
The other answers didn't work for me (as I didn't have any theme files), but the following did:
Open FileMerge
Go to Preferences
Click the 'Set...' button under 'Font'
Click the top of the Fonts window so that it gets focus (this is the key step - if the Fonts window doesn't get focus the changes won't stick). If the Fonts window has focus, you should see your changes reflected in the FileMerge Preferences window live as you make them.
The solution was to delete the folder ~/Library/Developer/FileMerge. It did not solve the font problem (typescript files rendered with proportional font of different size, which causes problems for long files).
For me also the font panel settings have no effect at all. Same problem in XCode "Font & Colors" preferences.
For your colors problem, I would try quitting FileMerge, archiving the preference file, and relaunching:
mv ~/Library/Preferences/com.apple.FileMerge.plist ~/Library/Preferences/com.apple.FileMerge.plist.backup
FileMerge has a XCFontAndColorCurrentTheme setting:
defaults read com.apple.FileMerge XCFontAndColorCurrentTheme
I've tried setting that:
defaults write com.apple.FileMerge XCFontAndColorCurrentTheme "Presentation.xccolortheme"
But I don't see a difference. So maybe Apple is in the middle of revising this feature.
In addition to the answers already given, if those do not work, check that the files you are comparing are plain text and not rich text. If they're rich text, file merge will get the font attributes from the files themselves, hence you will not be able to affect the size of the font. You could instead open the files in a text editor and either convert them to plain text, or increase the size of the font manually.
None of this helped in my case on Big Sur, but this did the job. Requires sudo throughout so be careful.
Make a copy of a theme within the xcode bundle:
sudo cp "/Applications/Xcode.app/Contents/SharedFrameworks/DVTUserInterfaceKit.framework/Versions/A/Resources/FontAndColorThemes/Default (Light).xccolortheme" "/Applications/Xcode.app/Contents/SharedFrameworks/DVTUserInterfaceKit.framework/Versions/A/Resources/FontAndColorThemes/fileComp.xccolortheme"
Edit (in xcode for example) ~/Library/Preferences/com.apple.FileMerge.plist. Select the new theme by setting the XCFontAndColorCurrentTheme value to fileComp.xccolortheme
Edit the font values in new theme file fileComp.xccolortheme. Quit and restart FileMerge each time to apply.
I remember once while using Microsoft Visual Studio, opening a source file (by accident I think) and having it render in either subdued colors or with a different background and showing a watermark indicating that this file was not a normal editable source file. I was under severe time pressure then and unfortunately can't recall the file or the wording of the watermark (or I would be able to investigate unaided).
Does this ring a bell with anybody? Is there a way to cause MVS to display auto-generated files in a different manner so that the developer does not waste time editing something that should not be edited? I open plenty of auto-generated files all the time (usually as a result of some global search) and it would be helpful to have all such files render in the editor this way.
The MVS version in question is Microsoft Visual Studio Professional 2015. I have Resharper and OzCode as well.
I was having this same problem. For the files I work with (web stuff, js, css, etc.) the watermark is applied by Web Compiler: "Shows a watermark when opening a generated file" (see features list in https://github.com/madskristensen/WebCompiler).
It turns out the "Generated" mark is toggled by clicking the bottom right corner of the editor window. In fact, it is always there, however if you accidentally click it, that will cause it to be hidden UNLESS you mouse over the bottom right corner of the editor window of the generated file.
So, to re-enable the watermark:
Open a file you know for sure is generated, like one of the output files in your compilerconfig.json file.
In the editor window, mouse over the bottom right corner of the window. You should see the "Generated" text re-appear, with a tooltip that says "Click to toggle visibility".
Click the text. From now on the "Generated" watermark will show up in your generated files. Just be sure not to accidentally click and hide it again.
-Michael
I much prefer Wordpad to Notepad in Windows 7 for quickly checking out source files, namely because Notepad doesn't display most correctly if the file was written in Unix.
However it saddens me that I can't chose the plain-text mode's default font.
Is there a way to change it? I'm guessing registry here, if at all.
Open a new document, set the default font and size, and save the file as
"wordpad.wri". Close wordpad. Right click on the saved file and select
Properties. On the general tab check read-only, apply your changes and
click OK.
Whenever you want to launch wordpad, do so by double clicking the saved
wordpad.wri.
[src: Tom Porterfield ]
You can change also the Icon of the shortcut, putting the icon of the Wordpad program, and to change also the name of the shortcut, so it will look as it's really the Workpad program.
How can I set the position for the output prompt in Visual Studio 2008 when debugging is started?
I have two screens and I want the prompt to always appear on my second screen so that I still can see the code on the primary screen, I have tried some tricks but I haven't got it right.
I'm not sure what you mean by "outputprompt". If you are creating a command line application and are talking about the command window, then
position the window where you want it (you can pause you app if it closes too fast)
click on its system menu, then click on properties
on the third tab of the appearing properties dialog, enter the values you like (be sure to uncheck automatic window positioning)
close the dialog by clicking OK
in the dialog that appears, pick the option that changes the link, instead of just changing the current window (I'm not sure either a German or English translation of the options is helpful for you)
HTH.
I use a custom color scheme in Visual Studio (black background, gray text, etc.). There a few settings that refuse to change, however. For example, when cursoring through the markup for an aspx page, the current tag defaults to black text, which doesn't work well on my black background. I've previously changed the appropriate setting to a "visible" color. In fact, to fix it, all I have to do is open the Options window, check and uncheck the Bold setting on Plain Text and hit OK, and now all my chosen settings are properly loaded. If I open a new session though, I have to go through these steps again. There are only a few settings where I notice this behavior (the Read-Only Region is another one), but it's annoying to have to do a dummy option change to get them to kick in. Has anyone seen this behavior before, and does anyone have a fix/workaround?
UPDATE: Found an interesting fix. I still don't know what the root cause is (probably some corruption as #sliderhouserules suggessts), but I've got a quicker way to fix it than using Tools | Options | Fonts and Colors. I simply exported my current color settings and created a macro to load them in:
Public Sub ImportColors()
DTE.ExecuteCommand("Tools.ImportandExportSettings", "-import:""C:\Documents and Settings\gregf\My Documents\Visual Studio 2008\Settings\FontsAnColors_Exported-2008-12-05.vssettings""")
End Sub
I then mapped that macro to a button on my toolbar. Now I have a one-click fix whenever my colors go awry. Not ideal, but much less painful now.
Sounds to me like you may have some corruption in your VS install or something (IE you need to reinstall VS). This doesn't sound like a bug, and you'd be fishing in the dark trying to repair your registry or whatever config files are involved in setting and storing these options for VS.