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 6K
  • Win 3K
  • OS X 2K
  • Linux 1K
Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6
Windows 0 0 0 0 0 0 1 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 1 0 0 0 0 1 0 0 1 0 1 0 1
OS X 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 2 1 0 0 0 1 0 0 0 0 0 1 0 0 2 1 0 0 0 0 0 0 0
Linux 0 3 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 0 0 0 1 1 1 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 1

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