Monday, February 17, 2014

Re: Adapting an existing session file to a new plugin

On Monday, February 17, 2014 6:00:22 PM UTC-6, Tim Johnson wrote:
> This is kind of a general question, but it has to do with issues
>
> that have made coding life complicated for me in the past.
>
>
>
> For a specific example of this topic, I have just installed the
>
> drupal plugin for vim. I have an existing project that is loaded by
>
> a session file and it is named
>
>
>
> drupal_modules.vim
>
>
>
> it is likely that drupal_modules.vim has settings that might
>
> override the settings provided by the newly install drupal plugin.
>
>
>
> Quite a large number of buffers are present in this session. It is
>
> certainly doable, but is a bit of an inconvenience to to reload all
>
> of them.
>
>
>
> I have in the past done the following:
>
> Delete all commands in the session file *except for* anything
>
> starting with 'badd' or 'edit'.
>
>
>
> That has worked, but sometimes I have ended up with syntax
>
> highlighting being clobbered.
>
>
>
> I'd welcome all comments that might make the transition easier.
>
>
>


Well, do you really need your session file to restore option values and mappings? Or can you rely on your .vimrc, plugins, and other config to set options and mappings? If you don't need those in your session file, you can adjust 'sessionoptions' to remove the "options" string.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments: