Setting scroll_past_end to true (which is actually the default) does not seem to work to allow any file types not overriding this to scroll past the end of buffers.

However, when scroll_past_end is set to true in a syntax-specific settings file, it works.

Since the move to 2.0, the sidebar browsing is no longer working properly when browsing files hosted on our NAS: when we use the sidebar to dig into a subfolder structure, expanding a directory node often produces no effect: the Triangle icon is pointing down, but no content is shown below it. Only by using the right-click menu > Refresh, does the content appear.

This affects all our Windows 7 configs, when accessing our files via SMB. The files are stored on a dedicated Linux NAS (FreeNAS), on our LAN.

The issue seems to only affect "deep" folder structures, not the first/second levels.

The issue does not seem to affect files stored locally, or shared on a Windows server.

This was working fine up to Build 2181 (remarkably well, in fact!)

The 2.0.1 update does not fix the issue.

 The thing I miss the most, and keep stumbling over, is ^U universal argument support, the way it's used in emacs. I implemented my emacs-like key bindings, pretty much except for this common argument.

http://www.pennenergy.com/articles/pennenergy/2013/11/house-passes-bill-to-encourage-onshore-energy-production.html

This package of bills would protect and expand onshore American energy production and create new American jobs by streamlining government red-tape and regulations. Also, this legislation would establish an efficient and effective process to responsibly produce both renewable and conventional energy on our federal lands as part of a true all-of-the-above approach American energy production.

“For far too long the Obama Administration has deliberately blocked increased energy exploration and development in America, causing both oil and natural gas production on federal land to decline since President Obama took office. The real growth in American energy production is happening on state and private lands and this bill would bring that growth to federal lands,” said Natural Resources Committee Chairman Doc Hastings (WA-04). “This legislation unleashes America’s energy potential on federal lands by streamlining the federal permitting process and opening up proven energy reserves to increased energy production in places like the National Petroleum Reserve-Alaska. The passage of this legislation today is an important step forward to increase much-needed energy production in America that will create jobs, grow the economy, and make energy more affordable for hardworking American families.”

H.R. 1965, the Federal Lands Jobs and Energy Security Act of 2013, includes the following five Natural Resources bills:

Federal Lands Jobs and Energy Security Act (Lamborn CO-05) - This bill would reform the leasing process for onshore oil and natural gas projects on federal lands to eliminate unnecessary delays; reform the process for energy permitting, once a lease is in hand, to encourage the timely development of our federal resources; ensure funds are available for efficient wind and solar permitting; and set clear rules for the development of U.S. oil shale resources.

Planning for American Energy Act (Tipton, CO-03) - This bill would establish common sense steps to create an all-of-the-above American energy plan for using federal lands to meet our Nation’s energy needs.

National Petroleum Reserve Alaska Access Act (Hastings, WA-04) - This bill would cut through bureaucratic red tape to unlock the full potential of energy resources in the National Petroleum Reserve-Alaska (NPR-A) by ensuring that oil and natural gas are developed and transported in a timely and efficient manner.

BLM Live Internet Auctions Act (Johnson, OH-06) - This bill would give the Secretary of the Interior the authority to conduct internet-based auctions for onshore leases to ensure the best return to the Federal taxpayer, reduce fraud, and secure the leasing process.

Native American Energy Act (Young, AK-At Large) - This bill would streamline burdensome and duplicative government regulations and remove the barriers erected by the Obama Administration that are blocking Indian tribes from developing energy resources on their own land and creating new jobs.

I am a Mac user with OS X

Recommended by users, I recently bought and use Sublime Text 2. Before I was a fully satisfied user of UltraEdit.

UltraEdit has a nice and quick backup mode. I expected to find such a feature in Sublime Text 2 as well, but nope.

I downloaded the 'Automatic Backup' package, but now I get messages something like: If you use backup, Sublime Text will slow down tremendously, so switch it off.

With Automatic Backup I end up with a several chains of numberous consequent folders and in the end there is a file.

Those few files already take up several MB's of diskspace.

With UltraEdit I have just ONE folder where al backups go. I have 22,200 files in that folder and they use 212 MB of diskspace.

What I want is a Automatic Backup just as UltraEdit offers.

I want to use Sublime Text 2 to code programs, but it seems that I have to know Sublime Code to use the program instead of using it program my own stuff.

Compared with UltraEdit, I don't have to delve into the UltraEdit code to use that program, but with Sublime Text I have to.

Am I wrong?

Did I miss some information?

Is there a user friendly GUI?

Please tell me!

Thanks in advance.

Hans

The Netherlands