Hi,
i need a little help with my setup for softwareprojects with a
shellscript. What i want to have is:
#!/bin/sh
export BLAH=blubb
start-some-server&
vim -S theSession --source-file project-specific-default-settings
The file project-specific-default-settings contains stuff like
set
On Thu, Jan 21, 2016 at 10:20 AM, wrote:
> Hi,
>
> i need a little help with my setup for softwareprojects with a
> shellscript. What i want to have is:
>
>
> #!/bin/sh
>
> export BLAH=blubb
> start-some-server&
> vim -S theSession --source-file project-specific-default-settings
>
>
> Th
Tony Mechelynck writes:
> On Thu, Jan 21, 2016 at 10:20 AM, wrote:
[...]
>> The files have to be read in this sequence:
>> 1) ~/.vimrc
>> 2) project-specific-default-settings
>> 3) theSession
[...]
> vim -S project-settings.vim -S theSession.vim
>
> (for files in Vimscript language the
2016-01-21 14:36 GMT+03:00 :
> Tony Mechelynck writes:
>
> > On Thu, Jan 21, 2016 at 10:20 AM, wrote:
>
> [...]
>
> >> The files have to be read in this sequence:
> >> 1) ~/.vimrc
> >> 2) project-specific-default-settings
> >> 3) theSession
>
> [...]
>
> > vim -S project-settings.vim -S the
On Thu, Jan 21, 2016 at 12:36 PM, wrote:
> Tony Mechelynck writes:
>
>> On Thu, Jan 21, 2016 at 10:20 AM, wrote:
>
> [...]
>
>>> The files have to be read in this sequence:
>>> 1) ~/.vimrc
>>> 2) project-specific-default-settings
>>> 3) theSession
>
> [...]
>
>> vim -S project-settings.vim
Well, it seems that I should not redefine :, but monitor the mode/status like
some plugin for the statusbar does.
--
--
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/mail
From time to time, upon exiting Vim an error message flashes on the screen, but
too quickly for me to read it. I'd like to understand why it happens. Is there
a way to log such errors or somehow pause Vim when an error appears?
Nicola
--
--
You received this message from the "vim_use" maillist
On Thursday, January 21, 2016 at 12:27:51 PM UTC-6, Nicola wrote:
> From time to time, upon exiting Vim an error message flashes on the screen,
> but
> too quickly for me to read it. I'd like to understand why it happens. Is there
> a way to log such errors or somehow pause Vim when an error appea
This works well.
Thank you very much for your thorough and thoroughly informed response.
> autocmd OptionSet buftype :if v:option_new is# 'nofile' | nnoremap …|
> endif
Unfortunately, 'OptionSet' event seems a very new event to vim :-(
The Distro provided vim's I use do not support it (but m
On 2016-01-21, Ben Fritz wrote:
> On Thursday, January 21, 2016 at 12:27:51 PM UTC-6, Nicola wrote:
> > From time to time, upon exiting Vim an error message flashes on the screen,
> > but
> > too quickly for me to read it. I'd like to understand why it happens. Is
> > there
> > a way to log such
On 2016-01-21 18:58:24 +, Gary Johnson said:
On 2016-01-21, Ben Fritz wrote:
On Thursday, January 21, 2016 at 12:27:51 PM UTC-6, Nicola wrote:
From time to time, upon exiting Vim an error message flashes on the screen, but
too quickly for me to read it. I'd like to understand why it happen
I can run vimdiff with multiple files, but I'd like to be able to use
vimdiff's "do", "diffu" features.
When I try to run "do", it gives me (obviously) an error:
"More than two buffers in diff mode, don't know which one to use"
If I have 3 files, and I'm on the center one, how do I tell it to "do"
Hmm...I guess I should have read the manual first.
:diffget
seems to do the trick. So to answer my own question, I would do
:diffget 1 for the one on the left
and :diffget 3 for the one on the right.
But if anyone has any other useful pointers for using vimdiff, I would
appreciate it.
Thanks,
Ve
13 matches
Mail list logo