Statalist


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: -set maxvar #- causes "page up" not to be able access command history


From   Dan Blanchette <dan.blanchette@duke.edu>
To   statalist@hsphsun2.harvard.edu
Subject   st: -set maxvar #- causes "page up" not to be able access command history
Date   Thu, 9 Apr 2009 12:28:41 -0400 (EDT)

Hello all,

I just discovered that a new Stata module I'm working on would not
let me page up to previous commands after I ran it.  It turns out
that since my new module sets maxvar to 32767 (though it doesn't
matter what valid max you set it to) that that is the reason why
page up stopped working.

This is Stata Technical Support's helpful response to my query to them about this:

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is not a bug. -set maxvar #- causes all of Stata's initial memory areas to be cleared and reallocated, including the pageup buffer. The size of these allocations must change because the maximum possible length of a command has just changed.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The -sex maxvar #- command is only available in SE or MP.

I figured I'd post this to let everyone know this so that they don't spend
hours trying to figure out why this happens and so that internet searches
in the future will find this post.

HTH,
Dan Blanchette
Research Associate
Center of Entrepreneurship and Innovation
Duke University's Fuqua School of Business
dan.blanchette@duke.edu
*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/



© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index