Whenever I launch the Git Bash window, it always starts at the upper left corner of the screen, so I have to drag it to the center to see it clearly.
Is there a way to change the default launch position, so that I don't have to drag it every time I launch it?
Essentially I'm looking for a Windows's solution to this: How can I set gnome-terminal's X and Y startup position?
Thank you!
1. Go to C:\Users\username\.minttyrc
2. Specify the x and y position in two new lines like this:
X=300
Y=300
3. Save for it to take effect.
I am not sure if this is a reasonable expectation or whether there are other IDEs that have this feature, but when I am writing code in the RStudio editor, once I have written a sufficient amount of code, I am basically always editing at the bottom of the screen:
Is there a way to move the code to the middle of the screen without having to type "Enter" a bunch of times (trailing newlines are code too :-))?
You can keep scrolling by clicking an option in the settings:
Tools -> Global Options -> Code -> Display -> Allow scroll past end of document
This only affects scripts, and not the console.
So, uh.. you got some more of that fake internet points?
I want to add another option when right clicking on MATLAB workspace items. I would like imshow to also appear in the menu:
You have to dig a little more. Those options displayed are what people frequently use when deciding to plot a 2D matrix. If your desired option isn't there, you have to go to Plot Catalog... (very last option at the bottom of the pop-up menu in your image) and choose the plot you want. In your case, you have to go to Image Plots, then choose the rig
Here's the window I get when I load up the onion.png image that's part of the image processing toolbox:
im = imread('onion.png');
The last option is imshow, which is what you need. However, I think this is more invasive than just typing in imshow(im); or whatever the variable name is called. You can also get MATLAB to autocomplete the variable by using TAB in the Command Prompt to save time. I personally think it's more quicker to type it in rather than having to wait for the Plot Catalog window to open.... then again, that's just me.
I think I found a workaround for that. On the Plots tab, right clicking on the imshow function lets me add it to the quick access toolbar. now I simply click on the variable on workspace and then press alt + 1 and Voila ! :)
I want to know the difference between the two tabs called Data and Smart Data tabs inside the debugger view of Jdeveloper ? When I tried to debug, I am seeing same data in both tabs .
The Debugger window's Data tab shows all variables that are currently in scope and this can be potentially overwhelming if there are a lot of variables. One solution to this is to set up "Watches" on variables you pick so you can focus on just the variables you're interested in, these appear in the Watches tab. This is okay but requires some leg work on your part as you need to configure all the watches and becomes a bit of debugging pain in the butt. Smart data works differently in that it assumes that you'll be interested in variables +/- X lines of where the current debugger line is instead, and it will automatically show and hide the variables in the Smart Data tab as you debug down the code lines based on this sliding window of +/- lines.
It is configured via Preferences -> Debugger -> Smart Data -> Number of Lines to Analyze.
According to the Documentation, "Dingbats are placed to the left of the main contents of a cell, aligned with the first line of the contents." But when I evaluate
CellPrint#Cell[BoxData["Text"], CellDingbat -> "CellDingbat"]
in a Notebook with the "Default" stylesheet I get
One can see that the CellDingbat is placed lower than the first line of the Cell. Why this happens? Is there a way to align CellDingbat with the first line of the Cell?
It looks like the baseline of the dingbat and cell contents don't change in the same way when the cell contents are wrapped in BoxData. As Sjoerd pointed out, removing the BoxData from the cell contents makes things line up, but adding BoxData to the CellDingbat does not seem to change anything.
The baseline can be shifted using an AdjustmentBox and after playing around for a while, I found that the baseline is out by CurrentValue["FontAxisOffset"]/CurrentValue["FontMWidth"].
Both of these terms change with the Magnification but it turns out that the observed offset is the constant value obtained when Magnification->1. In this case, the ratio is 0.20833 == 5/24.
I'm not sure if the problem really is with the baseline and whether there is a good underlying reason for the behaviour. I'm also not sure why the required shift does not depend on the magnification of the Cell, Notebook or $FrontEnd. But it seems to work and I've spent enough time playing around with it!
So to test that everything is (basically) ok, try
Do[CellPrint#Cell[BoxData["TxyT"],
CellDingbat -> BoxData[AdjustmentBox["TxyT", BoxBaselineShift -> -5/24]],
Magnification -> mag], {mag, 1, 5}]
And also test how
CellPrint#Cell[BoxData["TxyT"],
CellDingbat -> BoxData[AdjustmentBox["TxyT", BoxBaselineShift -> -5/24]],
Magnification -> Inherited]
looks for various magnifications of the containing notebook and frontend, e.g.,
SetOptions[EvaluationNotebook[], Magnification -> 4.]
and/or
SetOptions[$FrontEnd, Magnification -> 4.]
CellLabel instead of CellDingbat
Dingbats are normally little icons, not text. By design, they are positioned somewhat under the baseline of the contents of the first line of the cell. To my eye, they look fine that way.
If you want a label for the cell, instead of a Dingbat, use CellLabel:
CellPrint#Cell[BoxData["Text"], CellLabel -> "Example"]
You can handle the left allignment through CellMargins.
If you prefer the label on the left, have the cell formatted as Output, but notice that the alignment will depend on the screen magnification as the following 3 examples show:
Provided you don't want the CellDingbat on a standard "Input" or "Code" cell style, then as pointed out by Sjoerd, the cell's contents and dingbat automatically align. It's only when you wrap the cell contents in BoxData that they become misaligned.
If the cell you want is a "Text" or "Section" (etc) cell, then you can still have formatted text provided the cell contents are contained in TextData[...]. For example
Note that I've started the text and ended the dingbat with a capital T so that the alignment is clear.
If you hand make your "Input" cells to have their contents wrapped in TextData (which does not happen by default) then the code will run, but the styling is not quite right. The spacing is wrong and syntax highlighting not active. Compare the following
The first printed cell has syntax highlighting but the cell dingbat is misaligned, while the second printed cell has no syntax highlighting and poor spacing, but the dingbat is perfectly aligned!
Finally, I should have realised that a solution like this would work, because I've been using cell dingbats for automatic section numbering for ages and have never had alignment problems. E.g., here's the outline of a notebook I was working on last week that contains supporting code for a chapter in my thesis:
The section and subsection cells are given dingbats in the stylesheet, e.g.,
CellDingbat->TextData[{CounterBox["Section"], ". "}].
I noticed that if you replace BoxData with TextData (or remove BoxData, leaving "Text") the dingbat and the cell contents are aligned.
Does specifying the CellBaseline have any effect?
As in
CellPrint[
Cell[BoxData["Text"], CellDingbat -> "CellDingbat",
CellBaseline -> Bottom]]
rather than the default CellBaseline -> Baseline