[Clyde Schechter]

When you select text with the mouse, if (in Windows) you hold down the Alt-key, as you move down the page, instead of extending the selection to the end of each line, you will end up selecting only those columns that you have moused over. Perhaps this explanation is not really clear--I'm not sure how to really say it in words. Just open up some file in the do-editor, and try it--you'll see what happens. (I assume there is something similar in Mac and Unix, but I don't know how they work.)

[Ariel Karlinsky]

There's a nice little animation showcasing this in notepad++ - I assume the stata do editor is identical:
https://notepad-plus-plus.org/featur...e-editing.html

[Marcos Almeida]

Ariel Karlinsky : thanks for the helpful animation.

[Daniel Bela]

[...](I assume there is something similar in Mac and Unix, but I don't know how they work.)

In Stata for Unix, this works by pressing <Ctrl> during text selection -- and it works already in Stata 13 and Stata 14.

Regards
Bela

[Ariel Karlinsky]

In stata for windows it's with <Alt> during text selection.

[Ellora Derenoncourt]

Hi all,

I'm a Stata/MP 15 for Mac user and wanted to point out a couple bugs:

1. The variables window in the main window appears empty even when a dataset with variables is loaded.
2. The file path does not update even after using the cd command. It's stuck on the Applications directory.

I've talked to several other Mac users of the new release who've found the same issues. Is there a solution for these issues or can they be addressed in a future update?

Thanks so much,

Ellora

[Emilio Matuk]

I am using command "spmatrix idistance" which looks with a limit on size of 11,000 x 11,000 (aprox). Am I correct?

[Chinh Nguyen (StataCorp)]

Hi all,

I'm a Stata/MP 15 for Mac user and wanted to point out a couple bugs:

1. The variables window in the main window appears empty even when a dataset with variables is loaded.
2. The file path does not update even after using the cd command. It's stuck on the Applications directory.

I've talked to several other Mac users of the new release who've found the same issues. Is there a solution for these issues or can they be addressed in a future update?

Thanks so much,

Ellora

I'm assuming you're at Harvard and obtained Stata 15 from there. If so, there's a problem with their installer. Get their installer again, remove the old Stata 15, and reinstall Stata 15.

It's very important that you remove the old Stata 15. The version of the Stata 15 application that their installer was installing does not match anything from StataCorp and we can't vouch for any of the other files that were installed. We did verify that their current installer seems to be fine.

[Bill Sribney (StataCorp)]

I am using command "spmatrix idistance" which looks with a limit on size of 11,000 x 11,000 (aprox). Am I correct?

The limit on the size of the weighting matrices in the Sp commands is the limit of matrices in Mata -- which is 2^48 - 1. Obviously, you will reach memory limits on your computer before you make a square matrix of that size. The limit of 11,000 is max_matsize, which only applies to matrices created in Stata, not those created in Mata.

So the effective limit on the size of weighting matrices is the RAM of your computer.

[David Stevens]

Have there been any improvements to the multithreading of functions in Stata 15? In Stata 14 commands like mixed and stcox are both calculated using a single thread. Will these actually use multiple cores in Stata 15?

[Kazi Bacsi]

Recently I've experienced many Stata 14.2 crashes that was reported to the customer service. This involves losing quite much code. I've found among the feature requests a previous post asking for auto-save (every n minutes or each time Ctrl-D is pressed). Would it be a big deal to introduce it in a patch?

[Joseph Coveney]

Recently I've experienced many Stata 14.2 crashes that was reported to the customer service. This involves losing quite much code. I've found among the feature requests a previous post asking for auto-save (every n minutes or each time Ctrl-D is pressed). Would it be a big deal to introduce it in a patch?

help cmdlog

[Kazi Bacsi]

help cmdlog

Thank you very much indeed for this idea, I will use it! However, it is not replacing a very basic feature of script editors, and I don't think it would be an immense effort to code it...

[James Hassell (StataCorp)]

Recently I've experienced many Stata 14.2 crashes that was reported to the customer service. This involves losing quite much code. I've found among the feature requests a previous post asking for auto-save (every n minutes or each time Ctrl-D is pressed). Would it be a big deal to introduce it in a patch?

From the Do-file Editor's menu, look under Edit->Preferences, and once there look under Advanced. Select 'Always save before do/run'. This is available in Stata 15, 14, and before. If using Stata 13 or earlier, the Do-file Editor preference layout is different; look under the 'Windowing' group.

If you are experiencing crashes, perhaps you can send [email protected] something that is reproducible so we can investigate.

[Kazi Bacsi]

From the Do-file Editor's menu, look under Edit->Preferences, and once there look under Advanced. Select 'Always save before do/run'. This is available in Stata 15, 14, and before. If using Stata 13 or earlier, the Do-file Editor preference layout is different; look under the 'Windowing' group.

If you are experiencing crashes, perhaps you can send [email protected] something that is reproducible so we can investigate.

Dear James,

Thanks for your kind answer! Please correct me if I am mistaken, but that option only works if I run the whole do file, but it doesn't, when I run certain sections by selecting them (which is in 99% the case when I am coding).