Adam Strzelecki e59db8375f Use panel language unless spellingLanguage is specified
This partially reverts changes of 3fdc72b93a:
Support spell checking being “automatic by language”.

Before 3fdc72b spellingLanguage .tm_properties setting (default "en") was the
only way to set spelling language for file (buffer). English was default
language for all files. 3fdc72b introduced change that when “automatic by
language” was selected in system's spelling panel then TextMate was ignoring
spellingLanguage setting and was using automatic by language.

However because “automatic by language” is default on OS X, effectively 3fdc72b
makes spellingLanguage setting no longer effective. To make it work one needs
to set explicit spelling language either in System Preferences or in spelling
panel upon each TextMate run (since this is getting reset after application
restart) - which is counter-intuitive, can be treated as regression and it is
vaguely described in ChangeLog:

 * Support spell checking being “automatic by language”. This is set via the
   spelling panel.

This change presents alternative approach, introducing new empty
spellingLanguage setting "" (which is now default), which makes use system
panel language setting, including “automatic by language”.

From now on all files will be checked against system panel selected language
(or automatic), unless .tm_properties project specifies explicitly language for
given file using, eg.:

    [ locale-en_US.ini ]
    spellingLanguage = en_US

    [ locale-pl_PL.ini ]
    spellingLanguage = pl_PL

Or automatically depending on file name:

    [ locale-*.ini ]
    spellingLanguage = '${TM_FILEPATH/^.*locale-([a-z]+_[A-Z]+).*$/$1/}'
2016-01-29 08:46:18 +07:00
2016-01-15 12:07:16 +01:00
2016-01-15 12:07:16 +01:00
2015-09-07 18:27:16 +02:00
2014-07-24 22:47:55 +02:00
2016-01-15 12:07:16 +01:00
2016-01-15 12:07:16 +01:00
2013-03-20 14:39:52 +01:00
2012-08-09 16:25:56 +02:00
2012-08-09 16:25:56 +02:00

TextMate

Download

You can download TextMate from here.

Feedback

You can use the TextMate mailing list or #textmate IRC channel on freenode.net for questions, comments, and bug reports.

You can also contact MacroMates.

Before you submit a bug report please read the writing bug reports instructions.

Screenshot

textmate

Building

Bootstrap

To bootstrap the build you need to run ./configure (in the root of the source tree). You can set a few (environment) variables read by this script that change the generated build file:

  • builddir — location of built files. Defaults to ~/build/TextMate.
  • identity — for Apples codesign. Defaults to ad-hoc signing, which does not use an identity at all.
  • boostdir — location of boost includes. By default it will search various locations including MacPorts and Homebrew.
  • sparsedir — location of sparsehash includes. By default it will search various locations including MacPorts and Homebrew.
  • CC and CXX — C and C++ compiler.

In the simplest case you would run:

git clone https://github.com/textmate/textmate.git
cd textmate
git submodule update --init
./configure && ninja

Please note that if you downloaded the source code (rather than cloned via git) you likely miss the submodules and the build will therefore fail.

Prerequisites

To build the source the following must first be installed on your system:

You need to manually install Capn Proto if you're not using homebrew. To install the other dependencies via MacPorts run:

sudo port install ninja ragel boost multimarkdown mercurial sparsehash libressl

If port fails with a build error then likely you need to agree (system-wide) to Apples Xcode license:

sudo xcodebuild -license

To install using homebrew run:

brew install ragel boost multimarkdown hg ninja capnp google-sparsehash libressl

In practice hg (mercurial) is only required for the SCM librarys tests so you can skip this dependency if you dont mind a failing test.

OS X 10.7 (Lion)

If you are on OS X 10.7 you need pgrep and pkill (used by the “relaunch” build targets). To install using MacPorts:

sudo port install proctools

Or using homebrew:

brew install proctools

Building from within TextMate

You should install the Ninja and CxxTest bundles. Both can be installed via PreferencesBundles.

After this you can press ⌘B to build from within TextMate. In case you haven't already you also need to set up the PATH variable either in PreferencesVariables or ~/.tm_properties so it can find ninja and related tools; an example could be $PATH:/opt/local/bin.

The default target is TextMate/run. This will relaunch TextMate but when called from within TextMate, a dialog will appear before the current instance is killed. As there is full session restore, it is safe to relaunch even with unsaved changes.

If the current file is a test file then the target to build is changed to build the library to which the test belongs (this is done by setting TM_NINJA_TARGET in the .tm_properties file found in the root of the source tree).

Similarly, if the current file belongs to an application target (other than TextMate.app) then TM_NINJA_TARGET is set to build and run this application.

Build Targets

The build system classifies a target either as a library or an application. The latter can either be a bundled or non-bundled application. E.g. mate is non-bundled (just a mate executable) where TextMate.app is a bundled application.

For each output there are a few symbolic targets you can build. While the examples below refer to a specific library or application, they exist for all targets of same type.

For the io library:

ninja io                 # Build the io library and run tests.
ninja io/coerce          # Build the io library and skip tests.
ninja io/clean           # Remove the build folder for the io library.
ninja io/headers         # Copy exported headers to $builddir/include.

For the mate (non-bundled) application:

ninja mate               # Build the mate executable.
ninja mate/run           # Build and run the mate executable.
ninja mate/clean         # Remove the build folder for the mate executable.

For the TextMate.app application:

ninja TextMate           # Build and sign TextMate.app.
ninja TextMate/run       # Build, sign, and run TextMate.app.
ninja TextMate/clean     # Remove the build folder for TextMate.app.
ninja TextMate/dsym      # Create a tarball with extracted dSYM files.
ninja TextMate/tbz       # Create a tarball of TextMate.app. Also produce the dsym tarball.
ninja TextMate/deploy    # Push a nightly build. Fails without proper credentials :)

Note that ninja TextMate/clean only cleans the TextMate build folder ($builddir/Applications/TextMate), but all libraries and applications it depends on are not cleaned.

To clean everything run:

ninja -t clean

Legal

The source for TextMate is released under the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

TextMate is a trademark of Allan Odgaard.

Description
No description provided
Readme GPL-3.0 69 MiB
Languages
Objective-C++ 53.4%
C++ 40.8%
Ruby 2.5%
Objective-C 2.3%
C 0.4%
Other 0.5%