Christian Brabandt wrote:
On Mi, 25 Sep 2013, Christian Brabandt wrote:
On Mi, 25 Sep 2013, Christian Brabandt wrote:
On Wed, September 25, 2013 15:21, Bram Moolenaar wrote:
'cinoptions' is for 'cindent' options.
So do we agree, that cino=#N with N being non-zero would
Christian Brabandt wrote:
On Di, 24 Sep 2013, Gary Johnson wrote:
On 2013-09-24, Christian Brabandt wrote:
I guess, the intention is, that in C code the defines need to be in the
first column.
Thanks for checking that.
[...]
Vim's behavior looks to me like a mistake in
On Wed, September 25, 2013 13:18, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Di, 24 Sep 2013, Gary Johnson wrote:
On 2013-09-24, Christian Brabandt wrote:
I guess, the intention is, that in C code the defines need to be in
the
first column.
Thanks for checking that.
Christian Brabandt wrote:
Indeed, it looks strange. Especially, since left shifts are allowed, but
once you reach column 1, you can't right shift anymore. Also note, that
despite Vim's inability to right shift defines, the file will still be
marked modified.
Here is a simple patch,
On Wednesday, September 25, 2013 6:18:00 AM UTC-5, Bram Moolenaar wrote:
For portability and readability I would encourage keeping the # in the
first column.
Agree, that makes sense. And thus the default 'cindent' settings should also
place it in the first column.
Allowing to put it
On Wed, September 25, 2013 15:21, Bram Moolenaar wrote:
'cinoptions' is for 'cindent' options.
So do we agree, that cino=#N with N being non-zero would allow to
indent 'defines'?
regards,
Christian
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
On 2013-09-25, Ben Fritz wrote:
On Wednesday, September 25, 2013 6:18:00 AM UTC-5, Bram Moolenaar wrote:
For portability and readability I would encourage keeping the # in the
first column.
Agree, that makes sense. And thus the default 'cindent' settings
should also place it in
Gary Johnson wrote:
On 2013-09-25, Ben Fritz wrote:
On Wednesday, September 25, 2013 6:18:00 AM UTC-5, Bram Moolenaar wrote:
For portability and readability I would encourage keeping the # in the
first column.
Agree, that makes sense. And thus the default 'cindent'
On Mi, 25 Sep 2013, Christian Brabandt wrote:
On Mi, 25 Sep 2013, Christian Brabandt wrote:
On Wed, September 25, 2013 15:21, Bram Moolenaar wrote:
'cinoptions' is for 'cindent' options.
So do we agree, that cino=#N with N being non-zero would allow to
indent 'defines'?
No one
I've discovered that with 'cindent' set and with 'cinkeys'
containing 0# as it does by default, the command has no effect on
a line having a # in column 1.
To demonstrate this, start Vim as
vim -N -u NONE
and enter this line with the # in column 1:
#define this
Type and . Note that
On Di, 24 Sep 2013, Gary Johnson wrote:
I've discovered that with 'cindent' set and with 'cinkeys'
containing 0# as it does by default, the command has no effect on
a line having a # in column 1.
To demonstrate this, start Vim as
vim -N -u NONE
and enter this line with the # in
On 2013-09-24, Christian Brabandt wrote:
On Di, 24 Sep 2013, Gary Johnson wrote:
I've discovered that with 'cindent' set and with 'cinkeys'
containing 0# as it does by default, the command has no effect on
a line having a # in column 1.
To demonstrate this, start Vim as
vim
On Di, 24 Sep 2013, Gary Johnson wrote:
On 2013-09-24, Christian Brabandt wrote:
I guess, the intention is, that in C code the defines need to be in the
first column.
Thanks for checking that.
[...]
Vim's behavior looks to me like a mistake in someone's understanding
of C.
I
13 matches
Mail list logo
