CC'ing tex indent maintainer as it appears to be a tex-specific problem.
--
--
You received this message from the "vim_dev" 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
On Friday, 4 November 2016 22:33:42 UTC+3, DrChip wrote:
> Coacher wrote:
> > On Friday, 4 November 2016 14:36:12 UTC+3, Antony Scriven wrote:
> >> That's because 'o' in 'indentkeys' is causing new lines to be
> >> indented according to 'indentexpr'.
> > Indeed, after 'set indentkeys-=o' gqgq
On Friday, 4 November 2016 22:30:29 UTC+3, DrChip wrote:
> Your example has "filetype plugin indent on" -- that means that you
> have plugins enabled, and anything in ~/.vim/plugin has been loaded (ie.
> sourced). Ditto for indent plugins.
Neither ~/.vim/plugin, nor ~/.vim/indent exists.
--
Coacher wrote:
> On Friday, 4 November 2016 14:36:12 UTC+3, Antony Scriven wrote:
>> That's because 'o' in 'indentkeys' is causing new lines to be
>> indented according to 'indentexpr'.
> Indeed, after 'set indentkeys-=o' gqgq works as expected in the case
> described above.
> gqgq works as
Coacher wrote:
> On Wednesday, 2 November 2016 23:50:57 UTC+3, DrChip wrote:
>> Using 8.0.055, I get your expected results. So, I suggest that you
>> check your plugins.
> AFAIU since I have '-u NONE' in cmdline, only system-wide plugins are
> possibly in effect and I don't have any, except for
On Friday, 4 November 2016 14:36:12 UTC+3, Antony Scriven wrote:
> That's because 'o' in 'indentkeys' is causing new lines to be
> indented according to 'indentexpr'.
Indeed, after 'set indentkeys-=o' gqgq works as expected in the case described
above.
gqgq works as expected in non-tex files
On 2 November 2016 at 16:51, Coacher wrote:
> [...] Consider the following file:
>
> \begin{env}
>
x
x
> \end{env}
>
> Open it like this: vim -N
On Wednesday, 2 November 2016 23:50:57 UTC+3, DrChip wrote:
> Using 8.0.055, I get your expected results. So, I suggest that you
> check your plugins.
AFAIU since I have '-u NONE' in cmdline, only system-wide plugins are possibly
in effect and I don't have any, except for plugin manager
Gary Johnson wrote:
> On 2016-11-02, Charles E Campbell wrote:
>> Coacher wrote:
>>> Consider the following file:
>>>
>>> \begin{env}
>>> x
>>> x
>>>
On 2016-11-02, Charles E Campbell wrote:
> Coacher wrote:
> > Consider the following file:
> >
> > \begin{env}
> > x
> > x
> > \end{env}
> >
> >
Coacher wrote:
>
> Consider the following file:
>
> |\begin{env}
> x
>
> x \end{env} |
>
> Open it like this: |vim -N -u NONE -c 'filetype plugin indent
11 matches
Mail list logo
