On 2017-05-04, Jacques Troussard wrote:
> Can anyone explain to me why when writing python code, vim is auto
> indenting after this variable assignment?
>
> .vimrc file setting for python file
> autocmd BufNewFile, BufRead *.py
> \ set tabstop=4
> \ set softtabstop=4
> \ set
Can anyone explain to me why when writing python code, vim is auto indenting
after this variable assignment?
.vimrc file setting for python file
autocmd BufNewFile, BufRead *.py
\ set tabstop=4
On Do, 04 Mai 2017, Charles E Campbell wrote:
> What is v+ and v- ?
A special label used by mutt and vim to display the following lines like
shell window.
BTW: I just got a report, that on ufs inodes are not re-used and the
file will have a different inode after writing it with Vim.
Best,
Christian Brabandt wrote:
> Hi Gary!
>
> On Mi, 03 Mai 2017, Gary Johnson wrote:
>
If that was true, I would expect the inode number of the file to be
different after Vim had edited it, but that is not what I observe.
The inode number is unchanged.
I created a file with
On 17/05/03 13:26, Gary Johnson wrote:
On 2017-05-03, Christian Brabandt wrote:
Hi Gary!
On Mi, 03 Mai 2017, Gary Johnson wrote:
> > > If that was true, I would expect the inode number of the file to be
> > > different after Vim had edited it, but that is not what I observe.
> > > The inode
