├── .gitignore ├── .travis.yml ├── CHANGELOG.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── addon-info.json ├── autoload └── syncopate.vim ├── doc └── syncopate.txt ├── instant └── flags.vim ├── plugin ├── commands.vim └── mappings.vim └── vroom ├── main.vroom └── setupvroom.vim /.gitignore: -------------------------------------------------------------------------------- 1 | doc/tags 2 | -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: generic 2 | env: 3 | matrix: 4 | - CI_TARGET=vim MAKTABA_VERSION=1.9.0 5 | - CI_TARGET=vim MAKTABA_VERSION=master 6 | - CI_TARGET=neovim MAKTABA_VERSION=master 7 | before_script: 8 | - sudo apt-get update 9 | - sudo apt-get install python3-dev 10 | - if [ $CI_TARGET = vim ]; then 11 | sudo apt-get install vim-gnome; 12 | elif [ $CI_TARGET = neovim ]; then 13 | eval "$(curl -Ss https://raw.githubusercontent.com/neovim/bot-ci/master/scripts/travis-setup.sh) nightly-x64" && 14 | wget https://bootstrap.pypa.io/get-pip.py && 15 | sudo python3 get-pip.py --allow-external sudo && 16 | sudo pip3 install neovim; 17 | fi 18 | - wget https://github.com/google/vroom/releases/download/v0.12.0/vroom_0.12.0-1_all.deb 19 | - sudo dpkg -i ./vroom_0.12.0-1_all.deb 20 | - git clone -b ${MAKTABA_VERSION} https://github.com/google/vim-maktaba.git ../maktaba/ 21 | - git clone https://github.com/google/vim-glaive.git ../glaive/ 22 | services: 23 | - xvfb 24 | script: 25 | - '[ $CI_TARGET = neovim ] && VROOM_ARGS="--neovim" || VROOM_ARGS=""' 26 | - vroom $VROOM_ARGS --crawl ./vroom/ 27 | matrix: 28 | fast_finish: true 29 | allow_failures: 30 | - env: CI_TARGET=neovim MAKTABA_VERSION=master 31 | -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | # Current changes 2 | 3 | ## Features 4 | 5 | - New `'operatorfunc'` function `syncopate#ClipboardOperatorfunc()`, and default mapping `,<`. 6 | - This lets you do things like `,<>` mapping uses this instead of browser export 17 | * `:HtmlExport` renamed to `:SyncopateExportToBrowser` for clarity 18 | * Users can choose browser command with `browser` option (see `:help syncopate:browser`) 19 | 20 | ## Bugfixes 21 | 22 | * Syncopate failed in non-writable directories (#2) 23 | * HTML output was unreadable (yellow-on-white) when `t_Co=8` (#5) 24 | * Better handling of `'background'` option (important for `solarized` colorscheme) (#6) 25 | * Direct-to-clipboard was eliminating users' background colours (#16) 26 | 27 | # 0.1.0 28 | 29 | *2014-11-19* 30 | 31 | ## Features 32 | 33 | * `:HtmlExport` command exports to a browser tab 34 | * Optional mapping (default: `<>`) to run `:HtmlExport` 35 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | Want to contribute? Great! First, read this page (including the small print at the end). 2 | 3 | ### Before you contribute 4 | Before we can use your code, you must sign the 5 | [Google Individual Contributor License Agreement](https://developers.google.com/open-source/cla/individual?csw=1) 6 | (CLA), which you can do online. The CLA is necessary mainly because you own the 7 | copyright to your changes, even after your contribution becomes part of our 8 | codebase, so we need your permission to use and distribute your code. We also 9 | need to be sure of various other things—for instance that you'll tell us if you 10 | know that your code infringes on other people's patents. You don't have to sign 11 | the CLA until after you've submitted your code for review and a member has 12 | approved it, but you must do it before we can put your code into our codebase. 13 | Before you start working on a larger contribution, you should get in touch with 14 | us first through the issue tracker with your idea so that we can help out and 15 | possibly guide you. Coordinating up front makes it much easier to avoid 16 | frustration later on. 17 | 18 | ### Code reviews 19 | All submissions, including submissions by project members, require review. We 20 | use Github pull requests for this purpose. 21 | 22 | ### The small print 23 | Contributions made by corporations are covered by a different agreement than 24 | the one above, the Software Grant and Corporate Contributor License Agreement. 25 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # syncopate 2 | 3 | (**Syn**)tax (**cop**)y-p(**a**)s(**te**). 4 | 5 | ## What's it for? 6 | 7 | To make sharing beautiful code as frictionless as possible. 8 | 9 | Say you have a nicely syntax-highlighted buffer in vim. 10 | This plugin lets you open a browser tab with that buffer's contents, including the highlighting. 11 | If you copy-paste into a webmail window, a Google Doc, etc., the syntax highlighting stays intact. 12 | 13 | Best of all, it cleans up after itself: it won't clutter your directories with `.html` files. 14 | 15 | ## How do I install it? 16 | 17 | Depends on your plugin manager. 18 | 19 | Note that syncopate is a [maktaba](https://github.com/google/vim-maktaba) plugin, so you will need to install maktaba (if your plugin manager doesn't handle dependencies). 20 | If you want to configure the plugin, we strongly recommend installing [glaive](https://github.com/google/vim-glaive) as well. 21 | 22 | Here are instructions for Vundle, the most popular plugin manager. 23 | Add the following lines between your `call vundle#begin()` and `call vundle#end()` lines. 24 | 25 | ```vim 26 | " Dependency; required for vim-syncopate. 27 | Plugin google/vim-maktaba 28 | 29 | " Strongly recommended: easy configuration of maktaba plugins. 30 | Plugin google/vim-glaive 31 | 32 | Plugin google/vim-syncopate 33 | ``` 34 | 35 | Syncopate is expected to work on any platform vim supports, but the default 36 | configuration may not work on your system and direct-to-clipboard support hasn't 37 | been implemented for some platforms. Contributions welcome! 38 | 39 | ### xclip 40 | 41 | Syncopate requires `xclip` to manipulate the clipboard. In most cases, 42 | installing it from your package manager should just work. 43 | 44 | Arch Linux's official repository has an `xclip` (0.12.4) which is too old: it 45 | doesn't support `--target`. Arch users should install `xclip-svn` from AUR: 46 | 47 | ``` 48 | yaourt -S xclip-svn 49 | ``` 50 | 51 | ## How do I use it? 52 | 53 | ### Use the clipboard directly 54 | 55 | Use the `:SyncopateExportToClipboard` command. 56 | It populates the clipboard with the contents of your buffer (or just part of it, if you're in visual mode), including highlighting. 57 | You can then paste your beautiful code into a compose window (such as Gmail). 58 | 59 | Of course, it's even better with a keymapping, which you can enable using Glaive: 60 | 61 | ```vim 62 | " This line needs to go anywhere after 'call vundle#end()'. 63 | call glaive#Install() 64 | 65 | " Enable keymappings. 66 | Glaive syncopate plugin[mappings] 67 | ``` 68 | 69 | By default, syncopate's mappings all start with the prefix `<`. 70 | You can change the prefix by giving `plugin[mappings]` a value, like so: 71 | ```vim 72 | Glaive syncopate plugin[mappings]='qwer' 73 | ``` 74 | The following examples will assume you're using the default prefix, and that your [``](http://stackoverflow.com/questions/1764263/what-is-the-leader-in-a-vimrc-file) is `,`. 75 | 76 | - `,<` calls `:SyncopateExportToClipboard` on whatever motion you choose. 77 | (e.g., `,` calls `:SyncopateExportToClipboard` on the whole buffer (or your selection in visual mode). 79 | 80 | ### Put it in a browser window 81 | 82 | Alternatively, you can use the `:SyncopateExportToBrowser` command. 83 | It opens the HTML in a new browser tab, so you can select regions interactively. 84 | Syncopate automatically cleans up the HTML file after opening the tab. 85 | 86 | If you use `:SyncopateExportToBrowser`, be sure to copy with `Ctrl-C` (as opposed to mouse selection/middle-click); otherwise, the highlighting will not be retained. 87 | 88 | ## How do I configure it? 89 | 90 | There are a variety of syncopate-specific options: whether to change the colorscheme, which browser to use, etc. 91 | See `:help syncopate-config`. 92 | 93 | For everything else, use the built-in options for the `:TOhtml` command: `:help 2html.vim`. 94 | (Options are down below, starting at `:help g:html_diff_one_file`.) 95 | 96 | For example, the following line will exclude line numbers from the output, even if you use them in vim: 97 | 98 | ```vim 99 | let g:html_number_lines = 0 100 | ``` 101 | 102 | ## So how's this different from plain :TOhtml? 103 | 104 | Mainly convenience. 105 | Under the hood, `:SyncopateExportToClipboard` will: 106 | 107 | 1. Switch to the default `colorscheme` (it shows up better on white backgrounds). 108 | 2. Create the HTML version of your vim buffer. 109 | 3. Export it to the clipboard. 110 | 4. Restore your `colorscheme`, and any other settings it needed to change. 111 | 112 | Simply running `:TOhtml` only does the second step. 113 | In particular, the third step is difficult to remember how to do. 114 | Without it, `:TOhtml` usually involves tiresome saving-and-subsequently-deleting of HTML files, and fiddling with a browser. 115 | -------------------------------------------------------------------------------- /addon-info.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "syncopate", 3 | "description": "Syntax-highlighted copy-paste", 4 | "version": "0.2.0", 5 | "author": "Google", 6 | "repository": {"type": "git", "url": "git://github.com/google/vim-syncopate"}, 7 | "dependencies": { 8 | "maktaba": {"type": "git", "url": "git://github.com/google/vim-maktaba"} 9 | } 10 | } 11 | -------------------------------------------------------------------------------- /autoload/syncopate.vim: -------------------------------------------------------------------------------- 1 | " Copyright 2014 Google Inc. All rights reserved. 2 | " 3 | " Licensed under the Apache License, Version 2.0 (the "License"); 4 | " you may not use this file except in compliance with the License. 5 | " You may obtain a copy of the License at 6 | " 7 | " http://www.apache.org/licenses/LICENSE-2.0 8 | " 9 | " Unless required by applicable law or agreed to in writing, software 10 | " distributed under the License is distributed on an "AS IS" BASIS, 11 | " WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 12 | " See the License for the specific language governing permissions and 13 | " limitations under the License. 14 | 15 | let s:plugin = maktaba#plugin#Get('syncopate') 16 | 17 | 18 | " Change vim settings to prepare for HTML export, and save the old values for 19 | " s:SyncopateRestoreSettings(). 20 | " 21 | " NOTE: Do not change this function without making a corresponding change in 22 | " s:SyncopateRestoreSettings(). 23 | function! s:SyncopateSaveAndChangeSettings() 24 | let l:change_colorscheme = maktaba#ensure#IsBool( 25 | \ s:plugin.Flag('change_colorscheme')) 26 | 27 | " For vim (as opposed to gvim), we will need to muck with 't_Co' to avoid 28 | " outputting really hideous/unreadable colors for HTML (which should always 29 | " have 256 colours available). 30 | let l:should_set_t_Co = !has('gui') 31 | 32 | " Save any settings we'll need to restore later. 33 | let l:setting_names = ['g:html_use_css'] 34 | if l:change_colorscheme 35 | call extend(l:setting_names, ['&background', 'g:colors_name']) 36 | endif 37 | if l:should_set_t_Co 38 | call extend(l:setting_names, ['&t_Co']) 39 | endif 40 | let l:settings = maktaba#value#SaveAll(l:setting_names) 41 | 42 | " Syncopate forces g:html_use_css to 0 (false). This outputs ugly deprecated 43 | " tags, but it's necessary to make sure the HTML shows up correctly in 44 | " email clients (which usually strip out