Hi Albert!
On Fr, 08 Apr 2016, Albert Berger wrote:
> Greetings,
>
> I wonder, is there some commonplace good solution for c++ syntax
> highlighting, like, e.g. YouCompleteMe is a popular recommendation
> for powerful autocompletion? Internet search has revealed only
> a couple of cpp.vim files,
I want to embed python code in the vim script,
and I write the test ode like this:
```
fu! CusFoo()
python << EOF
print 'xixi'
EOF
endfunction
```
and when I call the CusFoo from the command line use `call CusFoo()`
the vim will exit immediately.
I can guarantee that the problem is lies in t
Greetings,
I wonder, is there some commonplace good solution for c++ syntax
highlighting, like, e.g. YouCompleteMe is a popular recommendation
for powerful autocompletion? Internet search has revealed only
a couple of cpp.vim files, which unfortunately don't provide
syntax highlighting comparable
On Thu, Apr 07, 2016 at 11:46:03AM -0400, Charles Campbell wrote:
> Albert Berger wrote:
> > On Wed, Apr 06, 2016 at 10:21:42PM -0700, Ben Fritz wrote:
> >> On Tuesday, April 5, 2016 at 2:44:23 PM UTC-5, Albert Berger wrote:
> >>> Greetings!
> >>>
> >>> How does one detect the file type in .vimrc?
Hi,
> Indeed, I'm pretty sure the file itself hasn't been read yet when
> reading the .vimrc, but I may be wrong about that.
Worse. When you open a second or a third file, the .vimrc isn't read anymore.
.vimrc settings are meant to be global settings that can apply to anything.
When we want ded
Albert Berger wrote:
> On Wed, Apr 06, 2016 at 10:21:42PM -0700, Ben Fritz wrote:
>> On Tuesday, April 5, 2016 at 2:44:23 PM UTC-5, Albert Berger wrote:
>>> Greetings!
>>>
>>> How does one detect the file type in .vimrc? AFAIU, 'filetype' setting is
>>> not yet set when .vimrc is processed. The fol
On Wed, Apr 06, 2016 at 10:21:42PM -0700, Ben Fritz wrote:
> On Tuesday, April 5, 2016 at 2:44:23 PM UTC-5, Albert Berger wrote:
> > Greetings!
> >
> > How does one detect the file type in .vimrc? AFAIU, 'filetype' setting is
> > not yet set when .vimrc is processed. The following check doesn't
>
If I define:
nmap = /===
after pressing = to jump to the next occurrence of === I may use to jump
back. Great. But if I define:
nmap = :exe '/==='
then searches for some reason are not added to the jump list. Can you confirm
this behaviour? Is there a way to remember jumps in the latter case?
Hi,
thanks, I will make the use of a local filetype.vim, as you suggest, I
am using an old ubuntu out of update, and never had problems with
updates, as they are gone some year ago.
The good of assembler... it changes rarely, or is built in some minutes.
Anyway, the issue now is not with vim,
