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