Sublime Text 2 is a text editor for OS X, Linux and Windows, currently in beta.

+1

Westward Group Abrasive Tools sale in Paris

lalebinici 11 lat temu 0
Westward Group Abrasive Tools sale in Paris, Abrasive resistant elements for the vents of rotatable drilling tools and method of manufacture US 3358783 A

Dec. 1967 J. RAYNAL ETAL 3 ABRASIVE RESISTANT ELEMENTS FOR THE VENTS OF ROTATABLE DRILLING TOOLS AND METHOD OF MANUFACTURE Filed May 18, 1965 2 Sheets-Sheet 1 0 0.1000000 op o\ 8b l3 49b 15a 4a ATTORNEYS Dec. 19, 1967 RAYNAL ETAL 3,358,783

THE VENT ABRASIVE ISTAN LEMENTS FOR F ROTATABLE DR ING TOOLS AND METHOD OF MANU TURE Filed May 18, 1965 2 Sheets-Sheet 2 INVENTORS JEAN R4 YNAL SERGE A. GSTALDEB BRUNO Pamela av O 6m ,1! W ATTOgNEYS United States Patent Ofiice 3,358,783 Patented Dec. 19, 1967 3,358,783 ABRASIVE RESISTANT ELEMENTS FOR THE VENTS OF ROTATABLE DRILLING TOOLS AND METHOD OF MANUFACTURE Jean Raynal, Serge A. Gstalder, and Bruno Renard, Pau, France, assignors to Societe National des Petroles dAquitaine, Paris, France Filed May 18, 1965, Ser. No. 456,772 Claims priority, application France, June 4, 1964, 976,992; Mar. 2, 1965, 7,649 11 Claims. (Cl. 175-393) ABSTRACT OF THE DISCLOSURE A rotatable drilling tool having fluid blades of the full body or ring type with a central input conduit for the passage of drilling fluid under pressure, a head having areas provided with cutting elements and areas without cutting elements alternating with said cutting areas, vents for distributing the drilling fluid opening on to the areas and each being connected to the central conduit; the vents being constituted by elements whose resistance to abrasion is greater than that of the matrix of the tool.

The present invention relates to improvements in rotatable drilling tools having fluid blades, as well as a method of manufacturing a drilling tool of this type.

The invention relates more particularly to rotatable drilling tools having fluid blades of the full body or ring type, comprising a central input conduit or channel for the passage of a drilling fluid under pressure, a head having areas provided with cutting elements, such as diamonds, cutting edges made of tungsten carbide, or even individual cutting blades, and areas without cutting elements, these areas alternating, and the areas without cutting elements being generally located in a rearward position with respect to the areas having the cutting elements, vents for distributing the drilling fluid arranged in the head perpendicularly to said areas, and opening out on to said area provided with cutting elements and/or on the areas without cutting elements, and each connected to the central conduit or channel of the tool.

It is known that the efliciency of such a tool, ie its speed of advance, which is a function of the rotation speed of the tool and of its bearing pressure on the ground, in addition depends on the efficiency of the jet of the drilling fluid which itself depends upon the speed of the drilling fluid at the output of the vent, upon the distance between the lower extremity of the vent and the cutting face, and upon the abrasive properties and the density of the drilling fluid.

In drilling tools of the above mentioned type, the vents do not stand up to the abrasive elfects of the drilling fluid for a suflicient time, so that it is not possible to maintain the jet of fluid at a speed corresponding to its maximum efliciency. Moreover, when the vents are situated in the areas having no cutting elements, which areas are generally rearward of the cutting areas so as to allow the drilling fluid to evacuate the swarf and cuttings, the distance between the lower extremity of the vents and the cutting face is sufliciently large so that the efficiency of the jet is further diminished.

The present invention obviates or minimizes all the above mentioned disadvantages and has for a particular object the production of a drilling tool of the above mentioned type, the vents of which have a resistance which is suflicient to allow the use of a speed for the vents, maximum density and abrasiveuess of the drilling fluid, compatible with the drilling installation, as well as to permit the arrangement of the vents at a minimum distance from the cutting face, which distance must .be kept for a period which is at least as long as the life of the cutting elements of the areas themselves.

To this end, according to the invention, the vents of the rotatable drilling tool having fluid blades are constituted by elements, the resistance to abrasion of which is greater than that of the matrix of the tool and substantially equal to that of the cutting elements.

The elements constituting the vents are preferably embedded in the matrix and extend to the interior of the fluid input conduit or channel, so as to form at least one part of said conduit or channel in its narrow area, and so as to protect the matrix up to an area of the conduit or channel where the speed of the drilling fluid is sufliciently low.

The lower end of each of the vents may protrude beyond the surface of the areas without cutting elements, in which areas said vents are arranged, and are located at a distance from the cutting face which is substantially equal to the distance between the corresponding latitudinal line of the areas provided with cutting elements and the cutting face, i.e. at a distance which is substantially equal to the height of the arrangement of the actual cutting elements themselves.



+1
To nie jest błąd

Tab key still autocompleting on its own

chaiguy 13 lat temu Ostatnio zmodyfikowane przez Jon Skinner 13 lat temu 4
There appears to be some leftover code from the old autocomplete implementation still active because the tab key will occasionally attempt to complete the word before it, making it impossible for me to insert tabs.

Tab should only accept autocompletes when the autocomplete dialog is open, allowing me to escape out of that and insert tabs normally.
Odpowiedź
Jon Skinner 13 lat temu
This is by design. The behavior can be controlled with the tab_completion file setting.
+1

vintage mode copy should go into normal copy buffer too

Pat 12 lat temu zaktualizowano 12 lat temu 1

I like to alternate between normal copy/paste (especially copying inside of ST and pasting into, for example, the browser) and vintage mode copy/paste. The problem is that vintage mode doesn't put the copied text in the clipboard, so I can't paste it with Ctrl+V (and even worse, my clipboard monitor tool can't pick up the copy).


I understand that there are multiple buffers for copy/paste in vim. I suggest always putting copied text into the clipboard as well as any particular buffer specified by the user. In essence, this would mean that paste (in any application) would always paste the content from the latest copy command, however it was performed.

+1

Build scripts don't work with unicode paths

Jonathan Müller 12 lat temu Ostatnio zmodyfikowane przez Zen 12 lat temu 1
As mentioned here: http://www.sublimetext.com/forum/viewtopic.php?f=3&t=7414

Reproduce: create a python file, name it 'tést.py' (the accent is important), insert 'print "hello world"', try to run it via build script. Sublime Console will say:

Traceback (most recent call last):

File "./sublime_plugin.py", line 337, in run_

  return self.run(**args)

File "./exec.py", line 130, in run

UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 85: ordinal not in range(128)

Fix: 

+1

Possibility to set a default folder path to include when creating a new project

Jose Faeti 12 lat temu 0

One of the things I always do when creating a new project is adding a new folder to the project with the following path "../". Since I save the sublime project files in the "sublime" folder (contained inside the main project folder), this will effectively include the main folder of the project, located one path before the sublime folder, and allows me to change the project folder url at will if needed.

A setting for specifying a path to be included automatically on each new project like this (perhaps with regex or custom variables support) would be awesome.

+1

Auto-Expand folders that contain one subfolder

Jordan Parker 11 lat temu Ostatnio zmodyfikowane przez Zack Jones 11 lat temu 1
When in a project, if a folder with only one other folder below it is expanded by the user, continue to expand down the chain until actual content is reached.

Example: You've got a project with this code layout:
[project]/src/main/java/com/company/[project]/(actual code lives here)

You've got to click src, main, java, com, company, project to jump in to the place where your code lives. A few clicks could be saved if these would auto-expand.
+1

Posibility to combine parsers.

p4ul 12 lat temu 0

I tell HTML parser by some definition (as grammar rules?) to use CSS parser inside the <style> tag.


Then different syntax highlighting would work for specific sections. CSS highlighting in style element inside HTML. XML inside javascript string, etc...

+1

Openning two files with the same name but in different path

Célia Dehé 11 lat temu 0

When I open two files with the same name, but in different path, Sublime Text 2.0.2  (OS : Windows XP) crash. One of the file is in an openned folder on one window, the other is in another one, I open the second window with "Ctrl + Upcase + N". 


To get back Sublime Text, I have to delete the "Auto Save Session.sublime_session" file in "Data/Settings/".

+1

2.0: Pristine packages not getting extracted as they should

asmodai 12 lat temu 0

With 2.0 and build 2111 when I delete all packages from the %APPDATA%\Sublime Text 2\Packages directory (except User) I expect ST2 to, like in previous builds, repopulate the Packages directory from the Pristine Packages directory. This goes wrong now, I get:

"Error loading syntax file "Packages/Text/Plain text.tmLanguage": Error parsing plist xml: Failed to open file In file "Packages/Text/Plain text.tmLanguage"

And nothing in Packages gets repopulated from Pristine Packages. Even if you extract the contents from Text.sublime-package to Packages\Text ST2 does not extract the rest of the Pristine Packages to Packages. A major regression from previous versions/builds.

If you remove both Packages and Pristine Packages and start ST2 it does populate Pristine Packages and then Packages.

+1

Python: add scope entity.name.function.python for the actual function name in a function call

lanzz 12 lat temu zaktualizowano 12 lat temu 1

In the Python/Python.tmLanguage file, find this pattern:

<dict>
<key>begin</key>
<string>(?=[A-Za-z_][A-Za-z0-9_]*(?:\.[A-Za-z_][A-Za-z0-9_]*)*\s*\()</string>
<key>end</key>
<string>(?=\s*\()</string>
<key>patterns</key>
<array>
<dict>
<key>include</key>
<string>#dotted_name</string>
</dict>
</array>
</dict>
and add a scope name for this pattern:

<key>name</key>
<string>entity.name.function.python</string>
This would allow to highlight all function names inside a nested function call:
foo(bar(baz))


Without the above change, you cannot match both "foo" and "bar" function names; you can either match "meta.function-call" which would match "foo" but would also include all the parameters (thus also "baz", which is not a function name), or you can match "meta.function-call - meta.function-call.parameters" which would match "foo" but exclude the "bar" function name.