ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Move​Text

Select text and drag it around, or setup a text tunnel to move code from one location to another.

Details

Installs

  • Total 5K
  • Win 2K
  • OS X 2K
  • Linux 1K
Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14 May 13 May 12 May 11 May 10 May 9 May 8 May 7
Windows 0 0 2 0 1 1 1 0 0 0 0 0 0 1 0 2 0 0 1 0 0 1 0 1 1 0 0 0 0 0 0 1 0 0 0 3 0 1 0 2 2 1 0 0 1 2
OS X 0 0 0 0 0 1 2 0 0 0 1 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 1 2 0 0 0 0 0 0 2 0 2 0 0 0 0 1 1 0
Linux 0 1 0 0 1 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 0 0 0 0 0 3 1 0 0 0 0 0 0 1 0

Readme

Source
raw.​githubusercontent.​com

MoveText

Select text and move it around using the keyboard, or setup a text “tunnel” to move code from one location to another.

Installation

  1. Using Package Control, install “MoveText”

Or:

  1. Open the Sublime Text Packages folder

    • OS X: ~/Library/Application Support/Sublime Text 3/Packages/
    • Windows: %APPDATA%/Sublime Text 3/Packages/
    • Linux: ~/.Sublime Text 3/Packages/ or ~/.config/sublime-text-3/Packages
  2. clone this repo

  3. Install keymaps for the commands (see Example.sublime-keymap for my preferred keys)

Commands

move_text_left: Moves the selected text one character to the left

move_text_right: Moves the selected text one character to the right

move_text_up: Moves the selected text one line up

move_text_down: Moves the selected text one line down

When moving text up and down, funny things happen when the destination line doesn't have enough preceding characters. An attempt is made to keep the text on the same column, but the mechanism for this uses sublime.View.command_history, which doesn't update after every movement. It updates in between “Undo” events, so if you move the text in the opposite direction, or if you pause long enough for an “undo” to register, the text will move correctly. It looks like this:

1. one*dragme*  1. one          1. one       1. one
2. two          2. two*dragme*  2. two       2. two
3.              3.              3. *dragme*  3.
4. four         4. four         4. four      4. *dragme*four

But if you move the text up first, it will move correctly:

1. one          1. one*dragme*  1. one          1. one       1. one
2. two*dragme*  2. two          2. two*dragme*  2. two       2. two
3.              3.              3.              3. *dragme*  3.
4. four         4. four         4. four         4. four      4. fou*dragme*r