Git Product home page Git Product logo

vim-session's Introduction

Extended session management for Vim

The vim-session plug-in improves upon Vim's built-in :mksession command by enabling you to easily and (if you want) automatically persist and restore your Vim editing sessions. It works by generating a Vim script that restores your current settings and the arrangement of tab pages and/or split windows and the files they contain.

To persist your current editing session you can execute the :SaveSession command. If you don't provide a name for the session 'default' is used (you can change this name with an option). You're free to use whatever characters you like in session names. When you want to restore your session simply execute :OpenSession. Again the name 'default' is used if you don't provide one. When a session is active, has been changed and you quit Vim you'll be prompted whether you want to save the open session before quitting Vim:

Screenshot of auto-save prompt

If you want, the plug-in can also automatically save your session every few minutes (see the g:session_autosave_periodic option). When you start Vim without editing any files and the default session exists, you'll be prompted whether you want to restore the default session:

Screenshot of auto-open prompt

When you start Vim with a custom server name that matches one of the existing session names then the matching session will be automatically restored. For example I use several sessions to quickly edit my Vim plug-ins:

$ gvim --servername easytags-plugin
$ gvim --servername session-plugin
$ # etc.

The session scripts created by this plug-in are stored in the directory ~/.vim/sessions (on UNIX) or ~\vimfiles\sessions (on Windows) but you can change the location by setting g:session_directory. If you're curious what the session scripts generated by vim-session look like see the sample below.

If you're still getting to know the plug-in, the "Sessions" menu may help: It contains menu items for most commands defined by the plug-in.

Installation

Please refer to the [installation instructions] howto-install available on GitHub. Once you've installed the plug-in the commands below will be available to you.

Commands

Note that environment variables inside command arguments are expanded by the plug-in.

The :SaveSession command

This command saves your current editing session just like Vim's built-in :mksession command does. The difference is that you don't pass a full pathname as argument but just a name, any name really. Press <Tab> to get completion of existing session names. If you don't provide an argument the default session name is used, unless an existing session is open in which case the name of that session will be used.

If the session you're trying to save is already active in another Vim instance you'll get a warning and nothing happens. You can use a bang (!) as in :SaveSession! ... to ignore the warning and save the session anyway.

Your session script will be saved in the directory pointed to by the g:session_directory option.

The :OpenSession command

This command is basically :source in disguise, but it supports tab completion of session names and it executes :CloseSession before opening the session. When you don't provide a session name and only a single session exists then that session is opened, otherwise the plug-in will ask you to select one from a list:

Please select the session to restore:

 1. vim-profile
 2. session-plugin
 3. etc.

Type number and <Enter> or click with mouse (empty cancels):

If the session you're trying to open is already active in another Vim instance you'll get a warning and nothing happens. You can use a bang (!) as in :OpenSession! ... to ignore the warning and open the session anyway.

Note also that when you use a bang (!) right after the command name existing tab pages and windows are closed, discarding any changes in the files you were editing!

The :RestartVim command

This command saves your current editing session, restarts Vim and restores your editing session. This can come in handy when you're debugging Vim scripts which can't be easily/safely reloaded using a more lightweight approach. It should work fine on Windows and UNIX alike but because of technical limitations it only works in graphical Vim.

Any commands following the :RestartVim command are intercepted and executed after Vim is restarted and your session has been restored. This makes it easy to perform manual tests which involve restarting Vim, e.g. :RestartVim | edit /path/to/file | call MyTest().

The :CloseSession command

This command closes all but the current tab page and window and then edits a new, empty buffer. If a session is loaded when you execute this command the plug-in will first ask you whether you want to save that session.

Note that when you use a bang (!) right after the command name existing tab pages and windows are closed, discarding any changes in the files you were editing!

The :DeleteSession command

Using this command you can delete any of the sessions created by this plug-in. If the session you are trying to delete is currently active in another Vim instance you'll get a warning and nothing happens. You can use a bang (!) as in :DeleteSession! ... to ignore the warning and delete the session anyway.

Note that this command only deletes the session script, it leaves your open tab pages and windows exactly as they were.

The :ViewSession command

Execute this command to view the Vim script generated for a session. This command is useful when you need to review the generated Vim script repeatedly, for example while debugging or modifying the vim-session plug-in.

Tab scoped sessions

When ['sessionoptions'] sessionoptions contains 'tabpages' (this is the default) session scripts will persist and restore all windows in all tab pages. When you remove 'tabpages' from ['sessionoptions'] sessionoptions you get a sort of light-weight sessions: They are constrained to a single tab page. Vim's :mksession mksession command and the vim-session plug-in both fully support this.

You can change ['sessionoptions'] sessionoptions in your [vimrc script] vimrc but then you can never save a session including tab pages. To decide on the spot whether you want a global or tab scoped session, the vim-session plug-in defines the three commands documented below.

Note that tab scoped sessions are regular session scripts, so when you load a tab scoped session using :OpenSession instead of :OpenTabSession the vim-session plug-in assumes it is a global session and will close all active tab pages before opening the tab scoped session.

The :OpenTabSession command

Just like :OpenSession but applies only to the current tab page.

The :SaveTabSession command

Just like :SaveSession but applies only to the current tab page.

The :AppendTabSession command

This command opens a new tab page and loads the given tab scoped session in that tab page. You can give this command a count just like [:tabnew] tabnew.

The :CloseTabSession command

Just like :CloseSession but applies only to the current tab page.

Options

The following Vim options and plug-in options (global variables) can be used to configure the plug-in to your preferences.

The sessionoptions setting

Because the vim-session plug-in uses Vim's :mksession command you can change how it works by setting 'sessionoptions' in your [vimrc script] vimrc, for example:

" If you only want to save the current tab page:
set sessionoptions-=tabpages

" If you don't want help windows to be restored:
set sessionoptions-=help

A lot of people don't like Vim's default behavior of saving hidden and unloaded buffers in sessions (which vim-session inherits due to the use of :mksession). To disable this behavior you can add the following line to your [vimrc script] vimrc:

" Don't save hidden and unloaded buffers in sessions.
set sessionoptions-=buffers

Note that the vim-session plug-in automatically and unconditionally executes the following change just before saving a session:

" Don't persist options and mappings because it can corrupt sessions.
set sessionoptions-=options

The g:session_directory option

This option controls the location of your session scripts. Its default value is ~/.vim/sessions (on UNIX) or ~\vimfiles\sessions (on Windows). If you don't mind the default you don't have to do anything; the directory will be created for you. Note that a leading ~ is expanded to your current home directory ($HOME on UNIX, %USERPROFILE% on Windows).

The g:session_lock_directory option

The vim-session plug-in uses lock files to prevent double loading of sessions. The default location (directory) of these lock files depends on a couple of factors:

  1. If you have explicitly set the g:session_lock_directory option that defines the directory.
  2. If the directory /var/lock exists and is writable that is used as a sane default.
  3. As a sane fall back for platforms where /var/lock is not available the directory that stores the session scripts themselves is used.

The g:session_lock_enabled option

Depending on your workflow locking of editing sessions can get annoying at times, so if you don't care about opening a session more than once and potentially "losing a version of your session" then you can use this option to completely disable session locking as follows:

" Disable all session locking - I know what I'm doing :-).
let g:session_lock_enabled = 0

The g:session_default_name option

The name of the default session without directory or filename extension (you'll never guess what the default is).

The g:session_default_overwrite option

If you set this to true (1), every Vim instance without an explicit session loaded will overwrite the default session (the last Vim instance wins).

The g:session_extension option

The filename extension of session scripts. This should include the dot that separates the basename from the extension. Defaults to '.vim'.

The g:session_autoload option

By default this option is set to 'prompt'. This means that when you start Vim without opening any files and the default session script exists, the session plug-in will ask whether you want to restore your default session. When you set this option to 'yes' and you start Vim without opening any files the default session will be restored without a prompt. To completely disable automatic loading you can set this option to 'no'.

The g:session_autosave option

By default this option is set to 'prompt'. When you've opened a session and you quit Vim, the session plug-in will ask whether you want to save the changes to your session. Set this option to 'yes' to always automatically save open sessions when you quit Vim. To completely disable automatic saving you can set this option to 'no'.

The g:session_autosave_to option

If g:session_autosave is 'yes' and this option is a nonempty string, automatic session saving always saves to the session with the name given by g:session_autosave_to regardless of what the current session is or any other options. In particular, g:session_default_overwrite does not have any effect. By default this option isn't set so none of this applies. Refer to [pull request 81] 81 for a more detailed use case.

The g:session_autosave_periodic option

This option sets the interval in minutes for automatic, periodic saving of active sessions. The default is zero which disables the feature.

Note that when the plug-in automatically saves a session (because you enabled this feature) the plug-in will not prompt for your permission.

The g:session_autosave_silent option

If you set this option to true (1) the messages normally emitted by automatic, periodic saving of active sessions are silenced.

The g:session_verbose_messages option

The session load/save prompts are quite verbose by default because they explain how to disable the prompts. If you find the additional explanation distracting you can lower the verbosity by setting this option to 0 (false) in your [vimrc script] vimrc.

The g:session_default_to_last option

By default this option is set to false (0). When you set this option to true (1) and you start Vim, the session plug-in will open your last used session instead of the default session. Note that the session plug-in will still show you the dialog asking whether you want to restore the last used session. To get rid of the dialog you have to set g:session_autoload to 'yes'.

The g:session_persist_font option

By default the plug-in will save the GUI font with the session to be reused the next time that session is loaded, this can be disabled by adding the following line to your [vimrc script] vimrc:

:let g:session_persist_font = 0

The g:session_persist_colors option

By default the plug-in will save the color scheme and the ['background' option] bg with the session to be reused the next time that session is loaded, this can be disabled by adding the following line to your [vimrc script] vimrc:

:let g:session_persist_colors = 0

The g:session_persist_globals option

The vim-session plug-in uses Vim's :mksession mksession command but it changes 'sessionoptions' so that Vim options and mappings are not persisted. The plug-in does this because persistence of options and mappings can break loading of sessions, in other words it's fragile (in my opinion).

If you want the plug-in to persist specific global variables or options you can add their names to the list g:session_persist_globals in your [vimrc script] vimrc:

" Persist the value of the global option 'makeprg'.
let g:session_persist_globals = ['&makeprg']

Because the [vimrc script] vimrc is loaded before the plug-in you have to define the list yourself. To persist multiple values:

" Persist all options related to :make.
let g:session_persist_globals = ['&makeprg', '&makeef']

Here's how you persist global variables: (in this case the variables of the session plug-in itself :-)

" Persist the options of the session plug-in using the session plug-in...
let g:session_persist_globals = ['&sessionoptions']
call add(g:session_persist_globals, 'g:session_autoload')
call add(g:session_persist_globals, 'g:session_autosave')
call add(g:session_persist_globals, 'g:session_default_to_last')
call add(g:session_persist_globals, 'g:session_persist_globals')

The example above doesn't persist the g:session_directory variable because this variable is used before loading a session script so persisting it inside the session script is pointless.

The g:session_restart_environment option

This option is a list of environment variable names (without the dollar signs) that the :RestartVim command will pass on to the new instance of Vim. This option is only useful on UNIX. By default the three environment variables $TERM, $VIM and $VIMRUNTIME are included in this list.

The g:session_command_aliases option

The names of the commands defined by the session plug-in start with the action they perform, followed by the string 'Session'. Some people prefer it the other way around because they find it easier to remember and you can type :Session<Tab> to get completion of all available commands (actually this works with the other style as well if you type :*Session<Tab> but I digress). If you are one of those people you can enable this option in your [vimrc script] vimrc like this:

:let g:session_command_aliases = 1

When this option is enabled the session plug-in will define the following command aliases:

  • SessionOpen is an alias for OpenSession
  • SessionView is an alias for ViewSession
  • SessionSave is an alias for SaveSession
  • SessionDelete is an alias for DeleteSession
  • SessionClose is an alias for CloseSession

Then there are the command aliases for tab scoped sessions:

  • SessionTabOpen is an alias for OpenTabSession
  • SessionTabSave is an alias for SaveTabSession
  • SessionTabAppend is an alias for AppendTabSession
  • SessionTabClose is an alias for CloseTabSession

The aliases support tab completion just like the real commands; they're exactly the same except for the names.

When you enable the aliases, the default command names will still be available. If you really don't like them, feel free to delete them using [:delcommand] delcommand.

The g:session_menu option

By default the plug-in installs a top level menu. If you don't like this you can disable it by adding the following line to your [vimrc script] vimrc:

:let g:session_menu = 0

The g:session_name_suggestion_function option

The default completion of the :SaveSession command is based on the names of the existing sessions. You can add your own suggestions using this option by setting the option to the name of a Vim script function. By default this option is set to an example function that suggests the name of the current git or Mercurial feature branch (when you're working in a version control repository).

The g:loaded_session option

This variable isn't really an option but if you want to avoid loading the vim-session plug-in you can set this variable to any value in your [vimrc script] vimrc:

:let g:loaded_session = 1

Compatibility with other plug-ins

Vim's :mksession command isn't really compatible with plug-ins that create buffers with generated content and because of this the vim-session plug-in includes specific workarounds for a couple of popular plug-ins:

If your favorite plug-in doesn't work with the vim-session plug-in drop me a mail and I'll see what I can do. Please include a link to the plug-in in your e-mail so that I can install and test the plug-in.

Function reference

The documentation of the 39 functions below was extracted from 2 Vim scripts on April 1, 2015 at 22:22.

Public API for the vim-session plug-in

The xolox#session#save_session() function

Save the current Vim editing session to a Vim script using the :mksession [] command and some additional Vim magic provided by the vim-session plug-in. When the generated session script is later sourced using the :source [] command (possibly in another process or even on another machine) it will restore the editing session to its previous state (provided all of the files involved in the session are still there at their original locations).

The first argument is expected to be a list, it will be extended with the lines to be added to the session script. The second argument is expected to be the filename under which the script will later be saved (it's embedded in a comment at the top of the script).

The xolox#session#save_globals() function

Serialize the values of the global variables configured by the user with the g:session_persist_globals option. The first argument is expected to be a list, it will be extended with the lines to be added to the session script.

The xolox#session#save_features() function

Save the current state of the following Vim features:

  • Whether syntax highlighting is enabled (:syntax on)
  • Whether file type detection is enabled (:filetype on)
  • Whether file type plug-ins are enabled (:filetype plugin on)
  • Whether file type indent plug-ins are enabled (:filetype indent on)

The first argument is expected to be a list, it will be extended with the lines to be added to the session script.

The xolox#session#save_colors() function

Save the current color scheme and background color. The first argument is expected to be a list, it will be extended with the lines to be added to the session script.

The xolox#session#save_fullscreen() function

Save the full screen state of Vim. This function provides integration between my vim-session [] and vim-shell [] plug-ins. The first argument is expected to be a list, it will be extended with the lines to be added to the session script.

The xolox#session#save_qflist() function

Save the contents of the quick-fix list. The first argument is expected to be a list, it will be extended with the lines to be added to the session script.

The xolox#session#save_state() function

Wrapper for the :mksession [] command that slightly massages the generated Vim script to get rid of some strange quirks in the way Vim generates sessions. Also implements support for buffers with content that was generated by other Vim plug-ins. The first argument is expected to be a list, it will be extended with the lines to be added to the session script.

The xolox#session#save_special_windows() function

Implements support for buffers with content that was generated by other Vim plug-ins. The first argument is expected to be a list, it will be extended with the lines to be added to the session script.

The xolox#session#auto_load() function

Automatically load the default or last used session when Vim starts. Normally called by the VimEnter [] automatic command event.

The xolox#session#is_empty() function

Check that the user has started Vim without editing any files. Used by xolox#session#auto_load() to determine whether automatic session loading should be performed. Currently checks the following conditions:

  1. That the current buffer is either empty (contains no lines and is not modified) or showing vim-startify [].
  2. That the buffer list either empty or persistent.

The xolox#session#auto_save() function

Automatically save the current editing session when Vim is closed. Normally called by the VimLeavePre [] automatic command event.

The xolox#session#auto_save_periodic() function

Automatically saves the current editing session every few minutes. Normally called by the CursorHold [] and CursorHoldI [] automatic command events.

The xolox#session#auto_unlock() function

Automatically unlock all sessions when Vim quits. Normally called by the VimLeavePre [] automatic command event.

The xolox#session#prompt_for_name() function

Prompt the user to select one of the existing sessions. The first argument is expected to be a string describing what will be done to the session once it's been selected. Returns the name of the selected session as a string. If no session is selected an empty string is returned. Here's an example of what the prompt looks like:

:call xolox#session#prompt_for_name('trash')

Please select the session to trash:

 1. first-session
 2. second-session
 3. third-session

Type number and <Enter> or click with mouse (empty cancels):

If only a single session exists there's nothing to choose from so the name of that session will be returned directly, without prompting the user.

The xolox#session#name_to_path() function

Convert the name of a session (the first argument, expected to be a string) to an absolute pathname. Any special characters in the session name will be encoded using URL encoding. This means you're free to use whatever naming conventions you like (regardless of special characters like slashes). Returns a string.

The xolox#session#path_to_name() function

Convert the absolute pathname of a session script (the first argument, expected to be a string) to a session name. This function assumes the absolute pathname refers to the configured session directory, but it does not check for it nor does it require it (it simple takes the base name of the absolute pathname of the session script and decodes it). Returns a string.

The xolox#session#get_names() function

Get the names of all available sessions. This scans the directory configured with g:session_directory for files that end with the suffix configured with g:session_extension, takes the base name of each file and decodes any URL encoded characters. Returns a list of strings.

If the first argument is true (1) then the user defined function configured with g:session_name_suggestion_function is called to find suggested session names, which are prefixed to the list of available sessions, otherwise the argument should be false (0).

The xolox#session#complete_names() function

Completion function for user defined Vim commands. Used by commands like :OpenSession and :DeleteSession (but not :SaveSession) to support user friendly completion.

The xolox#session#complete_names_with_suggestions() function

Completion function for the Vim command :SaveSession.

The xolox#session#is_tab_scoped() function

Determine whether the current session is tab scoped or global. Returns 1 (true) when the session is tab scoped, 0 (false) otherwise.

The xolox#session#find_current_session() function

Find the name of the current tab scoped or global session. Returns a string. If no session is active an empty string is returned.

The xolox#session#get_label() function

Get a human readable label based on the scope (tab scoped or global) and name of a session. The first argument is the name (a string) and the second argument is a boolean indicating the scope of the session; 1 (true) means tab scoped and 0 (false) means global scope. Returns a string.

The xolox#session#options_include() function

Check whether Vim's sessionoptions [] option includes the keyword given as the first argument (expected to be a string). Returns 1 (true) when it does, 0 (false) otherwise.

The xolox#session#include_tabs() function

Check whether Vim's sessionoptions [] option includes the tabpages keyword. Returns 1 (true) when it does, 0 (false) otherwise.

The xolox#session#change_tab_options() function

Temporarily change Vim's sessionoptions [] option so we can save a tab scoped session. Saves a copy of the original value to be restored later.

The xolox#session#restore_tab_options() function

Restore the original value of Vim's sessionoptions [] option.

The xolox#session#locking_enabled() function

Check whether session locking is enabled. Returns true (1) when locking is enabled, false (0) otherwise.

By default session locking is enabled but users can opt-out by setting g:session_lock_enabled to false (0).

Example function for session name suggestions

The xolox#session#suggestions#vcs_feature_branch() function

This function implements an example of a function that can be used with the g:session_name_suggestion_function option. It finds the name of the current git or Mercurial feature branch (if any) and suggests this name as the name for the session that is being saved with :SaveSession. Returns a list with one string on success and an empty list on failure.

Troubleshooting

Using multiple platforms (multi boot, Cygwin, etc.)

Session scripts cannot be shared between platforms because they contain absolute pathnames that most certainly won't match between e.g. Windows and Linux or even Windows and Cygwin. The best you can do is keep separate session scripts for different platforms (and I would certainly consider Cygwin a separate platform altogether :-). For more information please refer to [issue 85] 85.

Contact

If you have questions, bug reports, suggestions, etc. the author can be contacted at [email protected]. The latest version is available at http://peterodding.com/code/vim/session/ and http://github.com/xolox/vim-session. If you like the script please vote for it on Vim Online.

License

This software is licensed under the MIT license. © 2015 Peter Odding <[email protected]> and Ingo Karkat.

Thanks go out to everyone who has helped to improve the vim-session plug-in (whether through pull requests, bug reports or personal e-mails).

Sample session script

Here's an example session script generated by the vim-session plug-in while I was editing the plug-in itself in Vim:

" ~/.vim/sessions/example.vim: Vim session script.
" Created by session.vim on 30 August 2010 at 05:26:28.
" Open this file in Vim and run :source % to restore your session.

set guioptions=aegit
set guifont=Monaco\ 13
if exists('g:syntax_on') != 1 | syntax on | endif
if exists('g:did_load_filetypes') != 1 | filetype on | endif
if exists('g:did_load_ftplugin') != 1 | filetype plugin on | endif
if exists('g:did_indent_on') != 1 | filetype indent on | endif
if !exists('g:colors_name') || g:colors_name != 'slate' | colorscheme slate | endif
call setqflist([])
let SessionLoad = 1
if &cp | set nocp | endif
let s:so_save = &so | let s:siso_save = &siso | set so=0 siso=0
let v:this_session=expand("<sfile>:p")
silent only
cd ~/Development/Vim/vim-session
if expand('%') == '' && !&modified && line('$') <= 1 && getline(1) == ''
  let s:wipebuf = bufnr('%')
endif
set shortmess=aoO
badd +473 ~/Development/Vim/vim-session/autoload.vim
badd +1 ~/Development/Vim/vim-session/README.md
badd +1 ~/Development/Vim/vim-session/session.vim
badd +1 ~/Development/Vim/vim-session/TODO.md
set lines=43 columns=167
edit ~/Development/Vim/vim-session/README.md
set splitbelow splitright
set nosplitbelow
set nosplitright
wincmd t
set winheight=1 winwidth=1
argglobal
let s:l = 28 - ((27 * winheight(0) + 21) / 42)
if s:l < 1 | let s:l = 1 | endif
exe s:l
normal! zt
28
normal! 0
tabedit ~/Development/Vim/vim-session/TODO.md
set splitbelow splitright
set nosplitbelow
set nosplitright
wincmd t
set winheight=1 winwidth=1
argglobal
let s:l = 6 - ((5 * winheight(0) + 21) / 42)
if s:l < 1 | let s:l = 1 | endif
exe s:l
normal! zt
6
normal! 0
tabedit ~/Development/Vim/vim-session/session.vim
set splitbelow splitright
set nosplitbelow
set nosplitright
wincmd t
set winheight=1 winwidth=1
argglobal
let s:l = 17 - ((16 * winheight(0) + 21) / 42)
if s:l < 1 | let s:l = 1 | endif
exe s:l
normal! zt
17
normal! 014l
tabedit ~/Development/Vim/vim-session/autoload.vim
set splitbelow splitright
set nosplitbelow
set nosplitright
wincmd t
set winheight=1 winwidth=1
argglobal
let s:l = 473 - ((41 * winheight(0) + 21) / 42)
if s:l < 1 | let s:l = 1 | endif
exe s:l
normal! zt
473
normal! 018l
tabnext 4
if exists('s:wipebuf')
  silent exe 'bwipe ' . s:wipebuf
endif
unlet! s:wipebuf
set winheight=1 winwidth=1 shortmess=filnxtToO
let s:sx = expand("<sfile>:p:r")."x.vim"
if file_readable(s:sx)
  exe "source " . fnameescape(s:sx)
endif
let &so = s:so_save | let &siso = s:siso_save
doautoall SessionLoadPost
unlet SessionLoad

vim-session's People

Contributors

axujen avatar blueyed avatar cirosantilli avatar cpixl avatar inkarkat avatar roryokane avatar svermeulen avatar tarmack avatar xolox avatar yakloinsteak avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vim-session's Issues

Not restore nerdtree window

When open a nerdtree window and save session and quite vim, then open vim open that session, the nerdtree's left window will open, but is a blank window.

Session not marked as dirty when files loading into buffer

Hi,

I found when I opened multiple files for editing, but didn't create a new window or tab, the session wasn't marked as dirty and therefore wasn't saved on exit.

Replacing WinEnter with BufEnter on line 65 of session.vim should solve the problem.

Mark

auto save/load not working

i installed this plugin without any modification
commands all run well
but just no autosave/load even i enabled the opts.
echo checked in vim, they are set to 1
but still no luck...
anything i miss?
what i put in my vimrc is:

let g:session_autosave = 1
let g:session_autoload = 1

also tried;

let g:session_command_aliases = 1
let g:session_directory = "~/.vim_runtime/sessions"
let g:session_autoload = 'yes'
let g:session_autosave = 'yes'

no luck..
thanks

after a bundleUpdate,it cannot work

Error detected while processing function xolox#session#auto_load:
line 8:
E117: Unknown function: xolox#misc#option#split
Press ENTER or type command to continue
Error detected while processing function xolox#session#auto_load:
line 8:
E116: Invalid arguments for function index(xolox#misc#option#split(&viminfo), '%') >= 0)
Press ENTER or type command to continue
Error detected while processing function xolox#session#auto_load:
line 8:
E15: Invalid expression: (index(xolox#misc#option#split(&viminfo), '%') >= 0)
Press ENTER or type command to continue
Error detected while processing function xolox#session#auto_load..xolox#session#get_names:
line 1:
E121: Undefined variable: g:session_directory
Press ENTER or type command to continue
Error detected while processing function xolox#session#auto_load..xolox#session#get_names:
line 1:
E116: Invalid arguments for function xolox#misc#path#absolute(g:session_directory)
Press ENTER or type command to continue
Error detected while processing function xolox#session#auto_load..xolox#session#get_names:
line 1:
E15: Invalid expression: xolox#misc#path#absolute(g:session_directory)
Press ENTER or type command to continue
Error detected while processing function xolox#session#auto_load..xolox#session#get_names:
line 2:
E121: Undefined variable: directory
Press ENTER or type command to continue
Error detected while processing function xolox#session#auto_load..xolox#session#get_names:
line 2:
E116: Invalid arguments for function xolox#misc#path#merge(directory, '*' . g:session_extension)), "\n")

Stack trace on vim startup

Hello. After I've updated vim-session plugin I have an error popup on my gvim startup with following message:

Error detected while processing C:\Users\rgr.vim\bundle\vim-session\plug
in\session.vim:
line 72: E117: Unknown function: xolox#misc#os#is_win
E15: Invalid expression: xolox#misc#os#is_win()
line 86:
E121: Undefined variable: g:session_directory
E116: Invalid arguments for function fnamemodify(g:session_directory, ':p')
E15: Invalid expression: fnamemodify(g:session_directory, ':p')
line 87:
E121: Undefined variable: s:directory
E116: Invalid arguments for function isdirectory(s:directory)
E15: Invalid expression: !isdirectory(s:directory)
line 90:
E121: Undefined variable: s:directory
E116: Invalid arguments for function filewritable(s:directory) != 2
E15: Invalid expression: filewritable(s:directory) != 2
line 96:
E108: No such variable: "s:directory"

a lot of errors

I install this plugin with pathogen
vim version is 7.3.1136

qq20130628234355

E121: Undefined variable: a:var

I'm having issues on default installation of this plugin.

Steps to reproduce my issue:

  1. Install latest plugin (via pathogen + git clone)
  2. gvim /tmp/test.txt

  3. :w
  4. :SaveSession (session.vim 1.7: Saved 'default' session to ~/.vim/sessions/default.vim.)
  5. :q
  6. gvim

During gvim startup I see an error message:

Error detected while processing function xolox#session#auto_load..54_prompt:
line 9:
E121: Undefined variable: a:var
Press ENTER or type command to continue

Please note that I'm not doing any configuration. Just installing

Here is my ~/.vim/sessions/default.vim:

" ~/.vim/sessions/default.vim: Vim session script.
" Created by session.vim 1.7 on 03 May 2013 at 13:24:15.
" Open this file in Vim and run :source % to restore your session.

set guioptions=aegimrLtT
silent! set guifont=
if exists('g:syntax_on') != 1 | syntax on | endif
if exists('g:did_load_filetypes') != 1 | filetype on | endif
if exists('g:did_load_ftplugin') != 1 | filetype plugin on | endif
if exists('g:did_indent_on') != 1 | filetype indent on | endif
if &background != 'dark'
        set background=dark
endif
if !exists('g:colors_name') || g:colors_name != 'solarized' | colorscheme solarized | endif
call setqflist([])
let SessionLoad = 1
if &cp | set nocp | endif
let s:so_save = &so | let s:siso_save = &siso | set so=0 siso=0
let v:this_session=expand("<sfile>:p")
silent only
cd ~/.vim/sessions
if expand('%') == '' && !&modified && line('$') <= 1 && getline(1) == ''
  let s:wipebuf = bufnr('%')
endif
set shortmess=aoO
badd +1 /tmp/test.txt
silent! argdel *
edit /tmp/test.txt
set splitbelow splitright
set nosplitbelow
set nosplitright
wincmd t
set winheight=1 winwidth=1
" argglobal
setlocal fdm=manual
setlocal fde=0
setlocal fmr={{{,}}}
setlocal fdi=#
setlocal fdl=0
setlocal fml=1
setlocal fdn=20
setlocal fen
silent! normal! zE
let s:l = 1 - ((0 * winheight(0) + 20) / 41)
if s:l < 1 | let s:l = 1 | endif
exe s:l
normal! zt
1
normal! 0
tabnext 1
if exists('s:wipebuf')
  silent exe 'bwipe ' . s:wipebuf
endif
unlet! s:wipebuf
set winheight=1 winwidth=20 shortmess=filnxtToO
let s:sx = expand("<sfile>:p:r")."x.vim"
if file_readable(s:sx)
  exe "source " . fnameescape(s:sx)
endif
let &so = s:so_save | let &siso = s:siso_save
tabnext 1
1wincmd w
doautoall SessionLoadPost
unlet SessionLoad
" vim: ft=vim ro nowrap smc=128

background color lost

hi - I use the solarized theme which is configured in this way:

set t_Co=256
set background=dark
let g:solarized_termcolors=256
colorscheme solarized

after loading a session with OpenSession, the background is set to light instead of dark -
is there a way to save also the background variable?

Option to set default session name

I'd love to have an option to configure the default name vim-session uses.

My use case: I'd like to only use vim-session when I'm working on big projects, and I'd like to save a session per project. I'm using g:session_directory = '.' to save the session to the project directory, but I want to have the name be a dotfile that I can easily ignore (and also put in my global gitignore). I manually changed the name of the default in my own fork but it would be great if this were an option.

OpenSession stop workin

With this error:

Error detected while processing function xolox#session#complete_names..xolox#session#get_names:
line 5:
E121: Undefined variable: g:session_directory
E116: Invalid arguments for function xolox#misc#path#absolute(g:session_directory)
E15: Invalid expression: xolox#misc#path#absolute(g:session_directory)
line 6:
E121: Undefined variable: directory
E116: Invalid arguments for function xolox#misc#path#merge(directory, '' . g:session_extension)), "\n")
E116: Invalid arguments for function glob(xolox#misc#path#merge(directory, '
' . g:session_extension)), "\n")
E116: Invalid arguments for function split(glob(xolox#misc#path#merge(directory, '' . g:session_extension)), "\n")
E15: Invalid expression: split(glob(xolox#misc#path#merge(directory, '
' . g:session_extension)), "\n")
line 7:
E121: Undefined variable: filenames
E116: Invalid arguments for function map(filenames, 'xolox#session#path_to_name(v:val)')
E15: Invalid expression: map(filenames, 'xolox#session#path_to_name(v:val)')
Error detected while processing function xolox#session#complete_names:
line 3:
E712: Argument of filter() must be a List or Dictionary
line 4:
E712: Argument of map() must be a List or Dictionary

not working with vim 7.0

vim-session is currently not working with vim 7.0 because of the missing haslocaldir() function.

I got it to work by changing the line

if haslocaldir()

to

if exists("*haslocaldir") && haslocaldir()

in autoload.vim.

RestartVim command not working

:RestartVim stopped working since version 2.3.1 (f1cb34e).

I've tested on Windows with a fresh gVim installation, and after issuing the command this error message is displayed:

  session.vim 2.3.2: Saved global session 'default' to ~\vimfiles\sessions\default.vim.
  session.vim 2.3.2: Closed global session 'default'.
  Error detected while processing function xolox#session#restart_cmd:
  line   23:
  E371: Command not found

It seems that problem can be traced to commit 5ad0d15, which introduces xolox#misc#os#find_vim(). The problem is that it is returning an empty string.

OpenSession with empty file

Every time I Use the OpenSession command to restore a previous saved session, the last file I used comes as an empty and duplicated file. I have to delete the buffer and select the one that works. Is a little anoying. I'm using buffergator just in case it has something to do.

Thanks

Add MiniBufExplorer support

Similar to the other BufExplorer and TagBar issues, MiniBufExplorer creates a special -MiniBufExplorer- buffer that creates problems when restoring sessions. It works fine with bare Vim sessions, so I guess if you just skip saving this buffer it should work?

Restart doesnt work with compiled vim

Hi, your plugin is great, thanks for it. This is a feature request.
I compiled vim my self and run it from a non standard location, i made sure theres always a $VIMRUNTIME enviromental variable.
When using :RestartVim it opens a new vim without my .vimrc loaded. This file is in the standard place ~/.vimrc
I tried debugging the function that does the restart but it is beyond my skills.
I made symlinks of my vim binaries to /usr/local/bin with the default names vim and gvim.
Thanks again.

Only a single buffer is saved instead of all buffers

Win7 using GVIM 7.2
I open multiple buffers but only the current one is saved when using SaveSession.
When I look at the sessions/default.vim file I see a line for
silent edit C:\stuff\python\blueslug\blueslug\views.py

Add ConqueTerm Support

Not sure if other people have gotten this but using sessions with ConqueTerm it wont work. It'll just leave a blank buffer instead of where I was in the command session. Thanks for the plugins! They rock!

Session.vim with NERDTree: One tab disappears on OpenSession

I normally browse with NERDTree open in the current project folder. NERDTree sits in its own tab (at tab position 0) and I open each project file in a new tab.

Using either :SaveSession or autosave, I can reload my last session, but one tab is missing--the one next to the NERDTree tab.

If I keep a file open in the same tab as NERDTree, this doesn't seem to happen.

Mime type in download URL

Could you put the MIME type (.zip) into the download URL (currently it just says http://peterodding.com/code/vim/downloads/session)? That would make it much easier to integrate it in Janus without any special installation scripting. Another solution would be to have the full content on GitHub. As when I just copy those files (autoload.vim and session.vim) it doesn't seem to work.

Unknown function: xolox#misc#os#is_win

Error detected while processing /Users/IT001-xu/.vim/bundle/vim-session/plugin/session.vim:
line 72:
E117: Unknown function: xolox#misc#os#is_win
E15: Invalid expression: xolox#misc#os#is_win()
line 86:
E121: Undefined variable: g:session_directory
E116: Invalid arguments for function fnamemodify(g:session_directory, ':p')
E15: Invalid expression: fnamemodify(g:session_directory, ':p')
line 87:
E121: Undefined variable: s:directory
E116: Invalid arguments for function isdirectory(s:directory)
E15: Invalid expression: !isdirectory(s:directory)
line 90:
E121: Undefined variable: s:directory
E116: Invalid arguments for function filewritable(s:directory) != 2
E15: Invalid expression: filewritable(s:directory) != 2
line 96:
E108: No such variable: "s:directory"

menu entry(ies)

Hello,

What do you think about add some menu entries (for gvim)?
For example, I have:
amenu 10.321 &File.Open\ Session\.\.\. :OpenSession<CR>

What about to add something like this to core plugin?

Latest master broken?

Error detected while processing /home/vampas/.Dotfiles/vim/bundle/vim-session/plugin/session.vim:
line   72:
E117: Unknown function: xolox#misc#os#is_win
E15: Invalid expression: xolox#misc#os#is_win()
line   86:
E121: Undefined variable: g:session_directory
E116: Invalid arguments for function fnamemodify(g:session_directory, ':p')
E15: Invalid expression: fnamemodify(g:session_directory, ':p')
line   87:
E121: Undefined variable: s:directory
E116: Invalid arguments for function isdirectory(s:directory)
E15: Invalid expression: !isdirectory(s:directory)
line   90:
E121: Undefined variable: s:directory
E116: Invalid arguments for function filewritable(s:directory) != 2
E15: Invalid expression: filewritable(s:directory) != 2
line   96:
E108: No such variable: "s:directory"
Press ENTER or type command to continue

RestartVim command not working

I recall using this command in the past and it doesn't seem to be working now. When I type :RestartVim in Macvim, the tabs close, an error message blinks in the bottom area and then vim just closes. On the plus side, everything seems to be saving correctly.

I uploaded a gist of the debug output for mvim -v9error.log. There's more to the log file, but I'm pretty sure this is the part where :RestartVim is called.

saving a session for the first time

when no session is open and there are no existing sessions then when the user quits vim without invoking :SaveSession it would be nice if the plugin asked him whether he wants to save the current environment as a session. or it could silently store the environment as the 'default' session (based on some option).

this change will enable the following scenario: you download vim-session, install it, put some lines into your .vimrc and forget about the plugin. also some users might forget to invoke :SaveSession for the first time and thus lose their environment.

Errors after latest udpate

After did the update, whenever I tried to open vim it always gives me this errro:

Error detected while processing /Users/cnbuff410/.vim/bundle/vim-session/plugin/session.vim:
line 72:
E117: Unknown function: xolox#misc#os#is_win
E15: Invalid expression: xolox#misc#os#is_win()
line 86:
E121: Undefined variable: g:session_directory
E116: Invalid arguments for function fnamemodify(g:session_directory, ':p')
E15: Invalid expression: fnamemodify(g:session_directory, ':p')
line 87:
E121: Undefined variable: s:directory
E116: Invalid arguments for function isdirectory(s:directory)
E15: Invalid expression: !isdirectory(s:directory)
line 90:
E121: Undefined variable: s:directory
E116: Invalid arguments for function filewritable(s:directory) != 2
E15: Invalid expression: filewritable(s:directory) != 2
line 96:
E108: No such variable: "s:directory"

Autosave on quit doesn't work when opening and closing "quickly" (within a couple minutes)

When I open a file without a session specified, make a quick edit and then close a file. I expect that when I start gvim with no parameters that it will start back up a default session with that file I was editing.

This does not appear to happen. An explicit SaveSession works great, but not the automatic save.

My pertinent vimrc settings are:

let g:session_autoload = 'yes'
let g:session_autosave = 'yes'
let g:session_autosave_periodic = 2
let g:session_default_to_last = 1
set sessionoptions-=help

Cheers!

Allow use of variables in session name

If I have:

let $TODAYS_DATE = strftime('%b_%d')

in my .vimrc file,

I'd like to be able to run

:SessionSave $TODAYS_DATE

and result in a Aug_17.vim file instead of a $TODAYS_DATE.vim file.

Won't autoset filetype with filetype on after calling OpenSession

I call OpenSession as soon as vim starts to resume my previous editing session.

Everything looks OK -- my NERDTree window comes back fine, and my editor pane comes back but my syntax highlighting is not automatically enabled. :set filetype returns nothing.

If I open a file with vim directly, the filetype does get appropriately set, just not when resuming a session.

Error everytime I open Vim (Linux)

I installed the plugin with Vundle using Bundle 'xolox/vim-session in my ~/.vimrc file, but, since the last time I ran the command to update all the plugins, every time I open Vim, I get this errors:

linha   72:
E117: Função desconhecida: xolox#misc#os#is_win
E15: Expressão inválida: xolox#misc#os#is_win()
linha   86:
E121: Variável indefinida: g:session_directory
E116: Argumentos inválidos para a função fnamemodify(g:session_directory, ':p')
E15: Expressão inválida: fnamemodify(g:session_directory, ':p')
linha   87:
E121: Variável indefinida: s:directory
E116: Argumentos inválidos para a função isdirectory(s:directory)
E15: Expressão inválida: !isdirectory(s:directory)
linha   90:
E121: Variável indefinida: s:directory
E116: Argumentos inválidos para a função filewritable(s:directory) != 2
E15: Expressão inválida: filewritable(s:directory) != 2
linha   96:
E108: Variável inexistente: "s:directory"

It's in brazilian portuguese. The correspondence is:

  • "linha" = line
  • "Função desconhecida" = Unknown function
  • "Expressão inválida" = Invalid expression
  • "Argumentos inválidos para a função" = Invalid arguments to the function
  • "Variável indefinida" = Undefined variable
  • "Variável inexistente" = Variable doesn't exist

Empty buffer in the beginning

This commit aadb3a2 cause some troubles to me. Every time I saved a session, it added an empty buffer in the beginning. Does it the normal behavior?

Change of cwd not marking session as dirty

vim-session does not currently mark a session as dirty if the working directory changes. This means that if I open a session, 'cd' (or 'lcd') and then close the session, the updated session, with new working directory, will not be saved.

Out of curiosity, what is the reason for the dirty flag? Is it mainly so that users with autosave disabled won't get spurious save prompts?

My current thinking is that this feature may cause more problems than it solves. Dirty checks only check if the buffer list or layout have changed, which misses a lot of options that get saved with the session.

Various unknown variables/function in 2.3.9

Updated to cfc5bdf today — not sure from what, just something relatively recent. Since then I get on starting vim (7.3.1030 on Arch Linux):

Error detected while processing /home/nwt/.vim/bundle/vim-session/plugin/session.vim:
line 72:
E117: Unknown function: xolox#misc#os#is_win
E15: Invalid expression: xolox#misc#os#is_win()
line 86:
E121: Undefined variable: g:session_directory
E116: Invalid arguments for function fnamemodify(g:session_directory, ':p')
E15: Invalid expression: fnamemodify(g:session_directory, ':p')
line 87:
E121: Undefined variable: s:directory
E116: Invalid arguments for function isdirectory(s:directory)
E15: Invalid expression: !isdirectory(s:directory)
line 90:
E121: Undefined variable: s:directory
E116: Invalid arguments for function filewritable(s:directory) != 2
E15: Invalid expression: filewritable(s:directory) != 2
line 96:
E108: No such variable: "s:directory"

On session restore, text scrolls out of screen at top (also: NERD trees don't persist correctly)

In issue #19 @diego898 reports the following two unrelated problems:

Things seem to be working although there is two slightly strange things:

  • The current directory on NERDTree is not saved with the session. It always starts on ~/myname/Desktop, the directory I make gvim start out of by the shortcut I use. Vim's cwd changes quickly however, due to things in my vimrc that makes its current directory match that of the open file.
  • Upon startup, both nerdtree and the file that is shown (correctly coming over from my last session which is good) are both shown at their very very bottom. In other words, a file with lines 1-30, starts with line 30 at the very top of my screen with vim showing me ~ for 70 lines? NERDTree also starts "too high" as it were. A quick gg fixes it, just found it a little strange.

Since these are new problems I'm closing #19 and using this new issue to keep track of them instead.

g:autosave option for saving if default session exists

I have a use case that doesn't seem too unusual that would be incredibly useful to myself: usually, I don't want to make a default.vim session in any directory I happen to open vim in, otherwise I litter my clean directories with sessions from random times I needed vim open. On the other hand, if I have been using sessions (e.g. default.vim exists) I would like the autosave functionality to be "yes" so that when I quit, default.vim reflects the state of vim before exiting.

In essence, a fourth option of "ifexists", which acts like "no" if there isn't a default.vim in the current directory, and "yes" if there is one. This way, I don't litter my drive with sessions files, but get the autosave functionality where I have explicitly called SaveSession before.

~ Jonathan Martin

Make session_directory respect trailing '//'

It would be great if g:session_directory would respect a trailing //, the same way that the built-in dir does. That way, I could just keep the sessions for all my projects in a central location, the way I do with swap and backup files.

In case you're not familiar with this option, this is in :help dir:

For Unix and Win32, if a directory ends in two path separators "//" or "", the swap file name will be built from the complete path to the file with all path separators substituted to percent '%' signs. This will ensure file name uniqueness in the preserve directory. On Win32, when a separating comma is following, you must use "//", since "" will include the comma in the file name.

(This would be an alternative of solving the use case I presented in #22.)

broken after update

Error detected while processing /home/agummer/.vimrepo/pathogen/bundle/session/plugin/session.vim:
line 72:
E117: Unknown function: xolox#misc#os#is_win
E15: Invalid expression: xolox#misc#os#is_win()
line 86:
E121: Undefined variable: g:session_directory
E116: Invalid arguments for function fnamemodify(g:session_directory, ':p')
E15: Invalid expression: fnamemodify(g:session_directory, ':p')
line 87:
E121: Undefined variable: s:directory
E116: Invalid arguments for function isdirectory(s:directory)
E15: Invalid expression: !isdirectory(s:directory)
line 90:
E121: Undefined variable: s:directory
E116: Invalid arguments for function filewritable(s:directory) != 2
E15: Invalid expression: filewritable(s:directory) != 2
line 96:
E108: No such variable: "s:directory"
Press ENTER or type command to continue

add guioptions and guifont only when gui_running or gui_macvim

in autoload session.vim

if is_all_tabs
    call add(a:commands, 'set guioptions=' . escape(&go, ' "\'))
    call add(a:commands, 'silent! set guifont=' . escape(&gfn, ' "\'))
endif

please add guioptions and guifont only when gui_running or gui_macvim

in terminal vim save session will lose gui info

and please add macvim when check gui_running by gui_macvim

Use vim-misc repository, instead of shipping "xolox#misc" itself

I am using your plugins session and easytags (and the following folder names for it: easytags, session and vim-misc).

When using "vim-misc" as "vim-misc", but "vim-session" as "session" in the bundle folder, the following error is triggered:

Error detected while processing function <SNR>41_InitEasyTags..<SNR>41_CheckCtags..xolox#misc#os#exec: 
line    6: 
E731: using Dictionary as a String 
Error detected while processing function <SNR>41_InitEasyTags..<SNR>41_CheckCtags: 
line    6: 
E171: Missing :endif 
Error detected while processing function <SNR>41_InitEasyTags: 
line    3: 
E171: Missing :endif 
Error detected while processing /home/daniel/.dotfiles/vim/bundle/easytags/plugin/easytags.vim: 
line  121: 
E171: Missing :endif

I guess that it is related to easytags using the xolox#misc functions from the session plugin.
Renaming session to vim-session works around this.

Incompatibility with vimwiki plugin

I've noticed that this plugin doesn't work well with vimwiki plugin
(http://www.vim.org/scripts/script.php?script_id=2226) - it corrupt some of
the mappings.

Steps to reproduce de fault:

  1. :e temp.wiki -> by default vimwiki will create some normal mode mappings
    for some commands, such as 'O' and 'gqq'.

  2. insert some text, save the file and the session with :SaveSession testWiki

  3. either call :RestartVim or close the current instance of Vim and load the
    session testWiki

  4. normal 'O' now inserts nmap \wr VimwikiRenameLink"
    instead of new line, while 'gqq' doesn't format the line and gives an
    error.

Reset Session?

Right now i have a session that's over 800 lines... I've been working on this client project awhile, and that's the output of many many days of opening and closing the same session.

in fact, scarily:

% grep -c badd redstamp.vim 
829

I don't really want this many buffers open. :(

i've resorted to deleting the session, and starting again -- but i wonder, could you consider -- if there's any way? to be able to rebuild/reset the session with whatever is currently in view? I don't need hidden or unloaded buffers, for example, nor do i want to have settings that i've set, unset, etc.

or another best case way of doing it?

RestartVim doesn't set session

First of all I'd thank you for this great plugin!

I mainly use this plugin with its default session and option g:session_autoload set to 'yes'.
So when I open the first gVim instance the plugin brings the default session, and if I open more instances of gVim the plugin doesn't open any session.

The problem happens when I issue :RestartSession to restart the default session. The command executes correctly, but when I try to open new instances of gVim they try to open the default session. It seems that RestartSession doesn't set the session lock. Issuing SaveSession solve the problem, but it is a little bit annoying.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.